I wonder if it is worth using Alarmo from HACS? Presume Alarmo works with the Texecom2mqtt add-on and it seems to be more customisable. Anyone have experience with Alarmo and this add-on?
So I tried a different approach - rather than use the Alarm Card I created my own buttons on my main dashboard which shows both arm status and allows me to change the alarm setting. I simply double click the Arm/Disarm option I want and it runs a script to Arm/Disarm as per the button. I can tell the status of the alarm because that is the only icon which is coloured- the others are greyed out until the arm status changes. This seems to work pretty well - snapshot below - you can see in this example the house is currently fully armed.
cards:
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state: arming
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: red
icon: mdi:lightning-bolt
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
hold_action:
action: none
double_tap_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state: unavailable
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: yellow
icon: mdi:alert
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: call-service
service: hassio.addon_start
target: {}
data:
addon: c15a2434_texecom2mqtt
double_tap_action:
action: call-service
service: hassio.addon_start
target: {}
data:
addon: c15a2434_texecom2mqtt
hold_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state: disarmed
card:
type: custom:mushroom-entity-card
icon_color: green
icon: mdi:lock-open-variant
fill_container: true
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
hold_action:
action: none
double_tap_action:
action: navigate
navigation_path: /lovelace/alarm
entity: alarm_control_panel.texecom_home
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state_not: disarmed
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: dark-grey
icon: mdi:lock-open-variant
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
hold_action:
action: none
double_tap_action:
action: call-service
service: script.button_disarm_return_home
target: {}
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state: armed_night
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: orange
icon: mdi:shield-moon
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
double_tap_action:
action: call-service
service: script.button_disarm_return_home
target: {}
hold_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state_not: armed_night
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: dark-grey
icon: mdi:shield-moon
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
double_tap_action:
action: call-service
service: script.button_arm_night
target: {}
hold_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state: armed_away
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: red
icon: mdi:lock
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
double_tap_action:
action: call-service
service: script.button_disarm_return_home
target: {}
hold_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state_not: armed_away
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: dark-grey
icon: mdi:lock
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
double_tap_action:
action: call-service
service: script.button_arm_away
target: {}
hold_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state: armed_custom_bypass
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: red
icon: mdi:garage-lock
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
double_tap_action:
action: call-service
service: script.button_disarm_return_home
target: {}
hold_action:
action: none
- type: conditional
conditions:
- condition: state
entity: alarm_control_panel.texecom_home
state_not: armed_custom_bypass
card:
type: custom:mushroom-entity-card
entity: alarm_control_panel.texecom_home
icon_color: dark-grey
icon: mdi:garage-lock
fill_container: false
layout: horizontal
name: Texecom
primary_info: none
secondary_info: none
tap_action:
action: none
double_tap_action:
action: call-service
service: script.arm_away_exc_garag
target: {}
hold_action:
action: none
view_layout:
position: sidebar
Hi
I have the Texecom Home Assistant Integration working great.
The one thing I would like is the ability to trigger the alarm using the Integration, which I understand is not possible.
Are you able to give instructions to wire up a Shelly 1 to the alarm so I can use the Shelly to trigger the alarm? I have a Premier Elite 24.
Thanks very much!
E
I have had this add on running for 6 months without issue.
I had seen that some have had crashing issues so I run an automation once an hour to restart it.
I have had a few odd issues where for 5 mins the alarm will arm and disarm but then it is fine.
Today the add on has stopped and will one start for a short period.
I have rebooted and powered down the system but it will still only stay alive for maybe a minute.
I have also rebooted the network ( UniFi )
I am on ha 2024.5.4 and have not done any updates to the system at all for weeks.
The logs are below
Any ideas ?
Thank you
Jeremy
Error: connect EHOSTUNREACH 192.168.20.8: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: -113,
code: ‘EHOSTUNREACH’,
syscall: ‘connect’,
address: ‘192.168.20.8’,
port: 10001
}
2024-06-06 06:45:40 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
node:events:368
throw er; // Unhandled ‘error’ event
^
Anyone come across this error before?
2024-06-19 20:30:43 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
node:events:368
throw er; // Unhandled 'error' event
^
Error: connect ECONNREFUSED 192.168.1.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: '192.168.1.126',
port: 10001
}
Had this working for ages and just seem to stop working out the blue, no idea why. Now I just get this error every time I retart the addon and I don’t see anything in the moquitto logs at all.
Been searching for a solution for a few weeks, but I’m completely out of ideas!
Thanks in advance!
I have two Texecom alarm systems, using one isn’t an option. Anyone linked HA to two alarm systems using the integration?
My alarm state isn’t moving from arming to armed. all other states seem to work. Any suggestions?
Hi. I acknowledge that I haven’t read all 900+ replies so apologies if this has been all answered already.
Is this project still live and working?
I’ve just started my first HA journey 2 days ago and have just managed to get my first device (switchbot) connected.
I have a number of sensors in my house already with a premier elite + Connect smartcon.
I tried to follow all the steps with mosquito etc but when I launched Texecom2mqtt - it immediately stopped. My guess is that I completed a part of the configuration incorrectly. I was unclear where I’d gone wrong so deleted everything.
More Concerning, the panel reported UDL lockout and required a number of hours of panic (taking out power and being deafened with numerous tampering alarms).
I’m now nervous about trying things again - particularly if this doesn’t work anymore.
Are there any idiot proof tutorials out there IF I was feeling bold in the future? I’ve watched some YouTube vids around mqtt but nothing specific about Texecon.
Im also willing to send some money to your favourite charity if there is anyone that could talk me through things.
Sincere thanks
Hi Matt,
Couple of questions first: have you got engineer access to your own alarm system, or is it a professionally installed one where they are reticent to give the owner engineer access? Do you know your UDL password? This is a key starting point as the UDL password (which is not the same as the alarm code) is needed for texecom2mqtt to talk to the alarm panel. Wintex is also a very useful thing to have working with these alarm panels!
Next, what interfaces do you have on your alarm? Are you planning to connect to it using the SmartCom? Do you also plan to use the Texecom Connect service as well? The reason I ask is that if you do wade through this thread you’ll see that the Texecom panel is a simple creature and it does not like more than one service using a single network interface, which means that HA and Texecom Connect will not cohabit well on a single interface (e.g. SmartCom). Many of us have installed a second interface to the panel (e.g. ComIP) dedicated to HA to avoid this.
In terms of whether the project is alive, the answer is “mostly” - it works pretty well and there’s lots of us using it. There’s a couple of long-standing bugs, related entirely to long-standing bugs on the panel firmware itself, which means that the add-on can crash occasionally, but most of us live with this and it’s still a very useful add-on in HA. Speaking personally, I have very few issues with it, other than the odd checksum-related crash (again, more further back in the thread).
Thanks so much for taking the time to reply.
Professionally installed one where they are reticent to give the owner engineer access?: I spoke to the installer yesterday and they weren’t prepared to give me the engineer code
Do you know your UDL password?: Yes, it is 1234 - checked and working with Wintex
Next, what interfaces do you have on your alarm?: Just the SmartCom
Do you also plan to use the Texecom Connect service as well?: I could do without if required
Texecom Connect will not cohabit well on a single interface: I read this and would be prepared to buy a ComIP or use an additional pi if in theory, things were working
This is my log from today:
2024-08-07 18:47:12 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2024-08-07 18:47:12 - INFO: Connected to alarm, sleeping for 2 seconds…
2024-08-07 18:47:14 - DEBUG: Executing serial number command
2024-08-07 18:47:14 - INFO: Connection ready
2024-08-07 18:47:14 - INFO: Logging in to panel
2024-08-07 18:47:14 - ERROR: Could not log in to panel
2024-08-07 18:47:14 - DEBUG: Closing connection to panel
2024-08-07 18:47:14 - DEBUG: Closed connection to panel
and the config file:
texecom:
host: 192.168.1.184
udl_password: “1234”
port: 10001
mqtt:
host: mqtt://core-mosquitto
port: 1883
prefix: texecom2mqtt
username: mqttusername
password: mqttpassword
client_id: texecom2mqtt
keepalive: 60
clean: true
retain: true
retain_log: false
qos: 0
ca: none
cert: none
key: none
reject_unauthorized: true
homeassistant:
discovery: true
prefix: homeassistant
areas:
- id: house
name: House Alarm
full_arm: armed_away
part_arm_1: armed_night
part_arm_2: armed_home
part_arm_3: armed_custom_bypass
code_arm_required: false
code_disarm_required: false
code: “123456” - id: …
name: …
zones: - id: front_door
name: Front Door Sensor
device_class: motion - id: …
name: …
cache: true
log: debug
I have moments that I think I’ve cracked in but then it doesn’t connect. I’ve learnt not to keep watchdog on as x3 failed attempts leave to a UDL lockout + COM1 error + ATS Fault which clears after 4 hours.
Any idea where I’m going wrong? I figured that at least it would log in given that the texecom host/udl password and port is definitely right…
If I can get a connection - happy to consider buying other hardware
Yeah, unfortunately this will be key. e.g. I am pretty sure that you’ll need engineer access to shut off Texecom Connect or to add a new ComIP and even to disable the UDL lockout option while you are testing it! This properly winds me up as presumably you paid for the alarm and their time to install it, so what gives them the right to withhold something that limits your ability to use what you paid for. Grrr! Perhaps you could go back and explain what you are doing, but I suspect they’ll probably just want to charge you by the hour to do it for you.
Have you followed the various troubleshooting tips here, especially the encrypted ports option? GitHub - dchesterton/texecom2mqtt-hassio: Home Assistant add-on. Connect to Texecom Premier Elite alarm panels and publish updates to MQTT. Supports arming/disarming as well as zone updates and alarm events.
Have you double-checked the IP address is correct? (I assume it is or you wouldn’t be able to trigger the UDL lockout!)
The UDL lockout is disabled by cycling the power at the panel or leaving it alone for 4 hours so currently its back to usual. The installers stance is that it impacts on insurance - not something im prepared to fight over. IP is definitely correct as you stated - it led to a lockout! It aligns with what i put in Wintex and connects fine so this isn’t the issue.
Can others confirm that adding a COMIP requires an engineer code?
Let me check out the troubleshooting…
Has anyone got any flows or examples they are willing to share. I’m switching to using this now as my smartcom has stopped sending me any alerts recently. Its been working great but I am nervous about missing any important alerts so would be great if someone could share any flows they have. I’m mainly after push notifications to mobile devices - I can then expand out and do other things with it. I am on the market to try and find a cheap comip and use that then try and fix the smart com alerts but in the meantime - this is all i have!
Hi All,
Question about the Arm Types and if they can be renamed here.
What’s the difference between Arm Away, Arm Home and Arm Night? For me, I’ve always just assumed there is a Full Arm (ie the house is empty) and Night Arm (you’re asleep upstairs and you protect the downstairs). What would Arm Home before used for, is it something to do with Entry zones triggering immediately?
Lastly, is it possible for the alarm mode buttons to be renamed in the UI? We have the Custom Bypass setup for a particular zone configuration when the dogs are left indoors to prevent them triggering the alarm. The button name “Custom Bypass” isn’t very intuitive, can it be changed?
Thanks
Barry
Hi all, new to HA but have been running node red/mqtt for a long time.
Few questions as I am having trouble connecting to the panel via texecom2mqtt: using this UART>Ethernet module 2-CH UART To Ethernet Converter, Serial Port Transparent Transmission Module | 2-CH UART TO ETH
My setup:
UART>Ethernet module IP 192.168.1.214
Port 1 on panel - Nothing Fitted / port 2000 on the UART>Ethernet
Port 2 on panel - Crestron System / port 3000 on the UART>Ethernet
I fitted the system and know the UDL and engineer codes.
I can connect using Wintex on 192.168.1.214 @ port 2000.
Questions:
Port 3000 / Crestron protocol correct?
Does my config look ok? I have mqtt broker on a separate Pi4.
Is the UDL password needed? I can telnet into panel on port 3000 without it via putty…
Any other advice appreciated!
More info from above post…
I have it working now, ask if you need help as it does rather seem this post is dead…
As I’m new to HA I am now trying to figure out how to arm/disarm etc from HA.
I have a separate MQTT broker running on another Pi4, so not sure if that’s an issue. I do have discovery turned on, and can see everything in MQTTExplorer.
resurrecting an old thread. Good news - I managed to get the engineer password.
Bad news - still doesn’t work!
2024-09-27 20:27:10 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2024-09-27 20:27:10 - INFO: Connected to alarm, sleeping for 2 seconds…
2024-09-27 20:27:12 - INFO: Connection ready
2024-09-27 20:27:12 - INFO: Logging in to panel
2024-09-27 20:27:12 - ERROR: Could not log in to panel
It’s now a case of annoyance WHY it doesn’t work rather than getting it to work.
IP is definitely right I think as it connects to the panel (any way i can check?)
Only thing I can think is left is resetting the UDL.
i recognise i am now talking to myself but following a UDL reset - it still doesn’t connect! Now giving up