Hue light status - how does it work?

[taenzerme]

Hi there,

thanks for the great library!

I have a working KNX bridge connection and Hue bridge connection. I configured a Hue gradient light strip:

and the KNX device:

I set up the group address in ETS and set a button on a Glass Push-button II Smart to switch the light.

Switching works fine. But I don't get any status of the lamp / lightstrip.

Is there some tutorial somewhere how to get the status to the group adress correctly?

Thanks,
Sebastian

[Supergiovane]

Hi
the status is sent from HUE device to the node, at the address 7/1/1
You can take a look at my playlist. https://www.youtube.com/watch?v=egRbR_KwP9I&list=PL9Yh1bjbLAYpfy1Auz6CKDfXUusgMwOQr
There is some videos about HUE.
The new documentation will be out soon. I've been very busy in developing the HUE nodes, so the official documentation is currently unavaiable.

[taenzerme]

Hey Max, thanks!

This may be a stupid question, but do I have to create that GA 7/1/1 in ETS?

I did and connected that GA to the status of the MDT switch. But it does not update the status / read the status.

Any ideas why that is?

Thanks,
Sebastian

[Supergiovane]

Hi
you may not create the GA 7/1/1 in ETS, but you must create a KNX Device note (similar to what you've done for the GA 7/1/0), with GA 7/1/1 ;-)

[Supergiovane]

PS: i've misunderstood your question, sorry. If you must interact with real KNX devices on your BUS (your MDT for example), you must create the 7/1/1 in ETS as well.
I think you cannot set the GA 7/1/1 in the MDT if you don't create a GA in ETS.

[taenzerme]

Hi Max,

thanks, I tried, but it's still not working as expected.

I created the GA in ETS (7/1/0 = device, 7/1/1 = device status, 7/1/28 = device dim state.

I configured the GA in the Hue device like this:

But the GA value is alway empty:

Any idea?

Thanks,
Sebastian

[Supergiovane]

Hi
Take a look here https://github.com/Supergiovane/node-red-contrib-knx-ultimate/wiki/-Sample---Virtual-Device

If you intend to read the value of 7/1/1 as well as 7/1/28, the corresponding node must have the appropriate settings. You need to set the react to read telegram option, as well as “respond with” (this option appears as soon as you click “react to read requests)
I suggest you to fully understand the KNX part of the nodeset, by taking a look at the wiki.

[taenzerme]

Thanks Max, that helped a lot, but wasn' really the source of my problems.

I used a tunneling channel already in use for a different connection. Switching to a different tunneling channel of my IP gateway made it work :-)