Open smhex opened 2 years ago
As it turns out, the automation is not the only reason to trigger the situation. Restarting Homebridge lets to the same effect. The getcurrentdoorstate topic is retained. When Homebridge is started, the content of the state messages is not correct.
[2/6/2022, 3:37:00 PM] [Garage] Received MQTT: gdc/control/getnewdoorstate = close
[2/6/2022, 3:37:00 PM] [Garage] Received close - targetDoorState state is now 1
[2/6/2022, 3:37:00 PM] [Garage] Received MQTT: gdc/control/getcurrentdoorstate = closing
[2/6/2022, 3:37:00 PM] [Garage] Received closing - currentDoorState state is now 3
Normally the getcurrentdooorstate topic should return closed.
If the door already reached its final state and the last command is repeated the new status is intermediate (closing or opening). The keeps the icon in HomeKit spinning forever. The situation is triggered when automation is used (e.g. close door at 8 pm). As a workaround the rule should check the current door state before.