So I have managed to Create an account online. and I paid the £7 to configure my system online. I have also been able to add my ComIP via the texecom premier elite comport+ addon as com port 1 and 2 were populated with the smartcom.
can someone please help me how to configure the ComIP in the alarm?
It’ just needs to be configured as “ComIP module”. I would set a fixed IP address for it, so the address doesn’t change (Forcing you to update in Home Assistant)
Yes did that in the cloud configuration and can now see it on my network thanks. seemed quite simple although there are so many settings which i have no idea what they are and thought there has to be more to it
now to figure out how to integrate it to my HA
EDIT: Managed to get this up and running perfectly in HA. I have one question though when mapping areas to the HA Names is it possible to have custom names? as for Part Arm 1 i have it as Bedtime in the connect app and want to have it the same in HA Aslo
This works well for me on the whole, except every few days the add on stops working. I am using the official texecom app on the SmartCom and this add on is running on ComIp. Below is what the log shows when the add on stops running. Any ideas?
2023-01-04 12:59:21 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2023-01-04 12:59:41 - INFO: Connected to alarm, sleeping for 2 seconds…
2023-01-04 12:59:42 - ERROR: read ECONNRESET
2023-01-04 12:59:42 - INFO: Panel disconnected, exiting now
Good Afternoon all,
I’m having an issue where the last_activated_zone is reported as “undefined”.
I think it is an issue with my panel config. But I am getting no joy in working through the documentation for both the panel, the SmartCom, the Communcator or Wintex.
Has anyone experienced something similar?
@dchesterton You are an absolute champion with this, it is even more appreciated than you know!
Hi all, if successfully managed to get this working but only for a limited time.
Following a brief period of success I get the following. Has anyone any pointers as to what might be causing this?
Thanks
Likely the local IP address of your panel has changed and texecom2mqtt is no longer trying to connect to hte panel.
Managed to get this up and running perfectly in HA. I have one question though when mapping areas to the HA Names is it possible to have custom names? as for Part Arm 1 i have it as Bedtime in the connect app and want to have it the same in HA also but at the moment it only allows me to use the HA names such as arm_away, arm_home etc…
No, I don’t believe you can. I also have wanted to do the same, but I had a check of the HA codebase and this was all hard-coded. I admit that I’ve not checked it for a while, so if it’s changed (or if anyone else has a solution) I would certainly be interested!
Update on this: the panel log correctly contains the zone that lead to the alarm activation. So it is just not being pushed to the texecom2mqtt payload.
I am not using any other app connections to the panel (i.e. no texecom connect is setup).
Hi, is it possible to have two separate alarm systems running through HA using this integration? I have two texecom alarms - one in the garage and one in the house. I currently have the garage alarm running through HA using this integration but would like to add the house alarm? Thanks
Perhaps not with HAOS (I don’t think it lets you install multiple copies of the same add-on), but I suspect you could manually deploy two instances in docker with different configurations and this would work, providing the MQTT namespaces don’t overlap. You’d need to configure a unique MQTT prefix in the config and ensure zone and area names were globally unique, but I can’t think why it wouldn’t work.
As an out of interest, why have two separate alarms? You could have a single alarm but run the two buildings autonomously with their own areas, keypads, zones, sounders etc. but still maintain them as a single system (e.g. a garage alarm could trigger all sounders, not just those in the garage) and retain common set/unset processes and a single interface for alerting / notifications. This would have needed a different panel at one end - rather than a matching main panel, you would use a cheaper 8XP (or PSU200XP) as a satellite from the main panel.
Thanks for the reply. That does seem one solution but I’d rather only run one instance of HA. The reason we have two alarms is the house alarm was installed before the garage alarm and the run to the garage is a bit too far for wireless plus it would now be difficult to run cables to the garage. Perhaps in hindsight I would’ve run the cables needed but then again we’ve just added another two rooms on (its a garage and outbuilding really) so I’d be stuck and need more cables.
Hi, thanks for the response. I have ruled this out and still suffering the same issue.
Any other thoughts or pointers anyone may have?
Thanks
When you say this, do you mean “you’ve not set up the app”, or that you’ve explicitly removed the config from the alarm panel itself? There’s quite a bit of confusion over this, but the official app doesn’t actually talk to the panel - it talks to Texecom’s cloud platform. As such, even if the app isn’t installed or configured, if the panel is still set up to talk to Texecom Cloud, it will continue to do so even if there’s no app receiving the messages. This means that at alarm activation, it will try to do two conversations at exactly the same time using the same ComIP / SmartCom, and this will certainly cause one or both to fail.
It’s hard to know exactly what your issue is (after all, it may be something on your internal home network), but this issue of HA conflicting with Texecom Connect seems extremely common and, TBH, I think might be at the root of many of the stability issues reported here.
I added some notes on what to check in the alarm config here:
Thank you for the great project. I use it for several months already. Almost everything work perfectly but I don’t know why sometimes it disconnect from HA.
Today, the status show unavailable at 9:23:05, 9.41:58, 9:46:35, 11:58:28 Now at 12:00. I have no idea why it become unavailable, but some days it happen 0 time.
Sorry to drag this old message up but is this still the best way to send a notification which states which zone triggered the alarm?
Have a look at last_active_zone in the documentation. If you’re using the alarm control panel integration to detect triggered alarms, you’ll need to swap to MQTT. See example here.
Area A status changed to Disarmed - HA shows disarmed
Area A status changed to Armed - HA shows arming
How can I have the ARMED status?
Thank you!
