Random "Events" Occurring: HAI Omni LTe

[mdruno]

I do not have a wireless receiver. Not much on my system. Omnipro II with expansion board, 6 keypads, 2 areas, 4 thermostats, outdoor temp sensor and 7 ALC. When this happens, I lose control of my ALC's. Thermostats are fine.

 

[mdruno]

I also have the Omni Notifier board. Running version 4.0B.

 

[pete_c]

Are you using the network interface?

Test by disconnecting the Ethernet interface(s) and doing a power off (battery and transformer) rebooting and watching to see if it happens again in a day or two.

 

[dwalt]

After doing what Pete suggests, you may want to disconnect the keypads, one at a time. It can be something on the keypad bus.

 

[mdruno]

Are you using the network interface?

Test by disconnecting the Ethernet interface(s) and doing a power off (battery and transformer) rebooting and watching to see if it happens again in a day or two.

Thanks for your input. I did that last night. I will keep my fingers crossed.

 

[mdruno]

After doing what Pete suggests, you may want to disconnect the keypads, one at a time. It can be something on the keypad bus.

Thanks. I will try that. I even changed keypad address for grins and giggles.

 

[pete_c]

Welcome to the Cocootech forum @mdruno .

 

[mdruno]

It happened again last night. It lasted about 36 hours. The keypad did not shoe button 333 tis time but the same issues, ALC control is gone, perimeter beeps do not work and the keypads do not beep. While in PCAccess I noticed thermostat current temperature went to zero for about 15 seconds. I will now start removing keypads. Is there any way in the automation programming that I can reset the RAM ?

 

[jeremyg]

FYI for the forum. I have a 45A00 wireless receiver, 2 keypads and 2 touchscreens, and had been experiencing the random beeps and all on/all off events, and random thermostat setting changes.

I tried swapping the affected keypad console with a new keypad, changed console addresses, even re-spliced some connections, but the problem was not resolved.

I disconnected the 45A00 wireless receiver and the issue went away. Now on to try an alternative wireless solution...