search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.15k stars 1.68k forks source link

State of Philips hue bulb is never updated when controlled by Busch-Jaeger 6735 #5969

Closed asmolarczyk closed 3 years ago

asmolarczyk commented 3 years ago

Hi,

I'm using a Busch-Jaeger 6735 switch to control my zigbee devices. In order to use the dimmable scenes of this switch, I had to remove the bindings to the zigbee2mqtt coordinator. This setup works quite good when using e.g. Mueller Tint bulbs because they support attribute reporting. The state of the bulbs is immediately updated in zigbee2mqtt.

Unfortunately my Philips hue bulbs do not support reporting. Therefore the new state of the bulbs (on/off, brightness) is never updated. I already tried to use report_emulate, but I think this does not help here.

When using the Philips hue bridge, it takes a few seconds, but then the state of the bulbs is updated in the app. Is it somehow possible to get the same polling-based update behaviour in zigbee2mqtt?

I'm on the dev branch.

Koenkk commented 3 years ago

As a work around you can try putting the Hue bulb in a group and binding the 6735 to the group instead of directly to the device.

asmolarczyk commented 3 years ago

Thank you! This is a nice workaround. Unfortunately (of course) the bulbs restore to the last brightness level when using this approach. With the default dimmable scenes as described by busch jaeger it is possible to recall a scene

github-actions[bot] commented 3 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days