deep-seated-jeep4374

Surprisingly it states that 2.0.15 is the latest version when I try the above steps. # wget -qO- https://releases.hyperion-project.org/hyperion.pub.key | gpg --dearmor -o /usr/share/keyrings/hyperion.pub.gpg File '/usr/share/keyrings/hyperion.pub.gpg' exists. Overwrite? (y/N) y # echo "deb [signed-by=/usr/share/keyrings/hyperion.pub.gpg] https://apt.releases.hyperion-project.org/ $(lsb_release -cs) main" | tee /etc/apt/sources.list.d/hyperion.list deb [signed-by=/usr/share/keyrings/hyperion.pub.gpg] https://apt.releases.hyperion-project.org/ bullseye main # apt-get install hyperion Reading package lists... Done Building dependency tree... Done Reading state information... Done hyperion is already the newest version (2.0.15~bullseye). 0 upgraded, 0 newly installed, 0 to remove and 28 not upgraded. # I tried the Ubuntu\Debian steps mentioned here: https://releases.hyperion-project.org/ within the hyperion container terminal instead (removing any mention of sudo) # Add necessary packages for the installation: apt-get update && apt-get install wget gpg apt-transport-https lsb-release # Add Hyperion’s official GPG key: wget -qO- https://releases.hyperion-project.org/hyperion.pub.key | gpg --dearmor -o /usr/share/keyrings/hyperion.pub.gpg # Add Hyperion-Project to your APT sources: echo "deb [signed-by=/usr/share/keyrings/hyperion.pub.gpg] https://apt.releases.hyperion-project.org/ $(lsb_release -cs) main" | tee /etc/apt/sources.list.d/hyperion.list # Update your local package index and install Hyperion: apt-get update && apt-get install hyperion I then restarted the container and it reported I was on 2.0.16. I haven't performed any testing though. I'll check if this solves the problem I reported three posts above in a few days. Edit: I confirm this resolved both the Suspend\Lock errors in the logs AND hyperion is able to control my WLED leds. 🥳 Thank you @ishtangli for pointing me in this direction.

Hi all, I have the following setup: ESP32 with WLED connected to ws2812b leds I am able to control the leds via WLED without issue. Hyperion Android grabber installed on a 2017 Nvidia Shield Hyperion.ng (2.0.15) on unraid (6.12.10) Hyperion.ng is receiving the video stream from the Android grabber, but its not pushing anything to the leds (whether related to the stream, or even the non-streaming Background Effect/Color). Surprisingly, WLED is 'aware' that hyperion has 'taken over' led control since the WLED webUI states "WLED is receiving live data from 192.168.x.x", but the leds just go from the WLED setting to being switched off. To rule out an issue with my config, I installed Hyperion.ng (2.0.16) on my Windows machine with the exact same setup. The only difference apart from OS is my hyperion version, but I doubt thats causing connectivity to the leds. The only errors I see in my unraid instance of hyperion.ng are My understanding of any threads I found on the hyperion.ng forums said these are not 'real' errors as its just notifying that since its a headless server (unraid) it cant be suspended or locked. Hoping anyone can point in me in the direction of a solution. Would definitely prefer to run Hyperion.ng off my unraid instance.