If you go to configure the mqtt integration, you can listen to mqtt messages. I just put in texecom2mqtt/# and started listening. It showed me the messages and their keys coming in.
1 Like
ahhhh /# is the wildcard. Thanks 
Hi, The App is stalling and not triggering the watchdog, same as 1.039
texecom2mqtt
Current version: 1.0.40
|Installation Type|
Home Assistant OS|
|Development|false|
|Supervisor|true|
|Docker|true|
|Virtual Environment|false|
|Python Version|3.8.7|
|Operating System Family|Linux|
|Operating System Version|5.4.109|
|CPU Architecture|x86_64|
|Timezone|Europe/London|
Home Assistant Supervisor
|Host Operating System|Home Assistant OS 5.13|
|Update Channel|stable|
|Supervisor Version|supervisor-2021.04.0|
|Docker Version|19.03.15|
|Disk Total|228.5 GB|
|Disk Used|46.6 GB|
|Healthy|true|
|Supported|true|
|Board|intel-nuc|
Logs
2021-04-16 12:13:23 - DEBUG: Publishing to texecom2mqtt/1184708/zone/utility_room_motion_sensor: {"name":"UTILITY ROOM Motion Sensor","number":6,"areas":["A"],"status":1,"type":"Guard"}
2021-04-16 12:13:24 - PANEL: Output state changed digi: 207
2021-04-16 12:13:25 - INFO: KITCHEN Motion Sensor status changed to Secure
2021-04-16 12:13:25 - DEBUG: Publishing to texecom2mqtt/1184708/zone/kitchen_motion_sensor: {"name":"KITCHEN Motion Sensor","number":5,"areas":["A"],"status":0,"type":"Guard"}
2021-04-16 12:13:26 - DEBUG: Command 25 timed out (attempt 3, id: 202).
2021-04-16 12:13:26 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:14:05 - DEBUG: Updating system power...
2021-04-16 12:14:06 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:14:55 - DEBUG: Updating system power...
2021-04-16 12:14:56 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:15:45 - DEBUG: Updating system power...
2021-04-16 12:15:46 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:16:35 - DEBUG: Updating system power...
2021-04-16 12:16:36 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:17:25 - DEBUG: Updating system power...
2021-04-16 12:17:26 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:18:15 - DEBUG: Updating system power...
2021-04-16 12:18:16 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:19:05 - DEBUG: Updating system power...
2021-04-16 12:19:06 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:19:55 - DEBUG: Updating system power...
2021-04-16 12:19:56 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:20:45 - DEBUG: Updating system power...
2021-04-16 12:20:46 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:21:35 - DEBUG: Updating system power...
2021-04-16 12:21:36 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:22:25 - DEBUG: Updating system power...
2021-04-16 12:22:26 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:23:15 - DEBUG: Updating system power...
2021-04-16 12:23:16 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:24:05 - DEBUG: Updating system power...
2021-04-16 12:24:06 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:24:56 - DEBUG: Updating system power...
2021-04-16 12:24:56 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:25:46 - DEBUG: Updating system power...
2021-04-16 12:25:46 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:26:36 - DEBUG: Updating system power...
2021-04-16 12:26:36 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:27:26 - DEBUG: Updating system power...
2021-04-16 12:27:26 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:28:16 - DEBUG: Updating system power...
2021-04-16 12:28:16 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:29:06 - DEBUG: Updating system power...
2021-04-16 12:29:06 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:29:56 - DEBUG: Updating system power...
2021-04-16 12:29:56 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:30:46 - DEBUG: Updating system power...
2021-04-16 12:30:46 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:31:36 - DEBUG: Updating system power...
2021-04-16 12:31:36 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:32:26 - DEBUG: Updating system power...
2021-04-16 12:32:26 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-16 12:33:16 - DEBUG: Updating system power...
2021-04-16 12:33:16 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:19:01 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:19:50 - DEBUG: Updating system power...
2021-04-17 10:19:51 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:20:40 - DEBUG: Updating system power...
2021-04-17 10:20:41 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:21:30 - DEBUG: Updating system power...
2021-04-17 10:21:31 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:22:20 - DEBUG: Updating system power...
2021-04-17 10:22:21 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:23:10 - DEBUG: Updating system power...
2021-04-17 10:23:11 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:24:00 - DEBUG: Updating system power...
2021-04-17 10:24:01 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:24:50 - DEBUG: Updating system power...
2021-04-17 10:24:51 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:25:40 - DEBUG: Updating system power...
2021-04-17 10:25:41 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:26:30 - DEBUG: Updating system power...
2021-04-17 10:26:31 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:27:21 - DEBUG: Updating system power...
2021-04-17 10:27:21 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:28:11 - DEBUG: Updating system power...
2021-04-17 10:28:11 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
2021-04-17 10:29:01 - DEBUG: Updating system power...
2021-04-17 10:29:01 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":9,"battery_voltage":null,"panel_current":909,"panel_voltage":null}
Will revert back a couple of releases for now.
Regards,
I avoided the update to 1.0.39, but did update to 1.0.40 and have myself noticed some erratic behaviour.
Need to continue testing in order to come to any conclusions, however.
Just ran into erratic behaviour. I triggered an entry countdown with the alarm, but the addon was unresponsive. The same zone that triggered the entry normally switches on the lights in that room.
Tried to disarm the alarm using a tablet keypad without luck, and eventually the alarm triggered 
In the logs I can see:
{“battery_charging_current”:0,“battery_voltage”:null,“panel_current”:0,“panel_voltage”:null}
2021-04-19 21:52:14 - INFO: Remotely disarming House Alarm
2021-04-19 21:52:14 - WARNING: Could not disarm House Alarm
Rolling back for now as it caused a nuisance alarm, but perfectly happy to test it again if there’s any useful data I can obtain to post here.
I have been getting some weird stuff recently, it all started after a random UDL Lockout which occurred overnight, i had not changed anything on myside for weeks so assumed this addon had updated itself. i rolled back, with no success, i tried to update alarm firmware, no joy…i also re-setup texecom smartcom (i have an additional com-ip used for this addon), no change. The only bizarre workaround i’ve found is if i leave Wintex connected to my alarm via the smartcom option, then connect to the alarm from this addon via the additional comip. it works fine (well, its done about 24 hours so far). prior to this it would crash out within a few mins of loading (and then cause a UDL Lockout, which i would have to reset before i attempt to reconnect). ive done so many things along the way that could have changed the actual cause of the fault, ive tried several revisions from 1.30 to current rev with the same issue, perhaps its something in HA that has caused this issue, however for now, ill just leave WinTex connected to my alarm!
Hello everyone.
Some help needed for quite some time now I’ve been having an issue with the integration.
When I try to part arm the panel in the evenings using this app I get a message in the logs saying ‘unable to arm’. If I restart the the app, I’m able to arm.
Can anyone help me to debug the issue?
Thanks
Sups
I saw this a few times and have rolled back to 1.0.36 which, providing the watchdog is running, is very reliable and I’ve not had any issues setting/unsetting with this version
Is there a way to find out why this happens? I’m not getting much from app logs.
Did you try turning on debug logging to see if anything shows up?
yes I have debug enabled and no errors showing up on the supervisor logs… just this in the app log:
2021-04-23 10:03:53 - INFO: Remotely arming Area A to Part Arm 1
2021-04-23 10:03:53 - WARNING: Could not arm Area A
Yeah, not very helpful for fixing your problem, but if you scroll back you’ll see I had exactly the same problem as well. I’m now running 1.0.36 which seems absolutely fine and hasn’t done this on me yet.
I had something similar occur the other night when I went to set the alarm, I’d upgraded to 1.0.40 earlier that day I think.
Previously I’d just rolled back using an HA snapshot and doing a partial restore, however is there another way to install based on the docker tag? Looks like it might be possible with ‘ha addons install’ if a version can be specified?
I see 1.0.36 is still listed, but don’t immediately see a way to specify the tag/version in HA i.e which one it should fetch.
https://hub.docker.com/r/dchesterton/texecom2mqtt/tags?page=1&ordering=last_updated
EDIT: Doesn’t look like it’s possible to specify a version with ‘ha addons install/update’:
Flags:
-h, --help help for update
Global Flags:
--api-token string Home Assistant Supervisor API token
--config string Optional config file (default is $HOME/.homeassistant.yaml)
--endpoint string Endpoint for Home Assistant Supervisor (default is 'supervisor')
--log-level string Log level (defaults to Warn)
--no-progress Disable the progress spinner
--raw-json Output raw JSON from the API
It doesn’t appear to accept ‘-o version=x.x.x’ as you can for HA itself.
EDIT2: Seems not:
Does anyone have a way to manage failed sets with their alarm? I don’t have a physical keypad for my Elite, just Texecom2MQTT and Wintex - so at present, when there is a failed set, I have to go and reset the alarm via Wintex.
Just to add to this, I was slightly incorrect. With just the Smartcom installed I could connect T2MQTT via IP, and Wintex via Smartcom, and use the App. However, the panel wasn’t then sending notifications for logins/etc.
Today I’ve installed a Comport+ which adds Com Port 3 to the panel, set it to ComIP module and connected my old Com Wifi to the Comport+. This now allows me to point T2MQTT at the Com Wifi IP and allow the Smartcom to do everything else. Notifications are now sent out correctly.
Comport+ are about £10 for 5, I now have some spares…
I’ve released a new version 1.0.41 which should fix the recurring issue where the app crashes but doesn’t restart properly.
I’ve also changed the MQTT topic structure to remove the serial number, so where the topic would have been texecom2mqtt/[serial]/zone/... it will now be texecom2mqtt/zone/... This should fix issues some people are having where the app doesn’t find the correct serial number meaning you end up with multiple alarms in Home Assistant.
Unfortunately you will have to manually delete these topics (where ‘12345’ is your serial number):
texecom2mqtt/12345/*homeassistant/binary_sensor/texecom2mqtt-12345/*homeassistant/alarm_control_panel/texecom2mqtt-12345/*
The easiest way is to use an app like MQTT Explorer.
Doesn’t that mean with multiple alarms they’ll get merged ?
Saw a bunch of the below, after upgrading to 1.0.41:
2021-05-16 08:36:12 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID 1013672.zone.living_room already exists - ignoring binary_sensor.living_room
2021-05-16 08:36:12 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID 1013672.zone.landing already exists - ignoring binary_sensor.landing
2021-05-16 08:36:12 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID 1013672.zone.entry_door already exists - ignoring binary_sensor.entry_door
2021-05-16 08:36:12 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID 1013672.zone.garage already exists - ignoring binary_sensor.garage
2021-05-16 08:36:12 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID 1013672.zone.garage_door already exists - ignoring binary_sensor.garage_door
Tried trashing the entire MQTT topic, but still they seem to remain - texecom2mqtt log shows it talking to the alarm, just HA not happy with the entities.
UPDATE: Ah, probably need to trash the homeassistant/ MQTT topics, noted above. Although I seem to have caused myself a few other issues, arse. Rolling back for now.
UPDATE 2: Ok, fixed the above, deleted the right MQTT entries, but my ‘alarm_control_panel.area_a’ shows as an ‘Unknown’ state and the only option is ‘Disarm’ in the UI - which shows ‘Remotely disarming Area A’ but the state does not update/correct.
With the latest changes all my entities became unavailable. It appears that the MQTT discovery isn’t working at the moment for the new entities.
Also, rolling back to the previous release did not seem to restore the entities
My bad, didn’t notice the note about delete all the old topics. Would it be possible to add the release notes to wherever Supervisor looks for the changelog?
Thanks again for a great add-on/integration