Texecom2MQTT crashes on alarm activation
Opened this issue · 5 comments
Describe the bug
Whenever the alarm is triggered (and on some other seemingly random occasions), Texecom gets an error in the log and crashes.
Application version
Starting texecom2mqtt v1.2.3 (Node v16.13.0)
Texecom alarm type
Premier Elite 24, Firmware: V6.01.11LS1
Home Assistant version
2022.6.7
Debug log
ERROR: Corrupt response from panel: Unexpected start, expected 't', got 0x98
Same issue here
I thought this might be because I'm using both the phone app and the home assistant integration - however i've completed deleted the phone app connection (from the cloud dashboard too) and it's still doing it. Has anyone else managed to resolve this?
Did you remove the configuration from the alarm configuration itself? Pretty sure that if this is still present, regardless of app configuration, the alarm will continue to shout out on the SmartCom to the Texecom Cloud service, and this will certainly break this add-on due to the way the serial to ethernet adapters work.
Perhaps not actually - although, i'm struggling to figure out how to do that from the instruction manual.
This is the instructions to configure it:
https://texecom-live.s3.eu-west-2.amazonaws.com/wp-content/uploads/2022/03/29135511/Smartcom-Installation-Guide-INS760EN-7.pdf
You need the com port setup and UDL password in 7.1, but absolutely don't want the Texecom setup in 7.2. I would suggest poking through the menus and attempt to undo the settings from 7.2 while retaining those in 7.1.
My wintex configuration looks like this and you might find it easier to reconfigure using this rather than the menus - I know I do!
(all ARCs are set to "disabled")
This setup is normal for a SmartCom and ComIP installed - the smartcom uses Com1 and Com2 (Com2 has the smartcom IP address) and Com3 is the ComIP which, for me, is dedicated to HA. I connect Wintex to Com2 IP address and this was also the one that talks off to Texecom Cloud when it was configured. (Note: If you're using Wintex, make sure you have texecom2mqtt stopped as the two will certainly interfere if using a single ComIP / Smartcom!)