Comfort Automation/ Security System Forums
Ethernet and Slave Comms issues after thunderstorm - Printable Version

+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Support (https://www.comfortforums.com/forum-2.html)
+--- Forum: Problems & Troubleshooting (https://www.comfortforums.com/forum-36.html)
+--- Thread: Ethernet and Slave Comms issues after thunderstorm (/thread-5867.html)

Pages: 1 2


RE: Ethernet and Slave Comms issues after thunderstorm - slychiu - 06-04-2026

The slave will only send zone changes when they occur, it does not automatically end a message when it i not doing anyting. It is best to check the event log to see if there is any slave zone troubke


RE: Ethernet and Slave Comms issues after thunderstorm - caravanboy - 06-04-2026

Ok, I'll monitor it for a few days and see if any other failures show up.

As I said, the zone messages from the Slave all seem to be fine.


RE: Ethernet and Slave Comms issues after thunderstorm - cc_uk - 06-04-2026

I too used to get a Comms failure on a CM9000 with a SEM01   Wasn't there an issue with the latest SEM01 firmware that caused a timeout while it searched for an EEPROM?

I fixed this by downgrading my SEM01 firmware.  I believe there was due to be a newer update that would avoid this issue for the SEM.  However wondering if caravanboy has this issue and why he gets the comms failure for a while.


RE: Ethernet and Slave Comms issues after thunderstorm - caravanboy - 06-05-2026

Interesting. 

Just checked and my last batch of firmware updates (including SEM01) was Jan 2025. Apparently I had issues with getting the correct firmware at the time and Cytech had to point me at a different one. (from 7.141 to 7.207).

Guess what I also found from Dec 2025!!!! A note saying that after a system reset I DID have a Slave Comms failureRolleyes  I had no recollection of that!

Thanks for the info!  At least I know the slave probably was NOT damaged by the storm. 

If this is the only time it causes the problem I can live with that then. Unless Cytech can advise if there is a newer firmware that fixes this timing issue?