-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[avmfritz] changing the color of a fritz!dect 500 lightblub isn't working #12427
Comments
According to the AHA HTTP spec (section 3.5) I found online, color bulbs only accept a few select combinations of hue/saturation (maybe this is why the FRITZ!DECT 500 reports a Crucially, any other combination is silently discarded. Crude sample code for OpenHAB 3.2.0 to "snap" selected hue/saturation to a hardcoded table of legal combinations extracted from a sample light bulb might look as follows (edit: for completeness, I also added a color temperature channel and set the light to pure white for low saturations). Note that, color temperature aside, the same pre-filtering could be done in rules as well.
|
@sommer Thank you for your replay. Sorry for my late response, but it cost me some time to be able to try out your code snippets. (I'm absolutly new to Java and I don't go into that internals of openhab). In a first step I tried to work with a rule, waht don't works well to me. Finally I was able to run your code https://github.com/vich-667/openhab-addons/pull/1/files what works fine to me. I also read the pdf you linked. As far as I understand it, fritz box only support that dedicated values. If only this values are supported currently by the fritz box and it's light bub it would be great to add this to openhab. In addition I have the effect that my FRITZ!DECT 500 is detected as FRITZ_DECT_500 and HAN_FUN_COLOR_BLUB, where only the HAN FUN thing works do me. I saw you only added the light temperature to the HAN FUN device. Is it the same to you? |
Hi all, I have some good news for you. There is an undocumented method "setunmappedcolor" available for the HTTP interface which allows to set a user-defined color for the bulbs without restrictions related to the predefined color mappings. I already tried to implement a solution for this. A test version can be installed via UI. Settings -> JSON third-party Add-Ons: Insert URL "https://christophweitkamp.de/openhab/addons.json" Settings -> Bindings: In section "Other Add-Ons" choose "CW - AVM FRITZ! Binding (stable)" and start installation. Note: Uninstall original AVM FRITZ! Binding before installing the test version. Happy to get some feedback. |
@cweitkamp: I justed tested your solution with "setunmappedcolor". Works fine to me. But the same effect here. Only the "HAN_FUN_COLOR_BLUB" works but not the "FRITZ_DECT_500" @sommer I would also like to have the color temperature channel in. |
It seems that with the current version of openHAB 3.4 changing color is working now, BUT obviously it is not possible to change back to white mode, after once having set a color option. |
Expected Behavior
I have a Fritz!Dect500 LightBlub connected to my Fritzbox 7590, both with the actual firmware. I also own some other stuff for example a Fritz!Dect200 what works well.
In my things inbox a FRITZ!DECT 500 and a HAN_FUN_COLOR_BULB is shown. The FRITZ!DECT 500 uses the ain shown in the Fritz!Box UI. The HAN_FUN_COLOR_BULB uses the same ain with an
-1
in addition.Current Behavior
Possible Solution
Steps to Reproduce (for Bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: