I do not know, but generally I would not recommend Yeelight, as they make all sorts of problems (that is why I have not listed them before).
Cololight strip normally works out of the box and is not too pricey.
I do not know, but generally I would not recommend Yeelight, as they make all sorts of problems (that is why I have not listed them before).
Cololight strip normally works out of the box and is not too pricey.
Current everything which supports Nanoleaf‘s Open API work.
I think that does not apply to Matter.
You might want to look at Cololight, Philips Hue, Nanoleaf
There is no official open API provided by the vendor, so the answer is no.
There are unofficial ways of integration out there, so technically it could be done, but someone would need to spend time contributing to the project with an integration PR.
This is an open source project…. Everybody can get their hands dirty and provide further features.
Did you map the Hue UPD port into the docker?
If one would like to run Philips Hue in Entertainment mode, the following UDP port mapping is required in addition:- "2100:2100/udp"
see also https://github.com/psychowood/…docker?tab=readme-ov-file
Use the JSON API
Maybe you can check, which process blocks the port to be accessed by Hyperion ?
https://support.arduino.cc/hc/en-us/articles/4407830972050-Find-and-stop-process-blocking-a-port
It is always helpful to check the log for errors before uploading.
2024-04-14T00:12:36.441Z [LEDDEVICE|First LED Hardware instance] (ERROR) Device disabled, device 'adalight' signals error: 'Access denied.'
Your device cannot be accessed by Hyperion and therefore not be used.
As you are on Windows, I suggest you
- unplug the device,
- restart Windows,
- plug the device,
- start Hyperion
Ensure that no other program accesses the device.
vortex4711 Es kommt aktuell darauf an, wie Du die Kommandos benutzt.
Ich weiß nicht wie es in Hyperion Classic war.
In Hyperion NG kannst Du momentan die Kommandos nur über WebSocket bzw. permanenter TCP Session und dann nach einem Login benutzen.
Per Single http(s) Request geht es aktuell nicht.
Ich bin gerade dabei, das zu ändern.
Gib mir noch ein paar Tage, falls Du das Szenario benutzen willst.
I agree that it would be helpful to have details at one place. The doc link I shared above is an initial attempt.
Everybody can ship in to get the hyperion documentation elaborated.
I would think that place would be more suitable rather having a thread here that might get too long or spoiled over time.
Happy to add a HowTo or FAQ section, but it would be good, if content would be provided initially.
People can either share a Pull Request with content via https://github.com/hyperion-project/hyperion.docs or drop us a message.
See https://docs.hyperion-project.…ces/Overview.html#spi-pwm
you need to increase the SPI Buffer Size
Hi
Ich habe ein wenig Doku gefunden für eine LAN API
https://app-h5.govee.com/user-manual/wlan-guide
Es gibt auch eine Cloud API, die ergibt aber mit Hyperion keinen Sinn.
Es kann also jeder, der Lust und Zeit hat, hier gern Code für Govee Support einzureichen.
PS: Schon mal vorweg, der HA Code kann nicht einfach genommen werden, da er in Python geschrieben ist.
Any idea if the pi 3, wich I use before, will be supported in Hyperbian some times?
This is out of our control.
If this PR is merged, it will automatically be considered when building Hyperion.
You might need to check with the team providing the library linked.
Your Hardware „Revision : 9020e1“ is currently not supported.
Pi 3A+ 1.0 is…
There is already a change available, but it has not been made available yet.
You could apply the change and build Hyperion yourself …
Hyperion makes use of an external library which has a set of devices configured.
The error occurs, if your device is not supported.
Which Hyperion version are you running?
Edit: Please post the output of the following command to see what hardware version you are running with.
cat /proc/cpuinfo
I tried 2.0.16 on libreelec 9.0.2, 9.2.6, 10.0.4 and 11.0.6 but on none of them I got x11 working.
Thanks that you shared more details, as it helped to find a problem in the new install script.
I removed the DISPLAY environment variable to the service definition under the assumption that LibreELEC moved to GBM for all platforms.
I corrected the script and now you should be able to install 2.0.16 with LibreELEC on amd64.
Sorry for the inconvenience.
Note: Please backup your configuration file and import it into 2.0.16.
The config file location on LibeELEC was moved to the standard location as on other platforms.
I successfully installed Hyperion 2.0.16 on LibreELEC 9.2.6 (see picture below).
If you want to run LibreELEC 11.0.6, you need to use the Generic-Legacy image to run with X11.
see https://libreelec.tv/2024/01/29/libreelec-nexus-11-0-6/
Note, the script you used is not longer supported.
It would be great, if you could share what is not working with the latest install script and 2.0.16.
In case there are issues, we could have them addressed for the benefit of the overall community.