Texecom2mqtt: Texecom alarm panel and MQTT integration with HA support

marshn · October 5, 2024, 8:57am

Let’s try and narrow this down. One of my test panels is temporarily connected to the Internet. I will DM you the IP address. Port number is 10001 and the UDL PW is 1234.

I can connect to the panel via the Internet with Wintex and the protocol that Texecom2mqtt uses. Firstly see if you can connect using Wintex, then try connecting to it with you instance of Texcom2mqtt.

If those tests are successful then we must be looking at a problem with your panel. If you cannot connect then the problem must be with your Texecom2mqtt.
Let me know when you are done and I will take my test panel offline.

Matt186 · October 5, 2024, 9:20am

Thanks! Replied privately

Matt186 · October 5, 2024, 10:18am

@marshn was extremely generous with their time and gave me access to their private panel. I was able to use connect to their panel using Wintex, however, when I tried in Texecom2MQTT - I received the same errors as I recieved suggesting an issue with HA/Texecom2mqtt rather than panel side:

2024-10-05 10:16:50 - INFO: Logging in to panel
2024-10-05 10:16:50 - ERROR: Could not log in to panel

My config YAML is:

I thought:

texecom:
host: xx.xxx.7.126
udl_password: “1234”
port: 10001

would be enough to connect

Of interest - it gave @marshn the same UDL lockout message (despite UDL being correct).
Unfortunately @marshn doesn’t use Texecom2mqtt themselves so we cannot troubleshoot further.

Matt186 · October 5, 2024, 12:15pm

will stop spamming I promise but this is interesting - when I’m connected to the panel via WinTex at the same time, I get a different error suggesting that Texecom2mqtt can interact with @marshn’s test panel in some way

2024-10-05 12:12:24 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
node:events:368
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED xx.xxx.7.126:10001
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: 'xx.xxx.7.126',
  port: 10001
}
2024-10-05 12:12:29 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
node:events:368
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED 89.240.7.126:10001
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: 'xx.xxx.7.126',
  port: 10001
}

Vasilis_Ad · October 6, 2024, 8:56am

Hi, I need your help with texecom2mqtt

I’m trying to integrate my texecom elite 24 alarm system via ComIP module that I have installed on Com3. I can connect to alarm using Wintex and ComIP without any problem.
I created a user texecom2mqtt and installed and configured texecom2mqtt as in the screenshot
Screenshot 2024-10-06 112637

but I get the error “ERROR: Could not connect to MQTT broker”

Screenshot 2024-10-06 112937

I have read and test all the related previous suggestions on this forum without success.
I’m using mqtt mosquitto broker for frigate add-on only.
Username, password and other mqtt settings have tested and are correct.

What am I missing?

metaljay · October 7, 2024, 6:42pm

what does your comport settings look like?
I find if I leave it as ‘nothing fitted’ it works ok.

I have smart com as port 1, and ComIP as port 2 and then an ESP8266 running ser2net on comport 3 as ‘nothing fitted’ this is what the MQTT plugin connects to

Vasilis_Ad · October 7, 2024, 9:42pm

Currently it is as ComIP. I’ll return home tomorrow and I’ll change it to “nothing fitted”". I will inform you if addon connect to mqtt !

marshn · October 8, 2024, 7:21am

From the logfile that you posted @ Vasilis_Ad your issue is with Texecom2mqtt connecting to the mqtt server, not to the texecom panel. It looks like your panel is configured correctly and the changing the COM port configuration will not help. Is your MQTT server on the same subnet as the instance of Texecom2mqtt? Is there anything in the MQTT server log that would indicate whether a connection is being attempted? The 30 second delay before the ‘Could not connect to MQTT broker’ looks like a networking issue rather than a bad password etc.

@ metaljay is using a direct serial conection to their COM3 port without a COM-IP, so it is appropriate to configure that port as ‘Nothing fitted’. If they had a COM-IP fitted it would not be configured by the panel and they would be unable to connect to it. If a COM-IP is connected to a COM port it has to be configured by the panel, and the appropriate setting is ‘ComIP Module’, with the desired IP address set in the ‘COM-IP Details’ setting.

Vasilis_Ad · October 8, 2024, 1:33pm

@marshn
Both Mosquitto Broker and Texecom2mqtt are add-ons on the same home assistant instance 192.168.88.5 as you can see in the configuration that I posted.
Frigate is running smoothly and I can also connect from anywhere in local network to mqtt using mqtt explorer.
Mosquitto Broker log show except the usual attempts from 172.30.32.2 that happens every 2 mins, an attemt when texecom2mqtt tried to connect:

172.30.32.1:41028 on port 1883.
2024-10-08 16:09:40: Client closed its connection.

What is going wrong?

Update: I reinstalled the addon and start the configuration from scratch. Finally it works!

Thank you!

Matt186 · October 14, 2024, 7:07pm

Hi

Some people would call me stubborn, I consider myself persistent. I’m determined to crack this and hopefully my journey through insanity will be helpful for others.

In my head, the problem is either the panel, my network, the Home Assistant software/config or my Pi.

Panel:

@marshn has kindly lent me his ‘test panel’ which gives exactly the same message when I connect suggesting it is not a panel problem. It would be great if anyone with a working instance of Texecom2mqtt could change their settings to the Test Panel to see if it connects (which would completely exclude a panel issue)

Network:

I thought this was the issue but I used my phone’s hotspot with @marshn’s test panel (as well as my own) and this led to the same error so I think I have excluded that

The PI or the HA sofware:

It would be slightly unusual for it to be a hardware issue given that everything else works. I’ve tried x2 SD cards with the same result. I’m going to exclude the Pi.

I put a vanilla copy of HA onto the Pi then ONLY installed Texecom2mqtt and added config (ip/UDL/port). The MQTT was left blank as I think the connection needs to happen first before the MQTT config. This is where I feel the most likely cause of failure is. It would be great if I could connect to someone else’s panel with a working Texecom2MQTT instance using my pi/HA (obviously with config settings changed to reflect).

TLDR: would anyone with a working instance of Texecom2MQTT be prepared to do some troubleshooting with me?

Thanks!

daern · October 16, 2024, 10:35am

If you and @marshn can give me access to his test panel (need external IP, port and UDL password), I’ll setup a clean texecom2mqtt instance here and will test it using this. I’ll also do a packet capture to see if I can see anything going on compared to my own panel.

One question: Do you know what firmware version any of these panels are running? Could it be that there’s a more recent version that doesn’t work well with this add-on? Mine is: Elite 48 V5.04.01 LS1 and SmartCom V03.03.00 (although I don’t use this smartcom for HA)

Matt186 · October 16, 2024, 10:53am

@marshn has kindly given me permission to share his test panel info privately so I’ll send you a message @daern this pm when I finish work. If you CAN connect to @marshn’s panel and I can’t - the problem is definitely my side (either the pi/HA software).

My panel details:

App version - 2.1.24
Panel Type - Elite 24
Firmware Version - 5.01.03
SmartCom Version - 04.05.01

chrisjcbt · October 16, 2024, 9:38pm

Is there anything I can do to help here? I’ve been trying to get a texecom premier elite 24 working with HA for some time (trying both texecom2mqtt and the HomeBridge addons, using Creston protocol). I would love to be able to compare settings on the wintex side.

Matt186 · October 16, 2024, 10:07pm

With the generous help from @marshn and @daern - I managed to log into my panel.

I’m still scratching my head about what suddenly helped things work because I didn’t change anything!

If I was a betting man - I would say the problem was with the PI/HA install but like I said - I didn’t change anything…

chrisjcbt · October 17, 2024, 7:00am

If there is any chance, can you share some screenshots of the required wintex setup, and if you have comIP and SmartCom or just one or the other (and on which ports). I’m sure the issue is on my panel configuration side. DM me if you prefer. Anything would be really helpful.

Matt186 · October 17, 2024, 8:10am

Hi, I didn’t change the setup from this:

marshn · October 17, 2024, 9:01am

I just have two COM-IPs, one on COM1 and one on COM3. A smartcom may be different, but I have to specify the IP address in the Com-IP details section, see below. I am not sure how the panel would know what IP address to configure the COM-IP with unless it is specified. Maybe 0.0.0.0 means ‘use DHCP’?

Remember that if these setting are changed in Wintex they need to be uploaded to the panel, and in the case of COM-IP module setting the COM-IP needs to be reinitialised with the new settings.

daern · October 17, 2024, 10:45am

Much the same here. I have a SmartCom and a ComIP, so the SmartCom uses COM1 and COM2, the the second ComIP uses COM3:

From the ComIP documentation, if you set the IP address to blank or 0.0.0.0, it will use DHCP. This may differ in SmartCom - I can’t remember:

Pretty sure you need to have encryption disabled against the com port used by texecom2mqtt as it’s not supported, but it’s been a long time since I originally set this up so I can’t remember!

Matt186 · October 18, 2024, 12:31pm

I can see sensors and am having fun automating. Thanks all for the help. @dchesterton - I don’t know whether you check this thread anymore but I’ve bought you a ~~coffee~~ beer - enjoy!

cybergambit · November 26, 2024, 9:37pm

Hi all,

Just in the process of setting up HA from scratch and am on setting up the Texecom Premier Elite. Have got the add on (and already had mosquitto setup and running for Zigbee2MQTT). When starting the texecom2mqtt add on, I get this in the log:

2024-11-26 21:29:18 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
node:events:368
throw er; // Unhandled ‘error’ event
^
Error: connect ECONNREFUSED 192.XXX.X.XXX:10001
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
Emitted ‘error’ event on Socket instance at:
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -111,
code: ‘ECONNREFUSED’,
syscall: ‘connect’,
address: ‘192.XXX.X.XXX’,
port: 10001
}

My configuration page looks like the screenshot (obviously sensitive information replaced with x again).

Apologies if I’m missing something very simple - I’ve tried reading through this thread for my error but can’t understand the issue/solution given (or if it even matches my issue).

Thanks,
CG