3.13 Weirdness

[pete_c]

25th of May, 2014 - quiet; no smoke chirps / UPB wierdness and everything appeared to work fine since yesterday. 
 
27th of May, 2014 - chirping early this morning; continuously.  Following the chirping to a 120VAC installed smoke.  Eating my previous words here. Must have been a bad battery that was installed as previously stated. 
 
HAI OPII firmware appears stable. 
 
Unrelated....Concurrently here adding a few Omnpro Wintel touchscreens to the already installed in wall Omnitouch IP connected screens.  Doing this with my tabletop "do whats".  The IP camera connections that work fine with the Omnitouch 5.7e's do not work with the Omnitouch Pro software. (tabletops are all over the house; literally). 

 

[fabriziojoe]

Last evening I had a hardwired 3M CO2 push out a trouble. 5 minutes later all wireless zones went into a not ready status and then every hardwired zone tripped.
The controller then locked up and some of the keypads were showing "no communication" and another keypad displayed "No Controller Data43 cMEP435.
I removed all of the batteries and powered down the system. I reconnected all batteries and then powered the system back up-everything appears stable as of now.
The only change made to the system was the addition of the notifier board-this is now disconnected for the time being.

 

[ano]

Last evening I had a hardwired 3M CO2 push out a trouble. 5 minutes later all wireless zones went into a not ready status and then every hardwired zone tripped.
The controller then locked up and some of the keypads were showing "no communication" and another keypad displayed "No Controller Data43 cMEP435.
I removed all of the batteries and powered down the system. I reconnected all batteries and then powered the system back up-everything appears stable as of now.
The only change made to the system was the addition of the notifier board-this is now disconnected for the time being.

Yeah, that sounds similar to what happened to me. First some trouble alarms, then all wireless zones changing to "not ready."  That is bad news that this can happen to just a running system.

 

[fabriziojoe]

Last evening I had a hardwired 3M CO2 push out a trouble. 5 minutes later all wireless zones went into a not ready status and then every hardwired zone tripped.
The controller then locked up and some of the keypads were showing "no communication" and another keypad displayed "No Controller Data43 cMEP435.
I removed all of the batteries and powered down the system. I reconnected all batteries and then powered the system back up-everything appears stable as of now.
The only change made to the system was the addition of the notifier board-this is now disconnected for the time being.

Still receiving random beeps. I am going to write some logging rules to see if I can tell if it is a bad zone or bad firmware-leaning towards bad firmware.

 

[JonW]

I had disabled the keypad beeps when my system first started acting up on 3.13, but during the night my keypads still come out of sleep and light up the room.  I still see the same activity on them.  Sometimes there is a continuous 33333 being pressed (both keypads) and sometimes I'll see the "No Controller Data" error.  The errors go away very quickly, so I don't always see them and nothing is ever logged.
 
I just reflashed my board this morning and downloaded the config again.  I've got the new e-mail notifier board, but have not installed it yet, so the issue is firmware, not the new hardware.
 
Due to the wireless zone troubles and the keypad troubles, I'm guessing there is some kind of bug affecting the keypad bus.

 

[pete_c]

Sometimes there is a continuous 33333 being pressed (both keypads)

 
@jonw - so you see this on the keypads? 
 
Its been quiet now here relating to smoke's / beeps.
 
Last week I also had an issue with a couple of loose cats triggering my outdoor sensors (well and causing some beeping at 4 AM walking me up).   2nd or 3rd time this happened did a visual and saw the cats on the CCTV recordings.
 
I have moved the network connection to the main network in the house.  That said I am not seeing any real time sync problems, serial com issues nor networking issues with the panel and devices plugged into it.
 
Unrelated ....got the TP-Link TL-WR710N micro router which I am modifying adding more memory and swapping out the OS and connecting it serially and network wise to the panel.  Tiny router; very impressive and it will fit fine inside of the HAI MM can and take its power from the panel.

 

[JonW]

@pete_c - yes, I would see 333 on the keypads.  It's just like if you sat there and pressed the 3 key multiple times.  It would error and beep at you as an invalid input.  At first I thought it might be a stuck key, but then the second keypad was showing the same behavior.  With the wireless issues that others are seeing and the keypad issues I'm seeing, I really think this is something messed up in the firmware relating to the keypad bus.

 

[pete_c]

Yeah here I only have one keypad connected directly to the console and the rest of the legacy consoles are connected to the Omnitouch Hub.
 
Collecting HAI stuff here I do have two 45A00-1's and one 42A00-2 that I could test maybe.  (In FL have one still connected but mostly relating to testing only).  Test connected the devices once a while ago.  They are just sitting in their boxes unused (years now) these days.
 
Which of the two above are you using today?
 
Unrelated....
 
When I had the serial com issue / IP com issue it would crop up initially with the serially connected Omnistat values being incorrect on the Omnitouch screens (well and keypads) then go over to the network connected devices "disconnecting" them and concurrently time would go way off...minutes off per hour timeframe.  Here is what I would see:
 
1 - time going way off
2 - Omnistat com to OPII panel to Omnitouch screens would show wrong temps and do weird stuff with Omnistat  (I didn't really pay attention to the Russound serial connection and probably should have).  Lighting PIMs all worked fine. (UPB, Z-Wave and X-10)
3 - IP transport would go to the dumps (for everything connected via IP)
 
My fix to the above was just to move the network interface to a separate autonomous network (not a VLAN).  Been working fine in this fashion now for many months.  Recently though moved the network interface back to the main network.  It's been working fine now over the last few days.