[Texecom] Wintex doesn't full arm, only part arm.

[ani0405]

I'm using a Serial TTL to Ethernet adapter (not the official COM IP) and for some reason when I punch the code in the Wintex digital Keypad and hit yes to fully arm, it only goes to Part Armed. My Baud Rate is set to 19200 and I'm using 8 Data Bits and 2 Stop Bits so not sure what I'm doing wrong.

If it helps, when I try to arm using the Home Assistant Texecom2MQTT add-on, it arms but I get this error in the logs and the Home Assistant side hangs on "Arming":
Unexpected start, expected 't', got 0x78
sometimes it says
Unexpected start, expected 't', got 0x29

Thanks in advance.

 

[secureiam]

so you are connecting via the usbcom lead with wintex and using the HA integration?

 

[secureiam]

what is displayed in the event log?

 

[ani0405]

I'm using the Com Port 1 on the Panel and it's configured to "Nothing Fitted" in the UDL options. I'm following a guide on youtube by Cameron Gray and he did the same.

Edit: This is all via Wintex. I want to make sure it works there first before trying anything using HA.

This is what the log says, even though I selected to fully arm and not part arm.

 

[sparkymarka]

Does it set normally from keypad ? Do you have …auto part enabled….if so disable it …

 

[ani0405]

Thank you I wasn't aware of this functionality so that seems to have fixed it from the Wintex side. As for Home Assistant, I'm now getting this error:
ERROR: Corrupt response from panel: Unexpected start, expected 't', got 0x80

I am not connected to Wintex simultaneously. It doesn't seem to hang on "Arming" anymore but when this error comes up it causes a re-connection attempt to the panel.

I've been arming and disarming the last few minutes and there are occasions where if the error appears just before I arm then it doesn't work due to the HA add-on being offline.

 

[secureiam]

I see its been addressed, the event log clearly says the system has been part armed and that this was done remotely looks like it was instantly too.

The wintex keypad doesn't have a physical address so it functionality cant be changed unlike a physical keypad. From memory it acts as though it is assigned to Area A only.
Arming modes change how the panel responds.
So instant arm, arms instantly
Timed arms based on the exit timer expiring
Entry exit arms via the entry/exit door being opened and closed after the exit has started.

There are other options but less commonly used.

auto part arm part arms the system if it doesn't see the entry exit door go open and closed for the duration of the exit timer, rarely used these days.
So looks in this case as arming mode set to instant arm.

I cant speak for HA integration although I have tested it and had no issues

You cant use a comport connection for more than one thing at once reliably.

There are users on here using the integration regularly but don't know how often they are lurking around and you my want to start a specific thread on HA integration so it may alert them, or try the automation group.