You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have come across a strange behavior, and I am not yet sure whether this is connected to the specific bulb or your nodes or me being stupid. Anyway:
Bulb Firmware, Node Red, zigbee2mqtt, homekit-bridged and your nodes being at latest stable, I have created a very simple flow (see also attachement "flow.txt").
When I switch ON the light for he first time, it goes to 100% Brightness, then I switch OFF and ON again, now the bulb is on at 1% brightness. in the screenshot of the debugging nodes you can see, that the response node outputs 0% twice then turns to 1% in Brightness on Zigbee level. The bulb is at the same time not connected to any group, direkt link or other flow, but when I simulate the same thing with Zigbee messages and dashboard, it perfectls keeps it's prior brightness.
Any Ideas?
First of all, thanks for your work.
I have come across a strange behavior, and I am not yet sure whether this is connected to the specific bulb or your nodes or me being stupid. Anyway:
Bulb Firmware, Node Red, zigbee2mqtt, homekit-bridged and your nodes being at latest stable, I have created a very simple flow (see also attachement "flow.txt").
When I switch ON the light for he first time, it goes to 100% Brightness, then I switch OFF and ON again, now the bulb is on at 1% brightness. in the screenshot of the debugging nodes you can see, that the response node outputs 0% twice then turns to 1% in Brightness on Zigbee level. The bulb is at the same time not connected to any group, direkt link or other flow, but when I simulate the same thing with Zigbee messages and dashboard, it perfectls keeps it's prior brightness.
Any Ideas?
flow.txt
The text was updated successfully, but these errors were encountered: