If you go to add a new addon, the click the menu at top right then reload information, it will come up straightaway.
1 Like
Good tip, thanks 
Daniel,
Thanks for your continuing hard work, I really do hope this fixes the app.
Running in Docker
2022-01-11 16:18:03 - INFO: Starting texecom2mqtt v1.2.0 (Node v16.13.0)...
2022-01-11 16:18:03 - INFO: Connected to alarm, sleeping for 2 seconds...
2022-01-11 16:18:05 - DEBUG: Executing serial number command
2022-01-11 16:18:05 - INFO: Connection ready
2022-01-11 16:18:05 - INFO: Logging in to panel
2022-01-11 16:18:05 - INFO: Successfully logged in to panel
2022-01-11 16:18:06 - INFO: Connected to MQTT broker: 192.168.0.80:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0)
2022-01-11 16:18:06 - DEBUG: Publishing to texecom2mqtt/status: online
2022-01-11 16:18:06 - INFO: Serial number: 1184708
2022-01-11 16:18:06 - INFO: Panel: Premier Elite 24 (V5.02.01LS1)
2022-01-11 16:18:06 - INFO: Fetched Area A: House Alarm
2022-01-11 16:18:06 - INFO: Fetched Area B: Area B
Regards,
This is fantastic daern, thank you
Just ordered my Raspberry Pi 4, I’m away from next week, returning at the start of Feb, when I will give this a go!
Will let you know how I get on.
Hi Daniel,
Just caught this error, caused a C1E error on the panel and sensors became unavailable briefly.
Had to manually clear the panel fault
2022-01-12T05:44:03.780038007Z 2022-01-12 05:44:03 - INFO: LOUNGE REAR Motion Sensor status changed to Active
2022-01-12T05:44:03.780270309Z 2022-01-12 05:44:03 - DEBUG: Publishing to texecom2mqtt/zone/lounge_rear_motion_sensor: {"name":"LOUNGE REAR Motion Sensor","number":3,"areas":["A"],"status":1,"type":"Guard"}
2022-01-12T05:44:04.731590885Z 2022-01-12 05:44:04 - PANEL: Output state changed digi: 235
2022-01-12T05:44:07.520111830Z 2022-01-12 05:44:07 - DEBUG: Updating system power...
2022-01-12T05:44:07.784910985Z /snapshot/app/dist/texecom/texecom.js:79
2022-01-12T05:44:07.784976016Z throw new Error(`Unexpected start, expected 't', got 0x${headerStart.toString(16)}`);
2022-01-12T05:44:07.784990826Z ^
2022-01-12T05:44:07.785004602Z
2022-01-12T05:44:07.785017976Z Error: Unexpected start, expected 't', got 0x0
2022-01-12T05:44:07.785031400Z at Texecom.parseBuffer (/snapshot/app/dist/texecom/texecom.js:79:19)
2022-01-12T05:44:07.785044858Z at Socket.<anonymous> (/snapshot/app/dist/texecom/texecom.js:32:18)
2022-01-12T05:44:07.785058800Z at Socket.emit (node:events:390:28)
2022-01-12T05:44:07.785072320Z at addChunk (node:internal/streams/readable:315:12)
2022-01-12T05:44:07.785085794Z at readableAddChunk (node:internal/streams/readable:289:9)
2022-01-12T05:44:07.785099069Z at Socket.Readable.push (node:internal/streams/readable:228:10)
2022-01-12T05:44:07.785112128Z at TCP.onStreamRead (node:internal/stream_base_commons:199:23)
2022-01-12T05:44:09.648120728Z 2022-01-12 05:44:09 - INFO: Starting texecom2mqtt v1.2.0 (Node v16.13.0)...
2022-01-12T05:44:09.657272298Z 2022-01-12 05:44:09 - INFO: Connected to alarm, sleeping for 2 seconds...
2022-01-12T05:44:11.662749334Z 2022-01-12 05:44:11 - DEBUG: Executing serial number command
2022-01-12T05:44:11.683031466Z 2022-01-12 05:44:11 - INFO: Connection ready
2022-01-12T05:44:11.684504208Z 2022-01-12 05:44:11 - INFO: Logging in to panel
2022-01-12T05:44:12.026621795Z /snapshot/app/dist/texecom/texecom.js:79
2022-01-12T05:44:12.026705598Z throw new Error(`Unexpected start, expected 't', got 0x${headerStart.toString(16)}`);
2022-01-12T05:44:12.026734664Z ^
2022-01-12T05:44:12.026761345Z
2022-01-12T05:44:12.026787876Z Error: Unexpected start, expected 't', got 0x41
2022-01-12T05:44:12.026814531Z at Texecom.parseBuffer (/snapshot/app/dist/texecom/texecom.js:79:19)
2022-01-12T05:44:12.026840994Z at Socket.<anonymous> (/snapshot/app/dist/texecom/texecom.js:32:18)
2022-01-12T05:44:12.026868699Z at Socket.emit (node:events:390:28)
2022-01-12T05:44:12.026936827Z at addChunk (node:internal/streams/readable:315:12)
2022-01-12T05:44:12.026964454Z at readableAddChunk (node:internal/streams/readable:289:9)
2022-01-12T05:44:12.026990634Z at Socket.Readable.push (node:internal/streams/readable:228:10)
2022-01-12T05:44:12.027016991Z at TCP.onStreamRead (node:internal/stream_base_commons:199:23)
2022-01-12T05:44:14.302550064Z 2022-01-12 05:44:14 - INFO: Starting texecom2mqtt v1.2.0 (Node v16.13.0)...
2022-01-12T05:44:14.312048648Z 2022-01-12 05:44:14 - INFO: Connected to alarm, sleeping for 2 seconds...
2022-01-12T05:44:16.318587662Z 2022-01-12 05:44:16 - DEBUG: Executing serial number command
2022-01-12T05:44:16.650709923Z 2022-01-12 05:44:16 - ERROR: Could not fetch serial number
2022-01-12T05:45:29.725569210Z 2022-01-12 05:45:29 - INFO: Panel connection timed out
2022-01-12T05:45:29.728472156Z 2022-01-12 05:45:29 - DEBUG: Closing connection to panel
2022-01-12T05:45:29.732290364Z 2022-01-12 05:45:29 - DEBUG: Closed connection to panel
2022-01-12T05:45:29.763978859Z 2022-01-12 05:45:29 - ERROR: read ECONNRESET
2022-01-12T05:45:29.765296392Z 2022-01-12 05:45:29 - DEBUG: Panel socket closed
2022-01-12T05:45:29.766208162Z 2022-01-12 05:45:29 - INFO: Panel disconnected, exiting now
2022-01-12T05:45:31.603859858Z 2022-01-12 05:45:31 - INFO: Starting texecom2mqtt v1.2.0 (Node v16.13.0)...
2022-01-12T05:45:31.613120620Z 2022-01-12 05:45:31 - INFO: Connected to alarm, sleeping for 2 seconds...
2022-01-12T05:45:33.620529437Z 2022-01-12 05:45:33 - DEBUG: Executing serial number command
2022-01-12T05:45:33.651708361Z 2022-01-12 05:45:33 - INFO: Connection ready
2022-01-12T05:45:33.652099008Z 2022-01-12 05:45:33 - INFO: Logging in to panel
2022-01-12T05:45:33.969188720Z 2022-01-12 05:45:33 - INFO: Successfully logged in to panel
2022-01-12T05:45:34.076656637Z 2022-01-12 05:45:34 - INFO: Connected to MQTT broker: 192.168.0.80:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0)
2022-01-12T05:45:34.077784280Z 2022-01-12 05:45:34 - DEBUG: Publishing to texecom2mqtt/status: online
2022-01-12T05:45:34.080485107Z 2022-01-12 05:45:34 - INFO: Serial number: 1184708
2022-01-12T05:45:34.457393016Z 2022-01-12 05:45:34 - INFO: Panel: Premier Elite 24 (V5.02.01LS1)
2022-01-12T05:45:34.841947575Z 2022-01-12 05:45:34 - INFO: Fetched Area A: House Alarm
2022-01-12T05:45:34.842584161Z 2022-01-12 05:45:34 - INFO: Fetched Area B: Area B
Hi Daniel,
Thank you for adding the groupType field to the texecom2mqtt/log object.
That gives me the information that I need to get Home Assistant to send the messages to the app which would have been sent by Texecom if I wasn’t using the IP connection for Home Assistant.
I notice that when the group=0 from the panel then no groupType is sent to MQTT. Perhaps this is intentional, it isn’t a problem as I will know that if the groupType is missing then the value is zero.
I didn’t get on very well with testing last night as my WiFi connection to the panel seemed a bit dodgy and I wasn’t getting all of the messages that were being written to the log (Texecom2mqqt wasn’t receiving the messages, so couldn’t write them to MQTT). I’ll do some more testing tonight when I might have a more reliable WiFi connection.
I also notice that MQTT Explorer doesn’t show the texecom2mqtt/log entries. Perhaps they only exist briefly? I can see the texecom2mqtt/zone and texecom2mqtt/area entries so I think that I have MQTT Explorer set up correctly. Any ideas?
this worked, thanks.
The UDL Lockout kept coming back though after 10 minutes or so, which i now understand is likely down to me changing the UDL code (possibly as long as a year ago), and not ‘re-connecting’ to the SmartCom. i had a ‘planned power outage’ in November, which i think is what actually triggered this to be an issue (when the persistent UDL Lockout started)
This thread on the Texecom forum hints at this issue: Log In - Texecom Installer Forum
Anyway, all working now. thanks for the help. Sorry to get a bit OT with the above, but in my mind it’s related.
Thanks for letting me know. That’s a bug and has now been fixed.
By default, log messages are not set to retain so you will only see the messages in MQTT Explorer if you have it open at the time the message is sent. You can set the MQTT retain_log config entry to true to enable retain on these messages.
That looks like an issue with the panel, rather than being caused by the app. The Unexpected start, expected 't' error there is quite common and is a corrupt message from the panel. Unfortunately it’s a known issue which Texecom are aware of.
I occasionally get “ATS Path Fault” and “COM2 Fault” logged after using this integration, anyone know how to stop that?
Also, I’m seeing the container not shut down (and thus not get automatically restarted) on a failure to fetch serial number which I think is new? It gets stuck here:
2022-01-12 14:01:57 - INFO: Starting texecom2mqtt v1.2.1 (Node v16.13.0)...
2022-01-12 14:01:57 - INFO: Connected to alarm, sleeping for 2 seconds...
2022-01-12 14:01:59 - ERROR: Could not fetch serial number
It does that if I click ‘Restart’. So I always click Stop, wait a few seconds, then Start.
1 Like
Yep, this is a new bug. I’ve pushed a new version which will shut down the container if it happens.
2 Likes
A new feature I’ve added recently which I haven’t mentioned on here is cache support for zones/areas. It should speed up start time to a few seconds. This will be particularly useful for those with bigger panels such as the Elite 640 where traversing all the zones on startup can take a few minutes.
You can enable it by adding cache: true to your config file. The next time the app is run it will save the data to a cache file and then re-use it in subsequent runs instead of fetching the data from the panel.
Note: if you update the zones/areas on your panel you’ll need to clear the cache by turning it off and on again or deleting the container.
2 Likes
Hey Daniel, thanks for all your effort, maintenance and development of such a fantastic add-on.
Quick question - is it possible to trigger the siren via home assistant? eg using non-texecom sensors to trip the alarm.
Thanks, and sorry if that’s been answered somewhere else
1 Like
Hi all, great work Daniel, I keep seeing this banded about, and whilst I am familiar with Texecom Panels I am not familiar with HA so be gentle.
-
My understanding is I need a comip/comwifi module or at least a smart com that is not using the comip component for sending messages out to an ARC or the Texecom servers for Texecom connect?
-
Need a minimum of Version 4 Elite panel firmware, although we should all be on 5 now.
3.Uses the texecom connect protocol (Elite panels) which is an updated version of the simple protocol that was used on the Premier series 48 and above.
- This is a module that bolts on to HA, rather than being stand alone?
- This can integrate with otherthings based on whats integrated onto the pi unit?
Okay so i can load this onto a raspberry pi4?, but whats the minimum I can use? (see everywhere i have checked are out of stock)
Is there any videos to explain how HA works.
Thanks
Thank you Daniel, it works perfectly now.
Ah, yes, I had missed that config entry, that also works perfectly thank you.
Texecom2mqtt version 1.2.3 has now been running without any issues for 12 hours. Thank you for all your work on this.
Yes to all of the above.
I’ve no idea what the minimum Pi version is, I’m running HA on a Pi 4. I guess that it would work on an older version, just a bit more slowly.
I’m like you, years of experience with Texecom panels and new to Home Assistant a couple of weeks ago. The learning curve for HA is pretty steep and it can be frustrating at times because one small mistake in a config file can stop the whole thing from working and the documentation assumes that you already know a lot about it. Lots of searches on the internet eventually got my problems solved.
Hi, I am currently running firmware V5.02.01LS1, I see V5_06_00 is available.
Is it worth me updating it? I would have to buy the interface and cable so just wondering if it will fix the problem?
Regards,
If you’ve got a SmartCom you can sign up for a cloud account and do it online. I did mine last week. Needs to be an installer cloud account, rather than a user account (as required for the connect v2 App).