Hello.
On my HA instance it seems that DUAL R3 switches are mapped individually _1/_2 and when "sysmsg" is received for unavailable/available messages getStateByEntityId doesn't take that into account.
I am guessing similar is happening to other multi-switch devices as well.
Here is unavailable message for reference.
{"action":"sysmsg","deviceid":"<device-id-without-outlet-number>","apikey":"<api-key>","params":{"online":false}}
Some context:
I have heating setup in a way that an external timed trigger turns off the contactor which heating is connected to every 3-5 hours for about 40 minutes.
When this happens, my entities are renamed to undefined-1/2 and I need to resync lovelace card before I can control the device again.
Hello. On my HA instance it seems that DUAL R3 switches are mapped individually _1/_2 and when "sysmsg" is received for unavailable/available messages getStateByEntityId doesn't take that into account. I am guessing similar is happening to other multi-switch devices as well.
Here is unavailable message for reference.
{"action":"sysmsg","deviceid":"<device-id-without-outlet-number>","apikey":"<api-key>","params":{"online":false}}
Some context: I have heating setup in a way that an external timed trigger turns off the contactor which heating is connected to every 3-5 hours for about 40 minutes. When this happens, my entities are renamed to undefined-1/2 and I need to resync lovelace card before I can control the device again.