Open jannislehmann opened 4 years ago
My fix was to change the modelid and the manufacturer at the following locations:
https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/functions/__init__.py#L15
append the json by "manufacturername": "Philips", "modelid": "LST002"
https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/protocols/esphome.py#L102 to get the modelid from the light_types array or change this line https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/protocols/esphome.py#L133
GitHubMain diyHue software repo. Contribute to diyhue/diyHue development by creating an account on GitHub.
GitHubMain diyHue software repo. Contribute to diyhue/diyHue development by creating an account on GitHub.
GitHubMain diyHue software repo. Contribute to diyhue/diyHue development by creating an account on GitHub.
Hue apps will allow only supported entertainment lights to be added. ESPHome use custom modelid, and firmware version, so these must be replaced.
This is true, but why would you do that? The generic and wled builds emulate a hue bulb as well.
I remember when I made that I only tested rgbw bulbs for functionality. Curious if those still work with entertainment mode. Hassio add-on should definitely be something that should be added.
RGBW and RGB both work with Hue Entertainment if the model id is changed. I have a working hassio add-on, but it lacks so much and has some hardcoded changes.
https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/protocols/esphome.py#L102 Well this line could be changed to LST002 but that would cause it to treat any rgb bulb as a light strip. Custom devices for rgb were used because those were simply never available with standard hue lights. Rgbw still should work without any adjustments.
GitHubMain diyHue software repo. Contribute to diyhue/diyHue development by creating an account on GitHub.
What exactly is missing in the hassio add-on and why/what are hardcoded changed needed? IIRC seemed like a simple docker config repository.
I am not that confident with Dockerfiles therefore, I adapted the aarch64 Dockerfile and changed a few things. Another thing I changed is that I cloned it into a local folder for hassio to build it. I also changed the model id for the ESPHome bulbs.
And I tried to add Hass.IO ingress and a script for automatic saving before stopping but both without success. Lastly, I did a change to the network scan because it stopped at my first ip (router) because of an untrusted SSL cert.
Mostly, just moving files into a different location and one small patch.
Tell me this. If you do not change the model id for rgbw does it work?
If you mean Hue Entertainment, no.
That doesn't really make sense since rgbw uses the model id of a normal hue bulb. You changing the model id would only change it to a light strip. Something is not adding up...
Likely because you are not correctly adding the rgbw bulb. Finally, lightstrips are not technically supported with the current implementation, though they work.
You might be right and I may be mistaking. It's bin almost three weeks since I tested everything.
I am only using a RGB light strip.
In that case, this is more of a feature request rather than a bug. Potentially we may be able to change the model id of an rgb bulb to an oem hue bulb, but it may not function properly.
It worked properly on my end.
I'll consider this as a feature request to support rgb strips...
any news here? I am also trying to get esphome with rgb (ws2812).
Most of the focus is towards the refactor, and progress has been slow on that. After that is complete, I will look into new features.
Describe the bug I cannot add the ESPHome RGB light strip to a Hue Entertainment zone due to it being a outdated
swversion
.To Reproduce
diyhueasyncudp.h
file to check whether awhite_led
is set. Otherwise you cannot compile the ESPHome yaml.Expected behavior I should be able to add the ESP826 ESPHome bulb to a Hue Entertainment zone the same as with a generic one.
Logs
Additional context The
swversion
is set here. https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/functions/__init__.py#L15 I set mine manully to5.127.1.26581
as this is what the generic ESP8266 script uses. However, this still not works. I wonder whether this has to be with the model or manufacturer string?I did a few tweaks to get this to work in general. As soon as things are stable, I will try to create the pull request as I fixed a few things on my end. I also created a Home Assistant diyHue addon! But everything still features quite some hardcoded lines etc.