You are correct, well spotted however the editor is very finicky, there was an error with the code, should of been code: ‘xxxx’ between backticks. i found if it was not then the config kept changing form areas to zones and vice versa.
Fixed now and it has saved so will keep my eye on it.
Regards,
How do you get the logs? I’m getting multiple crashes a day but watchdog restarts it, I just noticed the warnings in the supervisor log. Don’t the logs get lost on container restart?
Disable the watchdog
I seem to have two instances when I open MQTT Explorer
texecom2mqtt/1184708
texecom2mqtt/21131255233315
texecom2mqtt log only shows one
2021-03-04 13:37:53 - DEBUG: Publishing to texecom2mqtt/1184708/power: {"battery_charging_current":27,"battery_voltage":13.56,"panel_current":567,"panel_voltage":13.63}
?
Private messaged you.
If it helps anyone, this is what I get when it crashes. I guess it is not tolerating a short break in communication. Mines connected via wifi, so I assume it is a wifi issue.
2021-03-05 03:48:09 - DEBUG: Updating system power...
2021-03-05 03:48:12 - DEBUG: Command 25 timed out (attempt 1, id: 246).
2021-03-05 03:48:16 - DEBUG: Command 25 timed out (attempt 2, id: 246).
2021-03-05 03:48:19 - DEBUG: Command 25 timed out (attempt 3, id: 246).
2021-03-05 03:48:23 - DEBUG: Command 25 timed out (attempt 4, id: 246).
2021-03-05 03:48:26 - DEBUG: Command 25 timed out (attempt 5, id: 246).
2021-03-05 03:48:26 - ERROR: Unhandled rejection - Command 25 timed out 5 times and could not be completed
2021-03-05 03:48:26 - DEBUG: Ending socket connection to panel
2021-03-05 03:48:26 - DEBUG: Socket connection to panel ended
2021-03-05 03:48:26 - DEBUG: Publishing to texecom2mqtt/1003728/status: offline
Hello
I am finally at the point I want with my setup and texecom and this amazing integration… however I am having 1 issue. I have 2 areas setup, home and garage. and 2 keypads, 1 in the home and 1 in the garage. and stuff set to A in house and B in garage. When I arm it via the keypad in the garage it works perfect and arms just the garage and the keypad shows part armed, area B fully armed (and HA shows armed away - perfect). However, if I arm it via HA it part arms it and on my dashboard, says pending constantly. On the key pad, it show part armed “bedtime”, bedtime is my house bedtime with 1 zone omitted. Any ideas please?? config below
texecom:
# Required: the panel IP address
host: 192.168.0.103
# 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: "xxxx"
# Optional: the port used to connect to the panel (default: 10001)
port: 10001
mqtt:
host: "mqtt://192.168.0.102:1883"
# Optional: MQTT server authentication user (default: nothing)
# username:
# Optional: MQTT server authentication password (default: nothing)
# password:
# Optional: MQTT client ID (default: random)
client_id: texecom2mqtt
# Optional: MQTT keepalive in seconds (default: 10)
keepalive: 30
# Optional: MQTT retain (default: true)
retain: true
# Optional: MQTT retain on log messages (default: false)
retain_log: true
qos: 2
homeassistant:
# Optional: enable auto discovery (default: false)
discovery: true
# Optional: MQTT topic prefix (default: homeassistant)
prefix: "homeassistant"
areas:
- id: 1
name: House
full_arm: armed_away
part_arm_1: armed_night
code_arm_required: false
- id: 2
name: Garage
full_arm: armed_away
# part_arm_1: armed_night
code_arm_required: false
log: debug
I’m now getting more worrying issues with the add-on. I had some sort of ATS fault this afternoon, so I reset my Digi on the board, but didn’t change any config. This allowed the add-on to re-connect, but after a few minutes I get this error.
2021-03-07 18:57:47 - DEBUG: Updating system power...
2021-03-07 18:57:47 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":297,"panel_voltage":13.7}
2021-03-07 18:58:17 - DEBUG: Updating system power...
2021-03-07 18:58:17 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":306,"panel_voltage":13.7}
2021-03-07 18:58:47 - DEBUG: Updating system power...
2021-03-07 18:58:48 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":315,"panel_voltage":13.7}
2021-03-07 18:59:18 - DEBUG: Updating system power...
2021-03-07 18:59:18 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":333,"panel_voltage":13.7}
2021-03-07 18:59:48 - DEBUG: Updating system power...
2021-03-07 18:59:49 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":324,"panel_voltage":13.7}
2021-03-07 19:00:19 - DEBUG: Updating system power...
2021-03-07 19:00:19 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":297,"panel_voltage":13.7}
2021-03-07 19:00:49 - DEBUG: Updating system power...
2021-03-07 19:00:49 - ERROR: Unhandled rejection - RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 1
2021-03-07 19:00:49 - DEBUG: Ending socket connection to panel
2021-03-07 19:00:49 - DEBUG: Socket connection to panel ended
2021-03-07 19:00:49 - DEBUG: Publishing to texecom2mqtt/1003728/status: offline
2021-03-07 19:00:49 - DEBUG: Panel socket closed
Then when I try to restart the add-on I get this:
2021-03-07 18:57:47 - DEBUG: Updating system power...
2021-03-07 18:57:47 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":297,"panel_voltage":13.7}
2021-03-07 18:58:17 - DEBUG: Updating system power...
2021-03-07 18:58:17 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":306,"panel_voltage":13.7}
2021-03-07 18:58:47 - DEBUG: Updating system power...
2021-03-07 18:58:48 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":315,"panel_voltage":13.7}
2021-03-07 18:59:18 - DEBUG: Updating system power...
2021-03-07 18:59:18 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":333,"panel_voltage":13.7}
2021-03-07 18:59:48 - DEBUG: Updating system power...
2021-03-07 18:59:49 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":324,"panel_voltage":13.7}
2021-03-07 19:00:19 - DEBUG: Updating system power...
2021-03-07 19:00:19 - DEBUG: Publishing to texecom2mqtt/1003728/power: {"battery_charging_current":9,"battery_voltage":13.49,"panel_current":297,"panel_voltage":13.7}
2021-03-07 19:00:49 - DEBUG: Updating system power...
2021-03-07 19:00:49 - ERROR: Unhandled rejection - RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 1
2021-03-07 19:00:49 - DEBUG: Ending socket connection to panel
2021-03-07 19:00:49 - DEBUG: Socket connection to panel ended
2021-03-07 19:00:49 - DEBUG: Publishing to texecom2mqtt/1003728/status: offline
2021-03-07 19:00:49 - DEBUG: Panel socket closed
The only way I can get it to re-connect is to reset the Digi again. Not ideal.
Any ideas anyone? It has been working mostly fine up to today.
I’m suspicious there is a problem with the Smartcom api today. I can connect to my panel via the V1 Texecom Connect app, but not via V2. Since both go via the Smartcom, it seems a bit odd.
Hi all,
First of all, thanks for this great integration. I was able to set it up against my newly installed Premier Elite 48 and was up and running in 30 minutes which is superb. I do, however, have a couple of questions:
And one more (sort of) unrelated question: does anyone know how to temporarily disable the bell output on the texecom so I can do some silent alarm testing without messing about with wires and bell holdoffs? I’ve waded through the docs, but not had so much luck so far.
Many thanks to the developer for this excellent, high-quality interface.
hi @daern,
Regarding your item (1.) this is what i have experienced too. if you are sharing an IP connection between Wintex and texecom2MQTT, you can only have one of them up and running at a time. I think the answer is to install a ComIP in addition to the SmartCom. You sort of get a similar “one thing at a time” behaviour with the Texecom Connect phone app. If you have the phone app running, and connect with Wintex (and i’m sure it’ll be the same while T2MQTT is connected), the phone app mostly works, but the push notifications appear to be delayed until you disconnect Wintex (and then you get all the push notifications all at once!!)
Not sure about the other queries, sorry!
Mathew
Thanks Mathew. I guessed that would be the case from the behaviour I’ve observed. Will see how I get on before I rush out and buy another ComIP interface!
Indeed! i did the opposite, and picked up a ComIP on eBay yesterday! i’ll report back on how i get on when it arrives…
Ah, cool! Do you have a SmartCom already? What’s your plan - to have one for Texecom Connect and one for T2MQTT?
I see the same as well however, I can connect via SmartCom in Wintex with the integration running and the experience isn’t actually too bad
If it’s an Odyssey X bell:
This puts the bell in hold off mode for either 17 minutes or until the tamper has been opened and closed. See page 12 here. This is of course the holdoff mode but I think it works for what you need?
Yeah, i have a SmartCom set up and working, i plan to continue to use this for Texecom Connect (and Wintex when required), and the ComIP for T2MQTT
Thanks. Interestingly, my Wintex won’t connect at all if the integration is running and I have to stop it first. I’m connecting direct to the SmartCom IP address, rather than via the Texecom cloud service (as I found that the Texecom Connect ARC interfered when the alarm went off!)
Ta. This doesn’t apply to my bell, but I found a setting (“Area Programming → Area Options → Bell & Strobe OP”) that disables the bell in an alarm condition, which makes testing of this stuff much more sociable! 
I only have a SmartCom installed, (well the ComIP is still in there but not connected because I only have an Elite 12). This can provide (as far as I can tell), a single IP connection which I use for T2MQTT, and then the Connect App and Wintex all use Smartcom. This can all run at the same time.
Could it be that you set up separate UDL codes (or do i mean different app codes) for each device/application/protocol ?? (i have not tried that)
You have to register the apps (and I think Wintex) using a code generated from the panel or app, but I’ve only set one UDL code.