Can anyone help me with adjusting how the config.yml is mounted for docker.
I’m using a QNAP NAS which has a front end to Docker called “Container Station”. I can get the docker image started using the docker-composer.yml example along with a config.yml in the same folder.
However, I need to SSH into the QNAP to do this. Ideally I would just use the front end for Container Station, but it doesn’t allow me to mount a specific file in it’s volume mappings, only directories. All the other images I have that use a mapped volume for config files have them in a folder (eg Config). Is there a way the Texe2MQTT docker can be mounted to find it’s config.yml in a folder?
Hi, just to say, for the minute I am running this under a daemon, but need to work out getting it to run automatically when the NAS is rebooted, but I realise that my problem is probably unique to QNAP. I may look at putting Portainer on to manage my docker images rather than QNAP’s Container Station in the hope that this will help with the auto-restarts.
In the mean time, I have got the docker image running and connected to my Texecom alarm successfully. Initially the auto discovery didn’t work, and the problem lies in the same config.yml that is on the docker hub page. Under the homeassistant: section it has the prefix as home-assistant even though it clearly states in the comments that the default shouldn’t have the hyphen in it. Commenting out this line reverts to default and then HA picks up the sensors. Might be worth you updating the sample config.yml to reduce confusion though either by correcting the prefix listed or comment it out.
Thanks for the great work though. I am going to see if I can get this working in the way I hope and then I will buy you beer !
Hi all, I’m hoping someone in the community can help me with this. I had my texecom alarm nicely integrated with HA and everything was working relatively well. I then had my alarm serviced (the engineer says nothing has changed) and I also updated to the latest versions of HA / supervisor / HAOS. I’m now getting this error on start up and am not really sure how to go about debugging. Any help much appreciated.
2022-11-06 11:44:42 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2022-11-06 11:44:42 - INFO: Connected to alarm, sleeping for 2 seconds…
2022-11-06 11:44:42 - TRACE: Received data chunk of length 2
2022-11-06 11:44:44 - DEBUG: Executing serial number command
2022-11-06 11:44:44 - TRACE: Received data chunk of length 2
2022-11-06 11:44:44 - ERROR: Could not fetch serial number
Still struggling with this but after discussing with the engineer and him resetting the SmartCOM and disabling and then re-enabling the com ports I now seem to have got a little further along. He says version 6.02.02 of the software is installed on the panel after he serviced it. My log now looks like this. Anyone else having issues?
2022-11-08 21:54:32 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2022-11-08 21:54:32 - INFO: Connected to alarm, sleeping for 2 seconds…
2022-11-08 21:54:34 - DEBUG: Executing serial number command
2022-11-08 21:54:35 - INFO: Connection ready
2022-11-08 21:54:35 - INFO: Logging in to panel
2022-11-08 21:54:35 - ERROR: Corrupt response from panel: Unexpected start, expected ‘t’, got 0xe4
2022-11-08 21:54:35 - DEBUG: Closing connection to panel
2022-11-08 21:54:35 - DEBUG: Closed connection to panel
2022-11-08 21:54:35 - DEBUG: Panel socket closed
2022-11-08 21:54:35 - INFO: Panel disconnected, exiting now
Do you have anything else connecting on the same Texecom com port connection?
For example the Texecom app or some other communication device? For reliable operation only 1 can communicate on any given com port at a time. You can add multiple com ports to your alarm for this purpose.
Has anyone had a panel show CIE Reset? This is apparently a CPU crash. I’ve had this twice in the last 2 months, and one other time when I was upgrading the firmware. Both recent times the panel was disarmed during the day, and I wasn’t doing anything on HA. Been using the integration for about 1 year.
Panel is 640 zone and about 4 years old. There is nothing in the logs.
I don’t think I have anything else connected (is there any way to check and kill all connections?). The engineer also confirmed that nothing else uses the COM ports. He disabed and then re-enabled COM ports 1 and 2 to see if it helped but unfortunately it made no difference. I previously was able to use both HA and the texecom app in parallel without any problems however, I would be fine to stop using the texecom app in favour of HA if I could get it working again. I’ve logged out of the texecom app but I am not sure if that disconnects it from the COM port. I enabled trace logging in case it helps diagnosis. I get this on startup:
2022-11-11 21:25:24 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2022-11-11 21:25:24 - INFO: Connected to alarm, sleeping for 2 seconds…
2022-11-11 21:25:26 - DEBUG: Executing serial number command
2022-11-11 21:25:30 - DEBUG: Command serial timed out (attempt 1, id: serial).
2022-11-11 21:25:30 - TRACE: Received data chunk of length 80
2022-11-11 21:25:30 - INFO: Connection ready
2022-11-11 21:25:30 - INFO: Logging in to panel
2022-11-11 21:25:30 - TRACE: Executing command 1
2022-11-11 21:25:31 - TRACE: Received data chunk of length 80
2022-11-11 21:25:31 - ERROR: Corrupt response from panel: Unexpected start, expected ‘t’, got 0x2a
2022-11-11 21:25:31 - DEBUG: Closing connection to panel
2022-11-11 21:25:31 - DEBUG: Closed connection to panel
2022-11-11 21:25:31 - DEBUG: Panel socket closed
2022-11-11 21:25:31 - INFO: Panel disconnected, exiting now
I don’t know if there is a way to kill them off, but since you’ve not added anything else to the system and it was working it seems a bit odd.
I can’t remember if you said you were connecting over Wifi or Ethernet. It might be possible to move the Com port to a different IP address to ensure that whatever was talking to it doesn’t know it’s address has changed and then try and get HA to connect to that?
I had to do the above as I have a SmartCom on one Com port and Control4 attached on another. Since I can’t access Control4 to turn off the Texecom integration, I changed the IP address on the Texecom port so that Control4 can’t reach it and now my HA talks to the new IP address without issue.
I can’t remember the error I was getting, but I have a hunch it was similar to yours.
Not had time to fix for a while, but am getting the error below after 24-36hours or running. Running 1.2.3 or texe2mqtt and HA running latest updates. Panel: Premier Elite 640 (V5.00.02LS1). Its running from a dedicated COMIP.
This was running fine since initial issues at first release, now this…
2022-11-12 18:00:38 - WARNING: Received message starting with ‘+++’. Panel has forcibly dropped connection, possibly due to inactivity
2022-11-12 18:00:39 - ERROR: Unhandled rejection - Command 1 timed out 5 times and could not be completed
Hi, I’m after some help, I’m running HA on a Synology docker, and try as I might (as well as reading all 700 posts here) I’m having trouble with the texecom2mqtt docker, it starts and immediately stops, I’m a bit of a noob when it comes to this but I’ve got a wall with this. I find this error under docker logs if it helps:
Start container texecom2mqtt
failed: (“message”.“OCI runtime
create failed: container_linux.go:367:
starting container process caused:
process_linux.go:495: container init
caused: rootfs_linux.go:61: mounting
I”/volume1 /docker/Homeassistant/
config/config.ymlI" to rootfs at
I"/volume1/@docker/aufs/mnt
/fac8aa2b 1 1fa58b4d1 03f4ba74
0cd485e4755b7a3555951ec488
9af2d2daOebb/volume1/docker
/Homeassistant/configI" caused:
not a directory: unknown: Are you
trying to mount a directory onto
a file (or vice-versa)? Check if the
specified host path exists and is the
expected type").
Any help is much appreciated.
Hi @RoganDawes, I’ve been using texecom2mqtt without any problems for the last couple of years but ever since I had my alarm serviced and the engineer “upgraded” some of the software I’ve been unable to connect from HA (It seems to be timing out trying to execute the serial command). I’d be interested in trying an alternative if you still have this working and can point me in the right direction? Thanks!
Hi @samirrpatel I do have this working to some extent, although I have been fighting against my lack of C++ knowledge. I currently have the ability to read the state of various binary sensors (essentially all those exposed via the Wintex app), as well as know how the protocol works to trigger zone bypass, and a number of other actions, including activating and deactivating zones (unfortunately, this is where my C++ inexperience is biting me).
What alarm panel do you have? And do you know what software the engineer updated that has caused the problems you are now experiencing? Are you able to connect with the Wintex app?
@RoganDawes it’s a Premier Elite 64 running firmware version 6.02.02 and SmartCom version 3.03. I believe it was the firmware that he upgraded as part of a regular service. I’ve not tried the wintex app (where do I get that from, is that an app on the Google play store or a windows application?). I’m able to connect and use the alarm via the Texecom v 2.0.24 app on my phone. One thing I’m going to try is to reassign the static IP associated with the alarm to see if that changes anything but I’m a bit worried that it might stop the Texecom app from working.
I’ve been running the below for, at a guess, around 6 months without a problem - slight variation from your version:
2022-11-22 07:32:15 - INFO: Panel: Premier Elite 24 (V6.02.00LS1)
That said, I don’t have all the various ARC settings (that makes it call out to Texecom), I don’t use the mobile App and I have the SmartCOM firewalled off without any internet access - so there is minimal chance of stability issues, due to the 1 concurrent connection (HA, TexecomCloud, Mobile App, etc, etc).
EDIT: My SmartCOM seems to be running a later version:
Looks like someone else on this thread had a problem with SmartCom version 3.03 - if you search ‘this thread’ for 3.03:
“Hi Herbert, I got the original issue fixed (that we both had ‘ECONNREFUSED’) by upograding the firmware and defaulting my panel. I then had another issue where it kept saying that it could not log in to the panel. That was when I changed my UDL back to a 4 digit and it worked, I’ve no idea why that would be as I’m sure you and many others use more than 4 digits.”
… my UDL is 5 digits, just for reference, but on v4 of SmartCOm firmware.
Thanks, I assume that’s something the engineer would be able to update? I’ll give him a ring to see if he can give that a go. I assume it’s not something I can do myself?
Funnily enough ever time I’ve started the add-on it’s got a timeout running the serial command but after logging in from the Texecom app and then restarting the add-on in HA it’s somehow got a little further along and is now complaining about not being able to connect to MQTT (definitely not changed any of the MQTT settings so that’s very odd)
2022-11-22 07:43:22 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)…
2022-11-22 07:43:22 - INFO: Connected to alarm, sleeping for 2 seconds…
2022-11-22 07:43:24 - DEBUG: Executing serial number command
2022-11-22 07:43:24 - TRACE: Received data chunk of length 11
2022-11-22 07:43:24 - INFO: Connection ready
2022-11-22 07:43:24 - INFO: Logging in to panel
2022-11-22 07:43:24 - TRACE: Executing command 1
2022-11-22 07:43:24 - TRACE: Received data chunk of length 7
2022-11-22 07:43:24 - INFO: Successfully logged in to panel
2022-11-22 07:43:25 - ERROR: Could not connect to MQTT broker
2022-11-22 07:43:25 - DEBUG: Closing connection to panel
2022-11-22 07:43:25 - DEBUG: Closed connection to panel
If the engineer set this up, then he can probably do it remotely via his Texecom Cloud account - although someone would have to login to the panel with the engineer code locally, so it can be performed (I think, been a while since I did it).
… if it is configured for Texecom Cloud and the SmartCOM isn’t firewalled off, this could potentially cause contention issues. If you have the ability to nullroute/block the SmartCOM IP from all internet access, might be worthwhile giving that a go as well.
Actually, you don’t normally need to pay the few quid. I’ve got mine on my own “installer” account for nowt, although it does complain about not having payment set up! But yes, Texecom Cloud is the easiest way to do firmware updates, although I leave it switched off most of the time as I don’t use the app, and would rather not have the conflict with wintex.
FWIW, mine (which is working fine) is a Elite 48 running V5.04.01 LS1, and SmartCom V03.03.00, although it’s worth noting that I don’t use this SmartCom for HA any more - that’s done through the older ComIP installed as a second interface dedicated for the integration.
Is it worth trying a ComIP instead of a smartcom to see if this works any differently? I paid £40 for mine from eBay and it was relatively simple to fit and configure.
I’m afraid I have no experience with the Elite panels, so I probably can’t help you much.
Wintex is a Windows application that the installers use to configure the panel, or manage numbers of panels. It can connect to the panel via a COM-IP, Ser-COM, etc.
I managed to get my installer to update the SmartCom firmware to v04.02.05 but unfortunately it’s not made a difference to the HA issue. I’m going to try reassigning the static IP next and will report back if that solves it. If that still doesn’t work I can try the dedicated comIP route but given this was all working fine I’m a bit reluctant to go that route until I’ve exhausted other software/config type issues. Is there someway I can have log files persisted rather than them disappearing after each restart?
