Seems to stop alerts going to the Texecom app?
Closed this issue · 10 comments
The integration works great and its so useful to have access to all the alarm sensors within HA, but I've noticed that I no longer receive state change alerts from the Texecom app on my phone. Is this normal?
I run the Texecom2mqtt app within docker and when I stop the container, all the messages will then flood through to the Texecom app.
I'm less concerned about the alarm state changes since HA deals/alerts those, but would like the reassurance that when the alarm is triggered the Texecom app still receives the alert since it can generate a sound overriding the silent setting of the phone which the app is installed.
Application version
Latest image
Texecom alarm type
Premier Elite 88
Debug log
No errors generated. Its working fine
Hey, This is alas by design :-( , see the readme.md at the bottom.
Because each com port can only be associated with one concurrent app, its either texecom cloud+app or Home Assistant.
Workarounds
- Install a 3rd Com unit, like a comIP or a com wifi? , bind two connections to texecom cloud and the 3rd one to this integration
- Use a different approach
Ive decided to use a different approach and am reusing something i built for my old guardsec. I built a pcb which uses esp8266 to monitor the two programable ports, so I can detect if the alarm is set, or part set. You can also use the digital ports (need esp32) and get more info. Alas this approach is MUCH more limited, all i get is the basic alarm set/no set etc, but that works for me. My system is a 64w, all wireless devices, so most of the PIRs are sleeping so I dont get motion information etc, so the value prop for me is limited.
I might add a com port to get the full monty in the future tho
Thanks. Clearly I should have read the readme fully :)
I think I'll go for an additional com unit
I was wondering if someone could explain how to add a third com port? All the units I've seen seem to only have 2.
Hi.
I added a 3rd ComIP unit to the panel and now have Texecom app and Texecom2mqtt working together successfully for many months.
To help, my configuration is as such;
Com Port 1 - SmartCom Module
Com Port 2 - ComIP Module (Used for TexecomApp)
Com Port 3 - ComIP Module (Used for MQTT)
Against Com Port 2 & 3 I assigned static IP addresses and used the same port number on both. I then pointed Texecom2mqtt at the ComPort 3 IP address and left the other one alone for the TexecomApp
Hope this helps.
What panel are you using? The ones I looked at only have 2 com ports.
I have an Elite 88 panel and added a 3rd port which is part number CEJ-0001 "Texecom Premier Elite ComIP IP Communicator"
Where do you connect the 3rd com port? The instruction manual only mentions 2 for the 88:
CEJ-0001 should come with an expansion adapter which plugs into port 13. This gives you the additional Comport.
The integration works great and its so useful to have access to all the alarm sensors within HA, but I've noticed that I no longer receive state change alerts from the Texecom app on my phone. Is this normal?
I run the Texecom2mqtt app within docker and when I stop the container, all the messages will then flood through to the Texecom app.
Hi. I also experienced this some time ago, and have been thinking about it on and off since. The COMIP solution seems very expensive for the pleasure of getting "state change alerts" to the texecom app on the phone. By the way we have the app installed on two phones, and both phone apps still seem to get state updates of all sensors fine in near realtime when the HA Texecom2MQTT is running, and it is just the State change alerts that are missing as you wrote.
As you also mentioned, when you stop Texecom2MQTT the state change alerts thus far not received on the texecom apps come flooding in. If this happens after many weeks it can be quite annoying having so many old alerts beeping away!
My Texecom is under the control of an alarm company and so I have a bit less flexibility and possibly rather more cost associated with any modifcations.
Anyway, I was wondering if it was possible to have a work around whereby a change the Texecom2MQTT code would perform a temporary disconnect from the ELITE panel after a final state alert arrives at TEXECOM2MQTT (an example of a final state alert being "set" rather than "setting" so that the alert(s) also travels to the texecom app during the break? Perhaps the length of the disconnect could be configurable for a specified number of seconds to cater for variations with different user set up. What do you think?
I expect we'll need Daniel Chesterton (@dchesterton) to review this as a viable option and provide expertise in implementing it if it is viable. Unfortunately I can't see any evidence that Daniel has had any spare time to concentrate on his much appreciated HA endeavours recently though(?)