Repository navigation
Replies: 2 comments 2 replies
|
Welcome, and thanks for including the diagnostics: it's the first report from V5.02 firmware. Night or Away while arming: your diagnostics show why it can't tell yet. When you set Night (Part Arm 2) at 10:12:55 and then Away at 10:13:13, the panel sent the same two messages at the start of each exit delay: area 1 in exit and Exit Started from keypad 1. It only says which mode it was once the area has armed (Part Arm 2 or Quick Arm). The panel's status flags should tell them apart, though: on my panel a Part Arming flag comes on during a part arm's exit delay. I'm going to try reading the flags as soon as an exit delay starts, and adding the mode it's arming to as an attribute on the alarm, for automations. I'll post here when it's ready to try. The alarm log: reading the panel's log is on the list, mainly to catch up on what happened while Home Assistant was disconnected. For what's happening now, the alarm's activity list (and the Logbook) already shows each arm and disarm, who did it at the keypad, alarms (naming the zone), tampers and faults, and the The unknown message: thanks. It came when the Front Door opened during the second exit delay: a short message ( PS: from v0.2.7, diagnostics also hide the names given to keypad users. One user's name shows in your post, in case you'd like to edit it out. |
|
v0.2.8 is out with this. While the alarm shows Arming…, it now has an triggers:
- trigger: state
entity_id: alarm_control_panel.texecom_house # your alarm's entity ID
attribute: arming_to
to: armed_nightAs your diagnostics showed, the panel's messages at the start of the exit delay are the same for every mode. Its status flags aren't: Part Arming plus Part Arm 1/2/3 for a part arm, and Full Armed/Exit for a full arm. So the integration reads them as soon as the exit delay starts. On my panel (V6.05) it knew within about 2 seconds. Yours is V5.02, so I'd love to hear whether it works there too. If |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Thanks for this integration, I've been using texecom2mqtt for a long time, but have just found this and switched.
Is it possible to tell the difference between "arming..." that is going to become Night.
and arming.... that is going to become Away.
Could you expose the "alarm log" and would that help ?
Any other way you could tell?
It would be useful for automations.
Also my intergration said it had a new kind of message you might want to know about...
message03
All reactions