-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Room and basic color (especially limitless/milight) support #713
Comments
There is now a logic to differentiate between color and dimmable lights, so the hue app knows which devices support color. |
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So i implemented rooms and some color support. If anyone is interested in being a beta tester go for it. Details can be found in my pull request or by asking me how to use it. I would suggest reading the request before trying it.
I myself tested the rooms with the official hue app and "all 4 hue" and via manual api calls. Seems to work. Controlling the color of my milight rgbw strips also works good.
What does that mean? You can do new stuff via the official hue app (or other hue apps) including
There is no default group anymore so you have to create one. Be careful to always uncheck "Add default scenes" during room creation in the official hue app for it to work. The rooms are stored in a separate .db file for which the location should be specified in bridge control, similar to the device.db path.
Note that group actions iterate through the lights in the group so if one item has a url with long processing durations because of delays etc. this will be noticeable.
There is now a ColorUrl additional to on/off/dim that is used for color commands.
There are currently the following replacements available:
${color.r} ${color.g} ${color.b} which will be replaced by the color in 0-255 format
${color.milight:x} where x is a number between 0 and 4 with 0 - all groups and 1-4 a individual group. That will be replaced by the entire hex string for the udp packet so usage is for example: udp:https://ip:port/0x${color.milight:0} Note that the fitting "group on" must still be sent before that item.
The replacements and thereby the color support work for the following item types: command, http, tcp, udp. Currently only incoming XY and CT values are processed, hue/sat does nothing (but hue/sat seems to be not used by the hue app anyway).
Color and rooms only work with apps, not with an amazon echo because the echo can't do that natively, it would require the skill and ha-bridge is not connected to that. So if you want milight color with an amazon echo you still have to create one separate device per color unfortunately.
For rooms/groups with Amazon Echo i implemented a workaround.
Currently all devices are now seen as "Extended color lights" regardless of their real capabilities. I plan on somehow differentiate between "Extended color lights" and "Dimmable lights" to let the hue app know when a device doesn't really support color. I will not use "On/Off light" even if it's adequate because it seems that an amazon echo finds these lights only via the skill..
Currently the rooms are not visible or editable through the ha-bridge web gui but eventually i will change that later. Perhaps with the possibility to define the processing order of the devices in a group for group actions.
There are other small changes (described in the request)
Currently waiting for bwssystems to react to my pull request but he seems currently absent.
The text was updated successfully, but these errors were encountered: