Texecom2mqtt: Texecom alarm panel and MQTT integration with HA support

@dchesterton

When I arm the alarm in the Home Assistant dashboard, it arms on the main physical wall panel almost immediately (within 5 seconds). However, when I arm the alarm instead using the physical panel there is a delay of around 60 seconds (to allow time to leave the house).

Is there any way to add a similar delay when arming the alarm using the Home Assistant Alarm Panel Card?

Hi all,

I’ve got the add-on setup and working fine, however when the alarm is armed, the status in HA on the texecom card says Arming - it never changes to Armed. Disarming works fine - everything else works fine.

I’m suspecting it’s because I haven’t mapped the areas as per the configuration steps but it does say this is optional….

Has anyone else experienced this issue? I’d be interested to know if anyone’s running OK with the bare minimal config!

One issue I have is that if I arm the panel using Home Assistant and the Texecom2mqtt add-on via the Home Assistant alarm panel the alarm will arm in 10seconds and ignore the Exit delay and the entry/exit zone. I cannot seem to find any mention of this anywhere and cannot find and setting in Wintex to address this.

Just to follow up - I can confirm this was caused by the mapping not being done, once areas were mapped arming status shows properly.

I think this is expected - when you arm via the texecom cloud app (via smartcom) the same thing happens, there is no exit delay, the panel just arms. The exit delay is to allow a person to exit the area (open, close doors etc).

The arm in 10 seconds - is this the same time as the ‘Exit Settle’ time? You could try changing the ‘Exit Settle’ time to 30 seconds and see, to confirm.

Hi biosmatrix, Yes I tried to change the exit settle time to 30seconds but it has no effect. Still arming in 10secs. I am trying to use the Home Assistant Alarm panel to effectively replace the Texecom keypad, as I have a HA touch panel near the front door, and would like to have the Texecom keypad hidden away. A much cleaner look. So the question is where does the 10 seconds come from?

@lawrencez

I think I’ve found the reason… check option 58 in the global system config options - it’s ‘remote arm instant’. If this isn’t enabled, the exit delays will be used when arming remote which includes smartcom, comIP etc.

@ biosmatrix
That has got me one step closer thanks, Now with option 58 disabled the exit timer is working, but my entry/exit zones now cause the alarm to disarm during arming via HA. This does not happen when using the Texecom keypad. I’m not sure if that was happening before

What does the event log say on the panel when it doesn’t arm?

Its says Exit started, then Exit stopped.

Hmm that’s it? Not much to go on…

Try global system config option 15 - what’s it set to at the moment?

Are you sure you have the zones & attributes setup correctly? (Sounds like you do as works from keypad ok)

Open 15 is disabled. I found by setting each zones attribute 1 to Access it will allow the alarm to arm, but it does not show that the entry/exit zones have been triggered, as it does with the keypad with a different tone to the arming tone

Not really sure where to go from here then…

Option 15:
15 - Hide Exit Errors
If a user tries to arm an area and there are zones activated, the exit
mode will continue (giving a visual and audible indication that there is
a problem).
View Exit Error (Not enabled)
If a user tries to arm an area and there are zones activated, the exit
mode is suspended until all of the zones are secure

If the exit just stops it would indicate something is not secured so it can’t arm properly. Are all guard zones secure when you’ve been trying to arm?