I've searched and read a number of posts regarding SYSTEM RESET issues without resolution, so I'm perhaps just adding my own story to the fray here with tiny hopes that maybe, just maybe I can leverage this hivemind to prevent me from otherwise having to scrap the totality of my OmniPro II system which I've had running mostly trouble-free for >10 years.
In short, one day I ran a firmware update on a few of my UniFi WAPs and PoE switch and that afternoon, my OPII system went utterly crazy and died. Correlation does not equal causation and I cannot imagine how these two events would conspire, but there you have it: that was the "trigger event". Prior to this, nothing else had changed or recently been updated or modified on my system. I'm using ~1300 lines of code, and this has been my codebase effectively for years with little change (i.e., I don't suspect any sort of code loop).
The OPII will not hold an Ethernet connection long enough to stay connected and download from PCA - this has ALWAYS been largely the case, and I blame the weak Ethernet port on the OPII, and the fact that I have heavy heavy traffic on my LAN: about 200 IP devices, 25+ 4MP IP cameras, 12+ iPads used as touchscreens (via Myro:Home), multiple PoE WAPs and other devices, and a ton of general network activity via PCs, laptops, servers, Synology storage servers, etc.
Since I'm talking about the LAN: A Ubiquiti USW-Pro-48-PoE powers the PoE side (600W budget, using about 200W of it), plus a few Cisco SG-200-48 switches, running through a Peplink multi-WAN router fed off Verizon LTE as primary ISP and a CenturyLink DSL as backup (we live in the sticks). HAI gear includes the OPII and a HiFi2 (I had the e-mail notifier board but it was junk so took it out). I have tried to connect just my PC and HAI on a small switch separated from the rest of the network traffic and this enables me to get PCA to download a bit better, but did not otherwise obviate the problems of the OPII failing.
So first I get the string of scores of SYSTEM RESET messages and I ignore it because otherwise the system is running just fine. Then I start getting error messages with my wireless sensors connected via the HAI 42A00-2 wireless received but they are just sporadic trouble signals that "go away" after a time. Then one night (it's always at night) at 4am every wireless sensor reports a trigger, not a trouble code, so all heck breaks loose, alarms go off, etc.
I start disconnecting devices one-by-one trying to get down to a stable system, but no luck. The OPII will no longer connect to several of the serial ports (HiFi2, Somfy URTSII, and the Z-wave interface) as well as the Ethernet port. SOME events run, but some don't...
I reset the EEPROM and started from scratch, nothing improved... I reached to Leviton SARA to see if I can send the board in and they said they're done with HAI. So I started looking for replacements (and what a daunting ugly and expensive job that has been so far).
Have I literally gone wire by wire and disconnected, tested, disconnected, tested? No - because I have literally every single expansion, every single zone, every single everything in use and I'm not even sure where to start in a methodical way. Given the errors "seemed" to begin with the wireless receiver, I could start with the RS485 bus and disconnect that and see if it helps??
@pete_c kindly nudged me here from a tangentially-related thread in the HS forums, thinking it would be worth maybe a last-ditch effort to troubleshoot before I started from scratch.
What else could I provide to any kind/brave souls who might graciously be willing to wade in here?
In short, one day I ran a firmware update on a few of my UniFi WAPs and PoE switch and that afternoon, my OPII system went utterly crazy and died. Correlation does not equal causation and I cannot imagine how these two events would conspire, but there you have it: that was the "trigger event". Prior to this, nothing else had changed or recently been updated or modified on my system. I'm using ~1300 lines of code, and this has been my codebase effectively for years with little change (i.e., I don't suspect any sort of code loop).
The OPII will not hold an Ethernet connection long enough to stay connected and download from PCA - this has ALWAYS been largely the case, and I blame the weak Ethernet port on the OPII, and the fact that I have heavy heavy traffic on my LAN: about 200 IP devices, 25+ 4MP IP cameras, 12+ iPads used as touchscreens (via Myro:Home), multiple PoE WAPs and other devices, and a ton of general network activity via PCs, laptops, servers, Synology storage servers, etc.
Since I'm talking about the LAN: A Ubiquiti USW-Pro-48-PoE powers the PoE side (600W budget, using about 200W of it), plus a few Cisco SG-200-48 switches, running through a Peplink multi-WAN router fed off Verizon LTE as primary ISP and a CenturyLink DSL as backup (we live in the sticks). HAI gear includes the OPII and a HiFi2 (I had the e-mail notifier board but it was junk so took it out). I have tried to connect just my PC and HAI on a small switch separated from the rest of the network traffic and this enables me to get PCA to download a bit better, but did not otherwise obviate the problems of the OPII failing.
So first I get the string of scores of SYSTEM RESET messages and I ignore it because otherwise the system is running just fine. Then I start getting error messages with my wireless sensors connected via the HAI 42A00-2 wireless received but they are just sporadic trouble signals that "go away" after a time. Then one night (it's always at night) at 4am every wireless sensor reports a trigger, not a trouble code, so all heck breaks loose, alarms go off, etc.
I start disconnecting devices one-by-one trying to get down to a stable system, but no luck. The OPII will no longer connect to several of the serial ports (HiFi2, Somfy URTSII, and the Z-wave interface) as well as the Ethernet port. SOME events run, but some don't...
I reset the EEPROM and started from scratch, nothing improved... I reached to Leviton SARA to see if I can send the board in and they said they're done with HAI. So I started looking for replacements (and what a daunting ugly and expensive job that has been so far).
Have I literally gone wire by wire and disconnected, tested, disconnected, tested? No - because I have literally every single expansion, every single zone, every single everything in use and I'm not even sure where to start in a methodical way. Given the errors "seemed" to begin with the wireless receiver, I could start with the RS485 bus and disconnect that and see if it helps??
@pete_c kindly nudged me here from a tangentially-related thread in the HS forums, thinking it would be worth maybe a last-ditch effort to troubleshoot before I started from scratch.
What else could I provide to any kind/brave souls who might graciously be willing to wade in here?
) I tried your "reboot WITHOUT Ethernet" guidance, and it's only been an hour, but gosh if that doesn't seem to be an improvement so far... will keep at it.
