No I don’t have the SmartCom, I have seen on xbxy someone selling compatible interface for £27.90, not bad including USB lead.
May give it a go
2022-01-13 12:15:32 - INFO: Panel: Premier Elite 24 (V5.02.01LS1)
I run this firmware with zero problems, so aside from variances/specific bugs for your setup I would say it’s not firmware related?
Given others with issues, I’m reluctant/see no need to update 
Slightly later here: Elite 48 V5.04.01 LS1, but like you, I’m not having issues with the alarm itself that would make me consider updating right now. The alarm has been rock-solid stable since day 1, so have no need to risk compromising this.
Now if they fixed some of the issues that Daniel referred to above, I might be tempted to upgrade, but for now…it’s staying as it is!
I am going to go ahead with the upgrade, ordered the interface cable.
I will be the Guinea pig for the group and will share my findings / issues as they may or hopefully not arise… 
Getting a bit offtopic… (feel free to message me?) - I am still on V4.02.01LS1 on my Premier Elite 24… can I do a cloud upgrade? Is it easy to get an installer cloud account (I have a regular one)
You need to be on 5.x to do a cloud upgrade. That came up when I can’t Texecom about the cloud account.
I went from 3 to 5.06 on a 640 panel about a month ago, purely to start using Smartcom and this plugin. All good.
Just wondered if it is possible to control the expander outputs via HA switches or service calls?
I recognise the name and thanks for replying, how much memory, not that it matters right now as I would need to get hold of one and everywhere is out it would appear. Like most programming I suspect, then finding what you have missed or added or even mistyped.
No doubt i will be back once i have a pi4 and see how I get on.
I don’t believe so now (at least it’s not in the documentation), but I would definitely second this as a feature request!
Hi Daniel,
I am experiencing a problem with the latest version where the state of the MQTT sensors does not change when the Texecom Alarm sensor state changes. This is a snippet from the log when the problem occurs:
2022-01-14 16:34:44 - PANEL: Monitored Alarm (Areas: A; Parameter: 4; Group: 4)
2022-01-14 16:34:44 - DEBUG: Publishing to texecom2mqtt/log: {"type":"MonitoredAlarm","description":"Monitored Alarm","timestamp":"2022-01-14T16:34:44Z","areas":["A"],"parameter":4,"groupType":4}
2022-01-14 16:34:45 - PANEL: Output state changed custom_3: 6
2022-01-14 16:34:46 - PANEL: Output state changed digi: 15
2022-01-14 16:35:03 - DEBUG: Updating system power...
2022-01-14 16:35:03 - DEBUG: Publishing to texecom2mqtt/status: online
2022-01-14 16:35:03 - DEBUG: Publishing to texecom2mqtt/power: {"battery_charging_current":0,"battery_voltage":13.56,"panel_current":333,"panel_voltage":13.56}
The panel passes a Monitored Alarm to Texecom2mqtt and Texecom2mqtt publishes it to the MQTT log correctly, but does not publish it to the MQTT zone and the binary sensor in Home Assistant does not change state.
This was working previously. It might have stopped working when I updated to version 1.2.3
Hi Paul, the app doesn’t do anything special with that log event and nothing has changed regarding that part of the code so I don’t think this is a new bug. What happens to generate that log event and what are you expecting the app to do here?
Unfortunately it’s not possible at the moment. The API does support it and it is a feature I want to add at some point but it will be a fair amount of work and I can’t commit to it at the moment.
Thanks for the update. Understood. As an alternative, Outputs can mimic inputs, so is there a way to trigger a zone through the API? Or, is there a way to change the wiring setting for a zone? Alternating between Normally Open and Normally Closed would trigger the zone.
Something is missing.
In the alarm a zone changed state from open to closed. This change of zone state also wrote a log event in the panel log.
The data received by texecom2mqtt only included the log event, texecom2mqqt never received the change of zone state.
This morning is even worse, texecom2mqtt didn’t receive the log event or the change of zone state it only received:
2022-01-15 08:20:09 - PANEL: Output state changed custom_3: 14
2022-01-15 08:20:10 - PANEL: Output state changed digi: 31
and then when back to updating the system power.
Perhaps the problem is with the panel as texecom2mqtt can obviously only process events that it receives. I wonder if the 30 second system power updates are overwhelming the panel and causing it not to send zone and log updates reliably.
I will investigate further. I will see if I can work out how to revert to an earlier version of texecom2mqtt and see if anything changes but I am very new to Home Assistant and completely out of my depth with it at the moment.
Hi Mark, its not to bad, i have updated lots with the flasher cable. just follow the instructions
Just done it, so far so good 
2022-01-15 13:32:52 - INFO: Panel: Premier Elite 24 (V5.06.00LS1)
2022-01-15 13:32:52 - INFO: Fetched Area A: House Alarm
Hi Daniel,
After more testing I have concluded that there is nothing wrong with texecom2mqtt. The problem lies with the Texecom firmware.
The zone that I was having problems with was a Latchkey type with the Monitored Only attribute selected. Texecom do not publish changes for this zone type over the Connect protocol so there is no way for texecom2mqtt to pick up the change of zone state.
The reason that I believed it was working previously was because, during testing, I repeatedly restarted texecom2mqtt. This causes texecom2mqtt to read the current zone state from the panel and gave the appearance that the zone status was changing.
Sorry to have bothered you with a non-problem.
Just a quick note to say thank you to @dchesterton for resolving the connectivity issues. A week has now passed and I’ve not had a single, impactful problem with the add-on over this time, which would previously have been unheard of, so things looking much better now!
Absolutely fantastic work, and huge thanks to Daniel and everyone else who helped provide diagnostic information to help resolve it. 
1 Like
Thanks Mathew, I hadn’t seen that before. Unfortunately it hasn’t made any difference to my issue, I’m still getting the below when trying to start up.
2022-01-30 14:25:21 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2022-01-30 14:25:21 - INFO: Connected to alarm, sleeping for 2 seconds…
2022-01-30 14:25:23 - DEBUG: Executing serial number command
2022-01-30 14:25:23 - INFO: Connection ready
2022-01-30 14:25:23 - INFO: Logging in to panel
2022-01-30 14:25:24 - ERROR: Could not log in to panel
2022-01-30 14:25:24 - DEBUG: Closing connection to panel
2022-01-30 14:25:24 - DEBUG: Closed connection to panel
I’m at a loss to understand why it doesn’t connect, Wintex works on both my SmartCom and my ComWIFI, I have tried changing the UDL, reset the com ports etc. but still no joy.