Wenn Du magst kannst Du den Fix testen:
Wie man PRs testet, ist in der Doku beschrieben:
Dass die Hintergrundbeleuchtung aktuell gelb/grün ist, ist ein bekanntes Problem und ein Fehler:
HTTPS Support is provided after the v2.1.1 release
Install the nightly build to make use of it.
You need to put the DNS hostname which is part of your certificate (signed by an official CA)
Enable minimum Advanced settings and then you can enable SSL.
HyperBian is a package of an operating system with Hyperion pre-installed.
It comes with the latest Release, not Nighly.
Nevertheless, you can switch the version of the pre-installed software.
If you have a spare SD card, it might be best, if you install another HyperBian and then switch the release. So you could test savely.
To switch:
1. log into HyperBian via ssh.
2. remove the current Hyperion
3. install the nightly build
The respective easy install script commands you find here:
Hyperion on Linux · Hyperion documentation
The install script takes care that Hyperion is auto started.
Version 2.1.1 has some issues…
Suggest you install the nightly build
Try to install 2.0.16
Hyperion has no direct Tuya protocol support.
But if you connect the device to HomeAssistant, Hyperion is able to send to HA. As suggested by Ambient_theater77,
Go and try the HA route.
If the device has Wifi, you should be able to connect directly to HA
Please checkout the following thread in addition
and review the grabber‘s hardware control settings.
Side note: does hyperion have some kind of schedule feature? I like it when my lights turn on in the evening
Have a look at the Scheduled Events configuration.
Not sure, if I see the screenshots correctly.
Looks like your green screen areas result in a red LED color.
This indicates that your LEDs device‘s Color order is not set correctly.
Just run Hyperion‘s Color Order Wizard from the top menu (Magic Wand icon)
Please checkout the following thread
and review the grabber‘s hardware control settings.
QuoteBlack image from capture card
If the grabber produces a black image, it is likely that the the brightness is set to zero.
To get this corrected:
a) Switch to Expert Setting
b) Check the Control values (see 1.)
c) Press Button "Default Hardware controls" (2.)
d) The Control Values should have changed (3.)
e) Click Save (4.)
Would be great, if you could report back, if that worked.
I updated the Release notes to ensure that people can find this easily.
QuoteYou should now see a non black image in the preview. when selecting the ws281x in the LED output, by default, I'm not able to use it because I'm not root
see the documentation on PWM Prerequisites (Controller type RPi PWM/ws281x) and the link how to change the service user.
How did you install Hyperion initially?
Via the easy install script?
What does the following command report?
systemctl status hyperion@${USER}
The HA API is not made for low latency updates. In case you have network lights which are directly supported by Hyperion, always go via the non HA route.
For your lights you might need to check where the latency comes from. Given you are not sharing too much details, it is hard to say.
Latency could happen as Hyperion does requests via a bad Wi-Fi connection.
To sort this out you could enable Debug logging in Hyperion.
There you will then see how long one API request to HA takes.
In case, you issue is more that you do not see frequent updates, you might want to test if reducing the latch time helps.
You should enable expert settings to see the element. You should not reduce the latchtime below the API request time (you checked above). Also include some buffer.
Hoping that this provided you with some pointers.
As every setup is different you need to explored the influencing dimensions.
You need to install the latest Nightly Build
Alternatively in 2.1.1 you could disable an instance before stopping Hyperion.
When you bring it up next time, the instance is still disabled and grabber stopped.
BTW: Build on Raspian Bullseye will fail too, because of QT5 support has been removed and there is no native QT6 support for Bullseye, only a non-supported backport solution, that's why a had to upgrade (fresh install) to Bookworm. Maybe you want to update SupportedPlatforms.md.
Maybe you would like to use our docker images to build for Bullseye?
We build on bullseye with Qt 6.4.2
