5xPa
commented
3 weeks ago Max this possibly be of relevance. I have four zones in the Texecom. 1 Front Door 2 Downstairs 3 Upstairs 4 Shed.
From Homekit I set zone 4 shed to Away mode, HomeKit Shed (zone 4) changed to Away after a minute or so Upstairs started to arm with the disarming message. Is it possible the problem is due to an error zone replies from the panel being sent to zone 3. Below is the Log
[20/08/2024, 09:08:02] [Homebridge UI] Homebridge log truncated by admin. [20/08/2024, 09:08:05] [Texecom] Sending arm/disarm command 1 to area 004 [20/08/2024, 09:08:05] [Texecom] Setting current status of area 004 to 1 because alarm responded OK [20/08/2024, 09:08:17] [MyChairOnDwnStairsAlmOn] Setting switch to true [20/08/2024, 09:08:17] [Evohome] System mode is set to: Away [20/08/2024, 09:08:17] [Evohome] { id: '1419055411' } [20/08/2024, 09:08:17] [Evohome] System mode is set to: Auto [20/08/2024, 09:08:17] [Evohome] { id: '1419055412' } [20/08/2024, 09:08:22] [MyChairOnDwnStairsAlmOn] Setting switch to false [20/08/2024, 09:09:05] [Texecom] Area 3 armed [20/08/2024, 09:09:05] [Texecom] Not sending command to alarm for change to state 1 because the state change appears to have come from the alarm itself. [20/08/2024, 09:09:05] [Texecom] Set target state 1 and current state 1 in response to notification from alarm
When the alarm sends an arm/disarm state change notification to the plugin, the current state is set correctly (so you get a HomeKit armed notification for example). But it will say "Disarming..." on the alarm's bubble in the Home app, indicating that the target state of disarmed has not updated. I haven't been able to work out what's causing this, can anyone help please?