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 am using version 0.4.0 with config setting topic_prefix = "livingroom", have a Hue Bridge configured and working, and two color light strips configured in the bridge. I can change the hue, saturation, on/off status of both light strips as expected by sending payloads like {"on": "true"} and {"hue": 43210, "sat": 50}, and so on.
However, I noticed that the state information published back by hue2mqtt never reflects the current state of the lights. Instead the messages always just show the initial values from when hue2mqtt was last started.
Here is an example log from subscribing to livingroom/light/#:
The same happens with the other light strip. The same also happens when I remove the topic_prefix config setting. Please let me know if there is anything else I could try to debug this behavior.
The text was updated successfully, but these errors were encountered:
I have similar issue with published group messages. When light is turned on/off the state field of the group message is not updated (all_on or any_on) and remains the same (when the hue2mqtt was started). To me it seems that the light messages has the correct state. I have version 0.4.1.
I am using version 0.4.0 with config setting
topic_prefix = "livingroom"
, have a Hue Bridge configured and working, and two color light strips configured in the bridge. I can change the hue, saturation, on/off status of both light strips as expected by sending payloads like{"on": "true"}
and{"hue": 43210, "sat": 50}
, and so on.However, I noticed that the state information published back by hue2mqtt never reflects the current state of the lights. Instead the messages always just show the initial values from when hue2mqtt was last started.
Here is an example log from subscribing to
livingroom/light/#
:Note how the reported state always has
"hue": 10000, "sat": 100,
instead of the new values. The lights do change to the new values.Here is the verbose output from hue2mqtt from the same session that produced the MQTT messages above:
The same happens with the other light strip. The same also happens when I remove the
topic_prefix
config setting. Please let me know if there is anything else I could try to debug this behavior.The text was updated successfully, but these errors were encountered: