I have been using the HAI plugin for about 6 months now and have not experienced any major bugs with it. I decided to upgrade to the new OMNI plugin this week and the upgrade process was for the most part painless.
Unfortunately, I experienced what I believe was a catastrophic failure with the OMNI plugin this morning. My system was working fine and all of a sudden, the HAI system went heywire. Here were all the symptoms during the failure:
1. A number of outputs connected to the system started turning on and off
2. The HAI consoles were for the most part unresponsive
3. I could not connect to the HAI system via Dealer PC Access.
4. The consoles appeared in a system startup mode and were asking me to set the time.
5. I could not get any of the consoles to go into Setup mode.
6. The OMNI plugin was sending some type of "communication error" to the log.
I shutdown HomeSeer to make see if that would fix the problem. It did not.
At this point, I figured that I had experience a failure in the HAI system so I removed power from the system and restarted it. The same problems occurred.
Next, I called HAI tech support. They told me to disconnect all the consoles and sub panels from the system and restart it again. Still, the problem persisted.
Next, I decided to unplug the ethernet cable from the OMNIpro panel. Amazingly, everything started working. The consoles worked again and the system appeared to be operating normally. When I plugged the ethernet cable back into the OMNIPro console, the same set of failures reappeared.
At this point, I concluded that a computer on my network was mounting an attack on the OMNIPro panel. So I shut down the computer that was running HomeSeer.
When I shut the HomeSeer computer down, I found that the "attack" on the OMNIPro panel went away. The panel ran fine with the Ethernet connected.
When I restarted the HomeSeer computer, everything worked fine. No issues what so ever.
My guess is that this failure was caused by a bug in the OMNI plugin. When the bug occurs, the OMNI plugin sends a stream of commands to the HAI panel and ends up overloading the HAI panel processor such that it is not able to operate properly.
Unfortunately, I experienced what I believe was a catastrophic failure with the OMNI plugin this morning. My system was working fine and all of a sudden, the HAI system went heywire. Here were all the symptoms during the failure:
1. A number of outputs connected to the system started turning on and off
2. The HAI consoles were for the most part unresponsive
3. I could not connect to the HAI system via Dealer PC Access.
4. The consoles appeared in a system startup mode and were asking me to set the time.
5. I could not get any of the consoles to go into Setup mode.
6. The OMNI plugin was sending some type of "communication error" to the log.
I shutdown HomeSeer to make see if that would fix the problem. It did not.
At this point, I figured that I had experience a failure in the HAI system so I removed power from the system and restarted it. The same problems occurred.
Next, I called HAI tech support. They told me to disconnect all the consoles and sub panels from the system and restart it again. Still, the problem persisted.
Next, I decided to unplug the ethernet cable from the OMNIpro panel. Amazingly, everything started working. The consoles worked again and the system appeared to be operating normally. When I plugged the ethernet cable back into the OMNIPro console, the same set of failures reappeared.
At this point, I concluded that a computer on my network was mounting an attack on the OMNIPro panel. So I shut down the computer that was running HomeSeer.
When I shut the HomeSeer computer down, I found that the "attack" on the OMNIPro panel went away. The panel ran fine with the Ethernet connected.
When I restarted the HomeSeer computer, everything worked fine. No issues what so ever.
My guess is that this failure was caused by a bug in the OMNI plugin. When the bug occurs, the OMNI plugin sends a stream of commands to the HAI panel and ends up overloading the HAI panel processor such that it is not able to operate properly.
Comment