Texecom2mqtt: Texecom alarm panel and MQTT integration with HA support

Thanks Daniel. Really appreciate this release.

Is there a requirement or recommendation for any specific Texecom panel firmware for maximum stability? My own is Premier Elite 48 (V5.04.01LS1) and I’ve always held back updating it on the basis that, even allowing for the odd add-on failure, it more or less worked well most of the time. What are you running on your own panel?

One thing I’m seeing that I wasn’t seeing on the old version is repeated re-securing of zones:

2025-02-25 08:01:12 - INFO: Updating all zone states...
2025-02-25 08:01:12 - INFO: Updating all area states...
2025-02-25 08:01:12 - INFO: Application ready
2025-02-25 08:02:23 - INFO: Dining Room status changed to Active
2025-02-25 08:02:27 - INFO: Dining Room status changed to Secure
2025-02-25 08:02:27 - INFO: Dining Room status changed to Secure
2025-02-25 08:02:27 - INFO: Dining Room status changed to Secure
2025-02-25 08:02:27 - INFO: Dining Room status changed to Secure
2025-02-25 08:02:27 - INFO: Dining Room status changed to Secure
2025-02-25 08:02:27 - INFO: Dining Room status changed to Secure
2025-02-25 08:07:51 - INFO: Dining Room status changed to Active
2025-02-25 08:07:53 - INFO: Dining Room status changed to Secure

It’s a bit anecdotal, but a quick scroll back through the log for the previous version showed a more expected alternate between states:

2025-02-25 07:58:17 - INFO: Dining Room status changed to Active
2025-02-25 07:58:18 - INFO: Dining Room status changed to Secure
2025-02-25 07:59:00 - INFO: Dining Room status changed to Active
2025-02-25 07:59:02 - INFO: Dining Room status changed to Secure

…and I couldn’t see any examples of it repeatedly sending the same state. Is this expected behaviour? FWIW, these additional states don’t appear in the HA entity history so I’d doubt that they would cause any issues (for me anyway).

Thanks for finding time to come back to this… it’s super appreciated.

Number 2 is a game changer!

No problem!

I’m running Premier Elite 24 (V5.02.01LS1) but it should work on any version v4 or higher. Obviously I can only test on this panel though and there’s 100’s of variations of panel size + firmware + config setup, so the closer you are to my setup the better I guess?

The re-securing of zones is not expected behaviour and it is a little odd to be getting that many updates. Is it happening every time? Could you set the log level to ‘debug’ and send the debug log when it happens?

Thanks Daniel, sounds like I’m in the right area, firmware-wise.

Regarding the odd log entries, I’ll have a play a bit more when I get back home later this week. I’ve just applied the latest 1.3.1 update and it didn’t repeat the odd behaviour on startup, but I’ll wade back through the logs to see if there are any more occurrences and, if necessary, I will try to reproduce it.

I have a Premier Elite 24 and a SmartCom connection. Texecom firmware version is 5.06.00LS1, SmartCom version is 04.01.03.

I only operate my Texecom using this excellent Home Assistant add-on or the physical keypad (I do not use the Texecom iOS app)

Once in a while - maybe every few weeks/months - I get a COM1 fault show on my Texecom keypad. It’s very annoying as to reset this alert I think I need to disconnect the alarm from the mains and battery power so I can force a reboot of the Smartcom.

I think I have disabled Texecom Connect in ARC 1 Protocol of the engineer settings and also block the SmartCom from the internet.

Two questions:

  1. Any ideas why I get this COM1 fault and how I can stop it happening?
  2. Is there a quicker way to clear the COM1 fault if and when it appears?

Thanks

If the alarm is activated - does disarming in HA stop it, and does it reset - or is it necessary to physically go to a keypad and reset. So if it is activated by a false alarm when I am away from home, can I turn the alarm off and re-arm from HA? Thanks

Still hoping for a response to this question above.

Also - in Home Assistant when I click on the entity it shows arming option is dont use - I can hide them in the alarm card, but if I click on the armed status it opens up the full list. Is there a way to remove unused arming options?

Thanks

Hi all, I have read through much of the 1000 or so posts here, but just wanted to check and get input.

I have a Premier Elite 24 panel and am an existing Home Assistant user, including running the Mosquitto MQTT broker.

I want to buy a communication module, to connect the alarm to HA through this add-on. I’m trying to choose between the ComIP and the Smartcom.

I have no interest in using the Texecom app, or connecting to any ARC, so I assumed I would just get the ComIP.

However price wise the Smartcom seems considerably cheaper (around for £75-80 vs £125-160 for the ComIP).

Any benefit of one over the other for this scenario? I understand the need for a dedicated module, so either one would be for HA only.

Personal opinion but I would go for the comip. I know it is £40/£50 more but it feels like the better solution - the Smartcom would work but its a more complex device as it is designed to connect to Texecom cloud primarily, not saying that it cant be used for pure ip comms though.

It will also take up two com ports which you may not need now but maybe in the future, it is also a seperate unit that has to be mounted and secured.

The ease of the comip, it being integrated into the alarm panel box and requiring minimal setup makes it a winner for me. Its simple and it works.

1 Like

I’m using a ComIP for HA integration. it’s installed int he alarm enclosure and is rock solid in my experience.
you can pick them up 2nd hand form ebay for £60 ish
(i also have a SmartCom installed that i use for Wintex and the Texecom app)

1 Like

Thanks for the input @MSE and @matt-uk you both confirmed what I think I wanted to hear, go for the ComIP. Tidier install in the panel, and a better dedicated device for this add-on.

I ordered one yesterday (couldn’t find any ebay bargains unfortunately).

Should keep me busy this weekend.

Your new ComIP does not look to be configured. Depending on how it’s physically connected in the panel, you should have two ComIPs configured:

In my case, Com1 and Com2 are the SmartCom (it uses two ports), and Com3 is the dedicated ComIP. Each has its own network connection (i.e. two physical network cables into the panel) and its own IP address. In my case, the dedicated ComIP IP address is solely used for HA and the SmartCom is used for Wintex and Texecom Cloud (which is typically disabled for me as I only use it when I need a firmware update).

You’ll need to follow the instructions to provision the new ComIP on the panel and discover its IP address, then use this for the HA connection. It’s not plug and play - you need to tell the panel that it’s there!

I’ve installed a comip module and built texecom2mqtt.

I can see it’s connecting to the panel and retrieving data okay. The logs show data being published to Mosquito MQTT.

2025-06-29 19:32:03 - DEBUG: Publishing to texecom2mqtt/config: '{"version":"1.3.1","log_level":"debug","model":"Premier Elite 24","firmware_version":"V6.05.03LS1","serial_number":"removed"}' (retain: true)

However, when I view MQTT the device doesn’t show:

I only see an existing unrelated device there.

Here’s my config:

log: info
cache: false
texecom:
  host: 192.168.1.50
  udl_password: "removed"
  port: 10001
mqtt:
  host: mqtt://core-mosquitto
  username: mqtt
  password: removed
  client_id: texecom2mqtt

homeassistant:
  discovery: true

Any tips on how to troubleshoot this further?

I’m struggling with this too. As far as I can work out, disarming via HA does not stop a triggered alarm. As I’ve ditched the Texecom App to free up SmartCom for HA, I can only cancel and reset an alarm event via the on-site panel. I’ve disabled any reporting out via Wintex too, thinking that the panel may be trying to comms out and hogging SmartCom.

Assume there must be a way of using HA in place of the Texecom app, including dealing with alarm triggers? what have I missed?

Many thanks

Hi,

I’m having a problem with areas and i cant figure out why.

I have 2 areas, and my config yaml is as follows-

In the texecom2mqtt log i can see that the areas are fetched OK:

image

But then the last entry on the log gives me an error about my config and an ‘Unknown area’:

image

Can anyone spot what the issue might be here?

Thanks,
Joel.

Hi Steve, I know this is old, but did you resolve this issue, as I am now getting the same error

Hopefully there isn’t a blatantly obvious piece of documentation I’m missing here. Apologies if so

Is it possible to arm and disarm the alarm from within HA using the user codes programmed into the panel, or is the only way to do it via the access code you define in the config yaml?

Is there any difference in terms of HA functionality if the ComIP or SmartCom is used?
SmartCom is obivously way cheaper.

No but will give you issues if using with Texecom cloud at the same time.

I seem to have an issue, I’ve installed an additional COMIP Module in COM3, I’m able to PING the IP Address I can also connect to WINTEX via the COM3 IP Address and communicate with the panel as expected.

But I’m getting the following Error when trying to connect using this Addon, Connecting using COM2 IP Address which is used for SmartCom on port 10001 is working fine, but this disables the app communication.

COM2 IP Module is running on 192.168.0.34:10001
COM3 IP Module is running on 192.168.0.35:10002

ERROR: Could not fetch serial number when using COM3 details, Sucessfull connection when using COM2 details;

log: debug
cache: false
texecom:
  host: 192.168.0.35
  udl_password: "*****"
  port: 10002
mqtt:
  host: core-mosquitto
  username: hamqtt
  password: ****
areas:
  - id: A
    code_arm_required: false
    code_disarm_required: true
    full_arm: armed_away
    part_arm_1: armed_night
    code: "****"
  - id: B
    code_arm_required: false
    code_disarm_required: true
    full_arm: armed_home
    code: "****"
zones: []
homeassistant:
  discovery: true

Can anyone help? Here is log file.;

2025-09-25 15:07:52 - INFO: Starting texecom2mqtt v1.3.1 (Node v23.7.0)...

2025-09-25 15:07:52 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0)

2025-09-25 15:07:52 - INFO: Connecting to panel...

2025-09-25 15:07:52 - DEBUG: Publishing to texecom2mqtt/status: 'online' (retain: true)

2025-09-25 15:07:52 - INFO: Connected to alarm, sleeping for 2 seconds...

2025-09-25 15:07:54 - INFO: Fetching serial number

2025-09-25 15:07:54 - DEBUG: Executing serial number command

2025-09-25 15:07:54 - ERROR: Could not fetch serial number

2025-09-25 15:07:54 - DEBUG: Publishing to texecom2mqtt/status: 'offline' (retain: true)

2025-09-25 15:07:54 - DEBUG: Disconnecting from panel

2025-09-25 15:07:54 - INFO: Closing connection to panel...

2025-09-25 15:07:56 - INFO: Closed connection to panel

2025-09-25 15:07:56 - DEBUG: Publishing to texecom2mqtt/status: 'offline' (retain: true)

2025-09-25 15:07:56 - INFO: Re-connecting to panel in 10s...

I’m falling at the first hurdle:

addon installed, but won’t start, I get the following message:

Missing option ‘homeassistant’ in root in texecom2mqtt (c15a2434_texecom2mqtt).

in a pop-up box.

I get the option to ‘edit config’ on a button, but it does nothing. I can’t seem to find any config files either…?

Already running Mosquito MQTT sucessfully for another integration, so I’m not sure what else to look for.

Has anyone got any thoughts on where I should be looking next…?

ta