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'm refactoring all of my Insteon devices within Home Assistant in order to future proof against the upcoming deprecation of the previous schema. As part of this, I'm revisiting some of the automations I use in Home Assistant in order to account for discrepancies of physical button pushes vs. using the insteon/{{address}}/scene topic.
For example, I have two dimmers in my "hallway" that are Insteon linked. If I turn one on, the state of the other is updated to reflect the reality. If I manually dim or brighten one, the state of the other is updated to reflect reality. This is via Insteon linking, so no MQTT or HA comes into play.
Now, when I use insteon/{{address}}/scene (which is said to duplicate a physical button press) to turn on or off one of the linked switches, it's state is updated to reflect reality via Insteon linking; no MQTT or HA involvement needed. However, when I set the brightness via the same insteon/{{address}}/scene, Insteon links are not updated to reflect the brightness level of the dimmer that I've set.
I've simply accepted this for the last two and half years, and I simply perform the syncing manually with a Home Assistant automation. However…
…is there a better way? Should insteon-mqtt be sending the brightness command to the modem/dimmer in a manner that the dimmer will broadcast its updated status via Insteon linking so that I don't need to manually update this via my own automations?
The text was updated successfully, but these errors were encountered:
I'm refactoring all of my Insteon devices within Home Assistant in order to future proof against the upcoming deprecation of the previous schema. As part of this, I'm revisiting some of the automations I use in Home Assistant in order to account for discrepancies of physical button pushes vs. using the
insteon/{{address}}/scene
topic.For example, I have two dimmers in my "hallway" that are Insteon linked. If I turn one on, the state of the other is updated to reflect the reality. If I manually dim or brighten one, the state of the other is updated to reflect reality. This is via Insteon linking, so no MQTT or HA comes into play.
Now, when I use
insteon/{{address}}/scene
(which is said to duplicate a physical button press) to turn on or off one of the linked switches, it's state is updated to reflect reality via Insteon linking; no MQTT or HA involvement needed. However, when I set the brightness via the sameinsteon/{{address}}/scene
, Insteon links are not updated to reflect the brightness level of the dimmer that I've set.I've simply accepted this for the last two and half years, and I simply perform the syncing manually with a Home Assistant automation. However…
…is there a better way? Should insteon-mqtt be sending the brightness command to the modem/dimmer in a manner that the dimmer will broadcast its updated status via Insteon linking so that I don't need to manually update this via my own automations?
The text was updated successfully, but these errors were encountered: