ph0b0s101

I have the exact same issue, configured everyhing as explained and changed the appdata directory accordingly. Get this message when i try to save some files to docmost: [Nest] 41 - 04/07/2025, 9:12:38 AM ERROR [AttachmentService] Error uploading file to drive: [Nest] 41 - 04/07/2025, 9:12:38 AM ERROR [AttachmentService] Error: Failed to upload file: EACCES: permission denied, mkdir '/app/data/storage/01960f03-de86-73db-b0b7-9232daaa15e7' at LocalDriver.upload (/app/apps/server/dist/integrations/storage/drivers/local.driver.js:19:19) at async StorageService.upload (/app/apps/server/dist/integrations/storage/storage.service.js:25:9) at async AttachmentService.uploadToDrive (/app/apps/server/dist/core/attachment/services/attachment.service.js:152:13) at async AttachmentService.uploadFile (/app/apps/server/dist/core/attachment/services/attachment.service.js:60:9) at async AttachmentController.uploadFile (/app/apps/server/dist/core/attachment/attachment.controller.js:82:34) [Nest] 41 - 04/07/2025, 9:12:38 AM ERROR [AttachmentController] BadRequestException: Error uploading file to drive at AttachmentService.uploadToDrive (/app/apps/server/dist/core/attachment/services/attachment.service.js:156:19) at async AttachmentService.uploadFile (/app/apps/server/dist/core/attachment/services/attachment.service.js:60:9) at async AttachmentController.uploadFile (/app/apps/server/dist/core/attachment/attachment.controller.js:82:34) { response: { message: 'Error uploading file to drive', error: 'Bad Request', statusCode: 400 }, status: 400, options: {} } Is there an official solution out there?

Would absolute dream, if you could share your config.

Genau das alturismo Hatte es gestern schon in unsere Gruppe geschrieben. Das ist das schöne an Unraid, es gibt für alles praktikable Lösungen. Danke dir für dein Feedback

Hallo Zusammen, aktuell läuft mein HA Setup noch auf einem Proxmox Server, den ich aber in Rente schicken möchte. Ich migriere gerade meine ganzen VM's und LXC Container nach Unraid. Heute war die HA VM dran. Dabei bin ich auf ein ungewöhnliches Problem gestoßen, wo ich aktuell noch keine Lösung gefunden habe. Ich möchte beide Sticks betreiben. Der Skyconnect als Zigbee Bridge und den Sonoff als Thread Boarder Router (ist bereits entsprechend geflasht). Konkret werden beide Sticks aus der Überschrift mit der gleichen Hardware ID erkannt: 10c4:ea60 Im VM Config Fenster wird dann nur einer von beiden angezeigt: Bei meiner Recherche habe ich zwei Threads gefunden, die ähnliche Themen haben. Einmal mit Proxmox wo es eine Lösung gab: https://community.home-assistant.io/t/skyconnect-usb-device-has-very-same-device-id-as-aeotec-z-stick-7/515025/8 Einmal auch mit Unraid, aber nur mit der Lösung einen anderen Stick bzw. den gleichen Stick in einer anderen Revision zu erhalten. Der aber auch schon 3 Jahre alt ist: Hatte schon mal jemand ein ähnliches Problem und kennt ggf. eine Lösung hierfür? Über Feedback freue ich mich.

I run into the same issue today but was lucky enought to find a quick solution for this. The problem is the line ending character of the script file itself. The fix was easy as descriped in this ubuntu forum post: https://askubuntu.com/questions/896860/usr-bin-env-python3-r-no-such-file-or-directory The problem are your line ending characters. Your file was created or edited on a Windows system and uses Windows/DOS-style line endings (CR+LF), whereas Linux systems like Ubuntu require Unix-style line endings (LF). There is a simple tool that can convert the two different styles for you called dos2unix. Install it by running sudo apt install dos2unix After that, you can convert files in either direction using one of the commands dos2unix /PATH/TO/YOUR/WINDOWS_FILE unix2dos /PATH/TO/YOUR/LINUX_FILE Example: $ cat test.py #!/usr/bin/env python3 print("ok") $ ./test.py /usr/bin/env: ‘python3\r’: No such file or directory $ dos2unix test.py dos2unix: converting file test.py to Unix format ... $ ./test.py ok Hope that helps someone else.

Switched to the pbs docker container and don't look back. VM + LXC Container Backups working as intended.

Ok created a new machine from scrapt with SeaBIOS and qcow2. The result ist absolutly the same: Error Message from Server: INFO: starting new backup job: vzdump 103 --mode stop --fleecing 0 --mailnotification failure --node proxmox-01 --notes-template '{{guestname}}, {{node}}, {{vmid}}' --all 0 --storage srv-prod-pbs-1 --mailto [email protected] INFO: Starting Backup of VM 103 (qemu) INFO: Backup started at 2024-07-10 22:12:53 INFO: status = running INFO: backup mode: stop INFO: ionice priority: 7 INFO: VM Name: homeassistant INFO: include disk 'scsi0' 'local-lvm:vm-103-disk-0' 64G INFO: stopping virtual guest INFO: creating Proxmox Backup Server archive 'vm/103/2024-07-10T20:12:53Z' INFO: starting kvm to execute backup task WARN: no efidisk configured! Using temporary efivars disk. ERROR: VM 103 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device INFO: aborting backup job INFO: resuming VM again after 18 seconds ERROR: Backup of VM 103 failed - VM 103 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device INFO: Failed at 2024-07-10 22:13:11 INFO: Backup job finished with errors INFO: notified via target `<[email protected]>` TASK ERROR: job errors Anything I can do from here on? Edit: Added VM Logs: 2024-07-10 19:53:38.050+0000: Starting external device: virtiofsd /usr/libexec/virtiofsd --fd=42 -o source=/mnt/disk3/Backups/proxmox/,cache=always,sandbox=chroot,xattr 2024-07-10 19:53:38.074+0000: starting up libvirt version: 10.0.0, qemu version: 8.2.2, kernel: 6.8.12-Unraid, hostname: SGER-unRaid01 LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME=/var/lib/libvirt/qemu/domain-10-Debian \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-10-Debian/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-10-Debian/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-10-Debian/.config \ /usr/local/sbin/qemu \ -name guest=Debian,debug-threads=on \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-10-Debian/master-key.aes"}' \ -machine pc-q35-8.2,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,hpet=off,acpi=on \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m size=2097152k \ -object '{"qom-type":"memory-backend-memfd","id":"pc.ram","share":true,"x-use-canonical-path-for-ramblock-id":false,"size":2147483648}' \ -overcommit mem-lock=off \ -smp 2,sockets=1,dies=1,cores=1,threads=2 \ -uuid 8bc7c4e7-1809-f127-9221-c02846b8a311 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=41,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ -device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ -device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ -device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ -device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pcie.0","addr":"0x7"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.3","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Debian/vdisk1.qcow2","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap","cache":{"direct":false,"no-flush":false}}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-2-format","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/linux/proxmox-backup-server_3.2-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":2}' \ -chardev socket,id=chr-vu-fs0,path=/var/lib/libvirt/qemu/domain-10-Debian/fs0-fs.sock \ -device '{"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","queue-size":1024,"tag":"backup_proxmox_virtiofs","bus":"pci.1","addr":"0x0"}' \ -netdev '{"type":"tap","fd":"42","id":"hostnet0"}' \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:d2:1e:29","bus":"pci.2","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=40,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,share=ignore,audiodev=audio1 \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pcie.0","addr":"0x1"}' \ -global ICH9-LPC.noreboot=off \ -watchdog-action reset \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.5","addr":"0x0"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2024-07-10 19:53:38.074+0000: Domain id=10 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring

Thank you for your fast answer. Tried to change to seabios, but this option is not available. Have you some hints how I can achieve this?

Hi SimonF, sorry for my late response, have to activate e-mail notification. I don't 100% get your question. On the proxmox side I can deside which backup mode i want to use: Snapshot, suspend or stop: Backup modes for VMs: stop mode This mode provides the highest consistency of the backup, at the cost of a short downtime in the VM operation. It works by executing an orderly shutdown of the VM, and then runs a background QEMU process to backup the VM data. After the backup is started, the VM goes to full operation mode if it was previously running. Consistency is guaranteed by using the live backup feature. suspend mode This mode is provided for compatibility reason, and suspends the VM before calling the snapshot mode. Since suspending the VM results in a longer downtime and does not necessarily improve the data consistency, the use of the snapshot mode is recommended instead. snapshot mode This mode provides the lowest operation downtime, at the cost of a small inconsistency risk. It works by performing a Proxmox VE live backup, in which data blocks are copied while the VM is running. If the guest agent is enabled (agent: 1) and running, it calls guest-fsfreeze-freeze and guest-fsfreeze-thaw to improve consistency. But either mode will result with the same error message. My uunraid server is bootet in uefi mode. So you think this will cause the problem?

I just played around with an Proxmox Backup Server (PBS) as VM on Unraid to Backup all CT and VM Container from my 2 remote Proxmox Nodes. I found this really helpfull thread on the proxmox forums: Proxmox Forum Thread I was able to create a working vm with access to the mounted unraid share, following the instructions from the linked thread. I can backup CT Containers just fine, but get Error's when I try the same for Virtual Machines: 100: 2024-07-08 17:09:50 INFO: Starting Backup of VM 100 (qemu) 100: 2024-07-08 17:09:50 INFO: status = running 100: 2024-07-08 17:09:50 INFO: VM Name: homeassistant 100: 2024-07-08 17:09:50 INFO: include disk 'scsi0' 'local-lvm:vm-100-disk-0' 32G 100: 2024-07-08 17:09:50 INFO: backup mode: snapshot 100: 2024-07-08 17:09:50 INFO: ionice priority: 7 100: 2024-07-08 17:09:50 INFO: creating Proxmox Backup Server archive 'vm/100/2024-07-08T15:09:50Z' 100: 2024-07-08 17:09:50 INFO: issuing guest-agent 'fs-freeze' command 100: 2024-07-08 17:10:02 INFO: issuing guest-agent 'fs-thaw' command 100: 2024-07-08 17:10:02 ERROR: VM 100 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device 100: 2024-07-08 17:10:02 INFO: aborting backup job 100: 2024-07-08 17:10:02 INFO: resuming VM again 100: 2024-07-08 17:10:02 ERROR: Backup of VM 100 failed - VM 100 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device My fstab looks like this: # <file system> <mount point> <type> <options> <dump> <pass> /dev/pbs/root / ext4 errors=remount-ro 0 1 UUID=149A-67A4 /boot/efi vfat defaults 0 1 /dev/pbs/swap none swap sw 0 0 proc /proc proc defaults 0 0 # unraid proxmox share backup_proxmox_virtiofs /mnt/backup_unraid virtiofs rw,relatime 0 0 The mount point as follows: root@srv-prod-pbs-1:~# ls -la /mnt/backup_unraid/ total 2104 drwxrwxrwx 5 backup backup 74 Jul 8 15:19 . drwxr-xr-x 3 root root 4096 Jul 8 14:37 .. drwxr-x--- 65538 backup backup 1069056 Jul 8 14:45 .chunks drwxr-x--- 5 backup backup 55 Jul 8 16:15 ct -rw-r--r-- 1 backup backup 0 Jul 8 14:45 .lock drwxr-x--- 3 backup backup 25 Jul 8 15:19 vm And the VM XML like this: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4'> <name>srv-prod-pbs-1</name> <uuid>c6f19883-32c1-898b-1565-45885add9b5d</uuid> <metadata> <vmtemplate xmlns="unraid" name="Debian" icon="debian.png" os="debian" webui="" storage="default"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-8.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/c6f19883-32c1-898b-1565-45885add9b5d_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/srv-prod-pbs-1/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/linux/proxmox-backup-server_3.2-1.iso' index='1'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/virtiofsd' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> </binary> <source dir='/mnt/disk3/Backups/proxmox/'/> <target dir='backup_proxmox_virtiofs'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:d9:87:e9'/> <source bridge='br0'/> <target dev='vnet3'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/run/libvirt/qemu/channel/4-srv-prod-pbs-1/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <watchdog model='itco' action='reset'> <alias name='watchdog0'/> </watchdog> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Anyone faced the same problem and found a solution? Running Unraid 7.0 Beta 1.

I could imagine that this is because of that the topic was already solved and nobody get attention to it. What do you think? Maybe we should open a new bug report topic?

Yep, scrolling is mandatory to bring the functionality back.

@Casadream_1 I can confirm, that this "workaround" will work for me as well. Wierd and maybe some kind of a bug. Thanks for sharing your finding!

I am facing the exact same issue with the new Unraid Version starting from 6.12. I am running 6.12.4 at the moment with NPM in Version 2.9.19 and websocket's enabled. The same issue as the original posted described. When I open unraid with local IP Address without proxy url, it is working perfectly fine. Any recommendations, what to do? Short Update, also tried the latest NPM Version, with no luck. Any feedback is much appreciated.

Sorry for my late feedback but it works like a charm. Thank you so much for sharing your solution. Great!

At the moment, I did not use the gpu in any docker. Only in the VM but did not have installed any nvidia drivers over the application store. Furthermore the gpu is bind via the tools system devices page in unraid. Is this a showstopper?

Thank you for sharing your solution. This is only working I use the nvidia gpu driver and did not pass through the gpu to any vm, right?

how?

Hello @mgutt, thank you for your reply. So far so good, but I cannot edit the go file because I did not find the file explorer plugin / app. I have installed the file manager plugin von dynamic but there is no option to directly edit files. So did I oversee something? Thank you for updating the start post with some power supply recommandations. This is great and I put them on my watchlist. Cheers

Hello together, I tried to get better idle energy usage by following you guide. Installed powertop and restarted the server, see that the cstates are not used. Tried the auto tune command and got the following: powertop --auto-tune powertop: /lib64/libncursesw.so.6: no version information available (required by powertop) powertop: /lib64/libtinfo.so.6: no version information available (required by powertop) modprobe cpufreq_stats failed Loaded 0 prior measurements Cannot load from file /var/cache/powertop/saved_parameters.powertop File will be loaded after taking minimum number of measurement(s) with battery only RAPL device for cpu 0 RAPL device for cpu 0 Devfreq not enabled glob returned GLOB_ABORTED Cannot load from file /var/cache/powertop/saved_parameters.powertop File will be loaded after taking minimum number of measurement(s) with battery only Leaving PowerTOP One User also mentioned that powertop was removed by Tips & Tweaks plugin because of more problems then rewards. So is it still a thing? Furthermore, how can I get the config editor in Version 6.11.1? Seems there is no app to install and I cannot find it in the tools section of the webgui. Any tipps?

Any chance for english translation or written instructions?

Missed to thank you for information how I can build a switch by myself. Work like a charm. Did managed to build a template switch which start the server via WOL and bring them to Standby with your MQTT implementation. Great.

Whatever you fixed, this was the problem Now it works and i got the message in the log aswell. > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js WARN mode option is deprecated. You can safely remove it from nuxt.config Connected to mqtt broker READY Server listening on http://0.0.0.0:80 Received MQTT Topic: homeassistant/sger-unraid01/binhex-lidarr/dockerState and Message: started assigning ID: MQTT-R-kkx4s6l1 MQTT-R-kkx4s6l1 succeeded Received MQTT Topic: homeassistant/sger-unraid01/sleep and Message: assigning ID: MQTT-R-kkx4swtl Received MQTT Topic: homeassistant/sger-unraid01/sleep and Message: assigning ID: MQTT-R-kkx4swtl MQTT-R-kkx4swtl succeeded So what is your plan for the final inplementation. So there will be also a switch or trigger of any kind, which I can use on the HA Dashboard, like reboot, restart, and so on or should I build an automation and call the mqtt service with the topic? I have to really thank you for your efford to implement this. Great 😄

Hm it still seems that no command will reach the unraid server.

Thank you for your reply, i assume, there must be any error on my site firing the mqtt command. Because there is nothing in the logs after i have issued the command. But when I trigger one of the docker switches it will work perfectly fine: > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js WARN mode option is deprecated. You can safely remove it from nuxt.config READY Server listening on http://0.0.0.0:80 Connected to mqtt broker Received MQTT Topic: homeassistant/sger-unraid01/binhex-lidarr/dockerState and Message: started assigning ID: MQTT-R-kkx2p44f MQTT-R-kkx2p44f succeeded Received MQTT Topic: homeassistant/sger-unraid01/binhex-lidarr/dockerState and Message: stopped assigning ID: MQTT-R-kkx2qvab Received MQTT Topic: homeassistant/sger-unraid01/binhex-lidarr/dockerState and Message: stopped assigning ID: MQTT-R-kkx2qvab MQTT-R-kkx2qvab succeeded So maybe I have to alter the command? On the mqtt manual from homeassistant there is mentioned that the payload is nessecary? https://www.home-assistant.io/docs/mqtt/service/ Sorry that I am not a big help so far 😞