Hue Binding & deCONZ Phoscon RaspBee & Osram Ledvance

Add-ons Bindings
1

Hello

I have a big Problem with the HUE Binding.
My configuration is Raspberry PI with a RaspBee and Phoscon Image.
On my Server Openhab2 with Hue binding.

The Phoscon Gateway find’s all my lamps and switches.
Osram plugs, Hue lamps, gledopto driver for rgbww and Osram Ledvance Downlights
The Ledvance lamps working since last update from deConz - update was a week ago.

The HUE Binding find’s all of them except the 10 Osram Ledvance Downlights…
So what can i do, that i get this also in Openhab or needs the HUE Binding an update or is it not compatibel in moment?

Thanks, Marcel

2

Hi @lons81,

Welcome to the openHAB community :+1:. Can you access the REST interface of your deCONZ and find out the JSON response for the lights/ endpoint (see http://dresden-elektronik.github.io/deconz-rest-doc/lights/ for more information)? With these data it would be possible to analyze why it is not working.

3

Hi

Here is the output from /lights/:

"etag": "9883a8119c818ac46c095a292868329d",
"hascolor": true,
"manufacturername": "LEDVANCE",
"modelid": "Down Light TW",
"name": "Wohnzimmer Couch",
"state":{"alert": "none", "bri": 254, "colormode": "ct", "ct": 370,…},
"swversion": "00102002",
"type": "Color dimmable light",
"uniqueid": "d5:3a:00:b8:d1:f0:00:00-01"

another:

“etag”: “10f8ce43b7f3f39f25c7903270e9526c”,
“hascolor”: true,
“manufacturername”: “LEDVANCE”,
“modelid”: “Down Light TW”,
“name”: “Badezimmer”,
“state”:{“alert”: “none”, “bri”: 181, “colormode”: “ct”, “ct”: 370,…},
“swversion”: “00102002”,
“type”: “Color dimmable light”,
“uniqueid”: “12:3a:00:b8:d1:f0:00:00-01”

And this is a Phillips which is find trough OpenHab:

“ctmax”: 454,
“ctmin”: 153,
“etag”: “5bf6eff2f879f06e73692eec543a07b9”,
“hascolor”: true,
“manufacturername”: “Philips”,
“modelid”: “LTC015”,
“name”: “Esszimmer Licht”,
“state”:{“alert”: “none”, “bri”: 254, “colormode”: “ct”, “ct”: 366,…},
“swversion”: “1.46.13_r26312”,
“type”: “Color temperature light”,
“uniqueid”: “00:17:88:01:03:37:1b:c2-0b”

I hope this will help to find my error.

Big thanks, Marcel

4

Yes, that helps a lot. Thanks. The “type”: “Color temperature light” is important for discovery of devices by the Hue binding. As you can see the LEDVANCE bulbs return “type”: “Color dimmable light” which will not recognized as valid by the Hue binding. I am not sure if that type is correct. Maybe you should post your findings into your related deCONZ issue and ask for verification over there.

1 Like
5

@cweitkamp can he just update it in the rest api of second also? I am thinking if it matches then it may just work. This is a short term fix if so of course.

6

@Thedannymullen I am afraid I did not understand what you are asking for. Who should update which REST API?

7

Sorry, I was asking if the OP could update the light type in the deconz rest api. Basically change the description to what openhab is looking for.

8

Ah. No he cannot. We asked the deCONZ developers to do so. And they did - very quickly b.t.w.

But I do not think that it will be a problem to manually add a thing of thing-type 220 to control the LEDVANCE device.

9

Thx!

10

Yesterday, i have tried to change power on settings in DeconZ VNC view.
There i see that the Ledvance downlights are “Zigbee HomeAutomation” not “Zigbee Light Link” - is this the problem why OpenHab didn’t find them?
But in android app “Hue Essential” i can controll the light (light temperatur & dimming and so on) like Philips Hue or Gledopto…
I hope this info helps.

11

Hi
Today i have test it with Domoticz.
Result all lamps work fine with deConz & Domoticz.
So it must be a problem with the Hue Binding of Openhab.

12

What is the best way to interact with the deConz guys to request fixing this on more LEDVANCE lights? I’m on the version that fixed the bug referenced in this thread, but I’m having the issue w/ the Flex RGBW and the 5/6 inch retrofit RGBW. API output for one of each below:

    "14": {
        "ctmax": 666,
        "ctmin": 153,
        "etag": "50e995d7a0e3cacfad12dbe19be8de90",
        "hascolor": true,
        "manufacturername": "LEDVANCE",
        "modelid": "FLEX RGBW",
        "name": "Bathroom Under Counter",
        "state": {
            "alert": "none",
            "bri": 0,
            "colormode": "ct",
            "ct": 271,
            "effect": "none",
            "hue": 0,
            "on": false,
            "reachable": true,
            "sat": 254,
            "xy": [
                0.5064,
                0.1674
            ]
        },
        "swversion": "00102101",
        "type": "Color dimmable light",
        "uniqueid": "f0:d1:b8:00:00:07:25:a2-01"
    },
    "2": {
        "ctmax": 526,
        "ctmin": 153,
        "etag": "2576d190715275eef5f1a8c1f9c8ca8b",
        "hascolor": true,
        "manufacturername": "LEDVANCE",
        "modelid": "RT RGBW",
        "name": "Living Front Left",
        "state": {
            "alert": "none",
            "bri": 77,
            "colormode": "ct",
            "ct": 341,
            "effect": "none",
            "hue": 0,
            "on": true,
            "reachable": true,
            "sat": 254,
            "xy": [
                0.735,
                0.265
            ]
        },
        "swversion": "00102101",
        "type": "Color dimmable light",
        "uniqueid": "f0:d1:b8:00:00:06:b1:d6-01"
    },```
13

Hi James,

Go to https://github.com/dresden-elektronik/deconz-rest-plugin/issues, file a new issue, describe your findings like you did here, reference the previous issue. That is it.

15

Thanks Christoph! Issue submitted: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2367

16

@cweitkamp do you have any suggestions (or expectation-setting for responsiveness) on how to get the Deconz devs to take a look at that bug? It was submitted in mid January and there has been no action on their part unfortunately.

17

Hm, not really. You can try to address them personally by mentioning them in the issue.