I have a Texecom Premier Elite 48 alarm, which has been installed (by myself) for around 3 years now and worked flawlessly in that time. Last week, it started reporting "ATS Path Fault Alarm from Panel Input", and has a latched "ATS Path Fault" alarm in System Status in Wintex. The panel reports "ATS Path fault - COM1 fault". There have been no changes made to the alarm configuration recently, either in hardware or configuration.
The system has a SmartCom device (used for Wintex only) on COM1/COM2 and a separate ComIP on COM3, dedicated to Home Assistant.
My guess is that it's trying to talk to Texecom Cloud via the SmartCom and this is failing (probably not permitted on my network), but I've no idea why it's only just started to report this now. As I have no need to us Texecom Cloud for this alarm, what's the best way to stop it trying to talk to it? Is it enough to just remove the "SmartCom" option from COM1 and leave the two remaining ComIP modules on COM2 and COM3? FYI, all ARCs are set to "disabled".
The system has a SmartCom device (used for Wintex only) on COM1/COM2 and a separate ComIP on COM3, dedicated to Home Assistant.
My guess is that it's trying to talk to Texecom Cloud via the SmartCom and this is failing (probably not permitted on my network), but I've no idea why it's only just started to report this now. As I have no need to us Texecom Cloud for this alarm, what's the best way to stop it trying to talk to it? Is it enough to just remove the "SmartCom" option from COM1 and leave the two remaining ComIP modules on COM2 and COM3? FYI, all ARCs are set to "disabled".