Hi, Removed and re added repository, same result.
20-09-10 08:34:14 ERROR (SyncWorker_6) [supervisor.docker.interface] Can't install dchesterton/texecom2mqtt:latest -> 404 Client Error: Not Found ("no such image: dchesterton/texecom2mqtt:latest: No such image: dchesterton/texecom2mqtt:latest")
https://github.com/dchesterton/texecom2mqtt-hassio
I have the app up and running on docker desktop but I am seeing the following in logs.
PS C:\Users\Mark\texecom2mqtt> docker-compose up
Creating texecom2mqtt ... done
Attaching to texecom2mqtt
texecom2mqtt | 2020-09-11 18:35:13 - INFO: Connected to alarm, sleeping for 0.5 seconds...
texecom2mqtt | 2020-09-11 18:35:14 - INFO: Connection ready
texecom2mqtt | 2020-09-11 18:35:14 - INFO: Fetched serial number: xxxxxxx
texecom2mqtt | 2020-09-11 18:35:14 - INFO: Logging in
texecom2mqtt | 2020-09-11 18:35:14 - DEBUG: Executing command 1
texecom2mqtt | 2020-09-11 18:35:14 - ERROR: Unhandled rejection - RangeError [ERR_INVALID_OPT_VALUE]: The value "NaN" is invalid for option "size"
my config.yml
texecom:
# Required: the panel IP address
host: 192.168.0.211
# Optional: the UDL password programmed in the panel (default: 1234)
# Please note: this is not the code used to arm/disarm the panel, it can be found
# in UDL/Digi Options - UDL Options - UDL Password
udl_password: 1234
# Optional: the port used to connect to the panel (default: 10001)
port: 10001
What panel do you have? That error normally appears when the app can’t work out the panel size/type.
Premier Elite 24 (Polymer) Firmware 5.02.01L51
Then it’s probably the UDL password that is wrong, you’ll need to check what it’s set to in your panel. Take a look at the ‘Troubleshooting’ section here: https://hub.docker.com/r/dchesterton/texecom2mqtt
I’ve just released an update which now gives the actual zone which triggered the alarm as well as additional information on zones such as the zone type and the areas it is in.
You can use the zone trigger information in an automation as follows:
alias: "Alarm triggered"
trigger:
platform: mqtt
topic: texecom2mqtt/12345/area/X
condition:
condition: template
value_template: "{{ trigger.payload_json['status'] == 'triggered' }}"
action:
- service: notify.phones
data_template:
title: Alarm Triggered
message: "{{ trigger.payload_json['last_active_zone']['name'] if trigger.payload_json['last_active_zone'] else 'Unknown' }}"
I’ve also changed the topic structure a little bit which may break your automations. All topics are now prefixed with texecom2mqtt/12345/# instead of texecom-12345.
I’ve made the change so that it’s easier to target texecom2mqtt topics using wildcards.
Which panels are actually supported? Some list would be lovely, because Premier Elite series is massive…
I’m thinking to buy one, but i need wireless…
Will it work with this one, for example?
https://www.alertelectrical.com/texecom-kit-0002-ricochet-premier-elite-64w-wireless-alarm-kit-smartcom-kit-0002-smartcom.html
It should work with any Premier Elite panel.
Above one is ‘ricochet premier elite’, that’s why i’m asking. They have got way too many models 
I just want to buy right one 
It’s still an Elite panel so it should work but I can’t guarantee it.
Ok thanks. I’ll try to find some other wireless elite model then, unless you have one recommended
Any non-discontinuted panel on this page should work: https://www.texe.com/uk/products/series/control-panels/premier-elite-series/
So it seems to be just Premier Elite 64-W in my case lol
Well I am pleased to say I have got the integration up and running and communicating with HA.
Not quite sure how but I did a complete reset of the panel and reconfigured with Wintex.
Maybe I wasn’t patient enough for the connection to fully close on Wintex app before starting Doccker?
HA auto discovers the 10 zones I have programmed on the Panel.
My question now, is it possible to have alarms or status outputs as binary sensors or are these just treated as events?
I have tried listening for events under Developer Tools but not receiving anything
output of log on docker desktop
texecom2mqtt | 2020-09-12 14:42:58 - DEBUG: Publishing to texecom2mqtt/1184708/power: {“battery_charging_current”:9,“battery_voltage”:13.56,“panel_current”:342,“panel_voltage”:13.63}
So the event to subscribe to is texecom2mqtt/1184708/power?
I still cannot setup from HA as per this procedure
To set the app up as a Home Assistant Add-on:
https://github.com/dchesterton/texecom2mqtt-hassio as a new repository. The add-on should now be listed on the ‘Add-on store’ page.
20-09-12 14:39:47 INFO (SyncWorker_0) [supervisor.docker.interface] Pull image dchesterton/texecom2mqtt tag latest.
20-09-12 14:39:49 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install dchesterton/texecom2mqtt:latest -> 404 Client Error: Not Found ("no such image: dchesterton/texecom2mqtt:latest: No such image: dchesterton/texecom2mqtt:latest").
20-09-12 14:39:49 INFO (SyncWorker_0) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 93.0 GiB
Regards,
All the topics are listed here: https://hub.docker.com/r/dchesterton/texecom2mqtt. The main ones you’re interested in will be texecom2mqtt/[serial]/area/[name] and texecom2mqtt/[serial]/zone/[name].
If you enable Home Assistant discovery (https://www.home-assistant.io/docs/mqtt/discovery/) it should create the relevant sensors for you.
I think the page you are looking at there is the event queue. You want to look at the MQTT queue which I thought was on the developer page somewhere, but I can’t see it on my phone.
Great work @dchesterton. I have my own serial to mqtt hardware adapter for Texecom using the Crestron and Simple protocol. What you’ve done here it brilliant! It sucks that Texecom won’t let you release the code.
Does this stop the standard Texecom app and notifications from working? In my early testing the SmartCom could only handle a single TCP connection. So if any other session was open the Texecom cloud can’t connect and the SmartCom will not send updates to it.
Thanks,
Kev
Hi @dchesterton this is a great piece of code that you have written, well done…
I had this working properly yesterday but updated it today after you said that you had done some code updates. But I have now run into a problem setting up the MQTT Alarm Panel within home assistant. I have entered all the new format for topic and command that you have suggested but it returns this error…
Any ideas…
Many thanks
Logger: homeassistant.components.mqtt.alarm_control_panel
Source: components/mqtt/alarm_control_panel.py:199
Integration: MQTT (documentation, issues)
First occurred: 4:36:41 PM (1 occurrences)
Last logged: 4:36:41 PMReceived unexpected payload: {“name”:“House Alarm”,“number”:1,“status”:“disarmed”}
Yeah I believe it does stop the app from working. I think others have it working by connecting both a SmartCom and a ComIP which should allow the 2 connections.
Can you try restarting Home Assistant? There’s a bug in HA where if the discovery code changes, HA doesn’t pick it up until it’s restarted.