[deconz] Tint remote control by Müller-Licht Color wheel does not work #8256
Comments
rabenhayn
added
the
enhancement
|
Please show how this is shown in the REST API. |
|
{ I guess the "angle" and "xy" values determine the color, some tests showed something like that: Yellow Green Light Blue: 270 Blue: Purple Red: |
|
I don‘t know what the angle is used for, but I think I can implement the xy sensor |
|
That's great! I think this LED remote control would be a fantastic addition to the Deconz-Zigbee environment at openHab.
|
|
Please try if https://janessa.me/esh/org.openhab.binding.deconz-2.5.8-SNAPSHOT.jar works as you expect. |
|
Hello, and thanks for the work. I have added the file to my openHAB/addons folder. After that the following thing appeared in the inbox. When I try to add it via paperUI, I get the error 409 Conflict Even if I remove all deconz .things and .items from the files, the error remains. When I connect the remote control via VSC, I don't see any more channels, I guess because it is still a switch. Probably I have to make the right thing out of it or create the right channels or items, but unfortunately I don't know which ones. EDIT: After I have removed the snapshot file from the openHAB/addons folder for a test, the thing is still found in the inbox. I guess I did not install the binding snapshot correctly. Do I need to install it in addition to the deconz binding, or does it replace the binding? If I remove the deconz binding from addons.cfg and leave the binding snapshot in the openHAB/addons folder, the deconz binding will appear in the paperUI, but not all things and their channels will be detected correctly. |
|
I‘ll have a look. |
|
Additional Log Information, Addons.cfg configured with deconz, Snapshot in openHAB/addons: 2020-08-13 08:14:14.716 [ERROR] [org.openhab.binding.deconz ] - bundle org.openhab.binding.deconz:2.5.8.202008101428 (239)[org.openhab.binding.deconz.internal.DeconzHandlerFactory(247)] : Error during instantiation of the implementation object com.thoughtworks.xstream.converters.ConversionException: Supported itemType for a ChannelType must not be empty. : Supported itemType for a ChannelType must not be empty. at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) ~[bundleFile:?] 2020-08-13 08:17:08.386 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type deconz:color. |
|
Unfortunately you downloaded the file before I fixed that error. Could you try to download and test again? Thanks a lot. |
|
Thanks for your answer. openhab.log: Do I have to create in VSC a specific thing with specific items? |
|
Argh. My fault. Fixed it. Please download again. |
|
Absolutely no problem. As I said, I really appreciate your work. For comparison the configuration menu of the remote control as a switch:
As you can see, the configuration parameters seem to be missing and some id points are different. |
|
Just uploaded a new version |
|
Well, you're on a very good way!
The thing is online and I was able to add the items, with the color channel providing a seemingly correct HSB value.
The paperUI does not show a value, but I don't think it matters, because the item is read correctly in the VCS.
Now, unfortunately, there is still a problem. Is it possible to add the missing switch-channels (Button Trigger and Button) to the thing? Because now only the last one added works. Either the switch from the VCS or the colorcontrol from the paperUI, but not both together. Probably because they have the same UID. |
|
I think this maybe related to the fact that the channel is read only and paper ui may not be able to display that. The more important thing is that the state of the item changes. I have added both channels. Can you try if that works as expected? |
|
Wow, I think you did it! All items seem to work properly.
I had to try a little bit on the rules, but now the buttons of the remote work according to their labels. I have to admit that the colour selection of the remote control is not very precise, but this seems to be a mechanical problem and requires some practice with a combination of long and short clicks. Thank you very much for your time and work! As mentioned before, I really appreciate your work and I think that others will benefit as well. Let me know if there's any other way I can thank you. |
Unfortunately the color wheel is only identified as a button. There seems to be no channel to read out the selected color.
This thread refers to the integration in deConz and zigbee2mqtt:
dresden-elektronik/deconz-rest-plugin#1209
THINGS
Bridge deconz:deconz:homeserver "Conbee 2" [host="xxx.xxx.xxx.xxx", apikey="xxxxxx", httpPort="30000", timeout=2000 ]{
switch LED_Fernbedienung "Fernbedienung LED" [ id="11" ]
}
ITEMS
Number FernbedienungLEDButton "Button" {channel="deconz:switch:homeserver:LED_Fernbedienung:button"}
DateTime FernbedienungLEDLastUpdated "Last updated" {channel="deconz:switch:homeserver:LED_Fernbedienung:last_updated"}
DateTime FernbedienungLEDLastSeen "Last seen" {channel="deconz:switch:homeserver:LED_Fernbedienung:last_seen"}
The text was updated successfully, but these errors were encountered: