3.13 Weirdness

Did anyone have any weirdness when updating an OMNI Pro II to 3.13 firmware?  I certainly did.  It downloaded and installed fine, and the panel rebooted like normal.  Keyboards started beeping "no communication" like normal, then things went downhill from there.  All wireless zones were reporting "not ready" and the two wireless smoke alarms that I have started reporting trouble.  About then I started getting emails from the alarm company, so I called them to cancel any false alarms.  I waited a bit, but things didn't resolve themselves.  I had to disconnect the battery from the panel and unplug it to reset it. It eventually restarted O.K. but took what seemed like a bit longer than normal before I could communicate with PC Access. 
 
It seems to be fine now.

Today/Tonight while in the basement work shop I did here a chirp from one of wired to the panel smoke detectors / CO detectors. 
 
I didn't pay attention until your post tonight.  Haven't noticed anything else weird since the update. 
 
I enabled the HAI logger program tonight.
 
Turning the logger on and off about 3 times noticed each time it started the time needed to sync up which is sort of odd as I haven't seen this before doing similar.
 
20th, May, 2014 - 0747c nothing noticed this morning. No wireless sensors configured here.

I didn't have any issues with this past firmware but had issues like you are describing in others. I always had to unplug the panel battery and kill the power to get things back. SJ

WOW - I thought it was just me with the gremlins!  My keypads started beeping randomly.  On one of them, it looked like the button "3" was being pressed repeatedly.  The screen showed it going into macros, then doing an error beep like 3333 was being pressed.  I thought maybe it was going bad since we use macros (button 3) on that keypad a lot.  Last night I had to unplug both keypads in the middle of the night because they wouldn't quit randomly beeping.  The second keypad never showed any messages when it was beeping.  This morning I plugged them both back in and disabled keypad beeps and key clicks, so not sure if the problem is gone or not.  Maybe I'll re-enable the keypad beeps when I get home and monitor it for a bit, then downgrade the firmware to see if it fixes it.

Here I shut down the HAILogger and re-enabled it after 24 hours and the clock was off some 5 minutes. 
 
I haven't heard any random beeps.   I did get one call / email from alarm company yesterday. 
 
It was a non descriptive something is wrong with my panel thing.
 

Trouble signal received: System Peripheral Trouble: HAI Hub on 20th of May, 2014 at around 8PM

Click to expand...

 
I did notice that my Omnitouch 5.7e's are having issues connecting to OPII.   My legacy Omnitouch 5.7's are fine.
 
Its like they do not see the OPII anymore.  I have disconnected and reset them a couple of times.  I wasn't paying attention.
 
This is an issue for me and I will for the time being downgrade back to previous FW version.
 
Downgraded back to FW 3.12 this morning at around 0800c.
 
Still having an issue with the Omnitouch 5.7e's connecting to the OPII.  I just redid the FW update on one of them; keyed in all of the stuff from scratch and it still will not connect staying at the "connecting screen"
 
Well its not an issue with the Omnitouch screens.  Looks like the OPII ethernet port is not up and working.  No blinking lights on port.
 
I just unplugged power and battery and it did not come up. 
 
The downgrade appears to have reset a bunch of stuff.  The IP changed.  I manually reset the IP with the keypad and was able to get into the panel. 
 
I just uploaded the configuration with the 3.12 FW instead of the one I had saved with the 3.13 FW.  Looking better now.
 
What a PITA this is to do.  Still having IP connectivity issues at 1030c this morning.
 
1100c - thinking I am OK now.  Omnitouch 5.7e's connecting fine. 
 
I also moved the network connection to main house network to get it going. 
 
I am though changing it anyways to the little mini combo firewall router serial connection box in the panel in the next few days....
 
Personally here thought that the network hardware issues were set in stone. 
 
Now wondering if HAI tried to fix something relating to the network stuff.

23rd May, 2013 - 0522c
 
Relating to downgrade to HAI OPII FW 3.12 all appears fine.    Not noticing the repetitive time syncs, network/serial com is good.
 
Note here that my only "weirdness" was that I heard a smoke chirp in one zone.  I didn't notice anything else.
 
The only issue I had was the IP change to default with downgrading.  Nothing else changed from what I could tell.
 
Unrelated / related modifying the tiny little TP-Link travel router upping the play space on it to 8 or 16 Gb and removing the HV stuff from it in the next few days.  I am installing OpenWRT on the TP-Link combo box.  I will move this endeavor over to a new blog. 

I had similar problems.  I have never had a problem with firmware upgrades before, but this time it was a mess.
 
Flashed to 3.13 with PCAccess, the panel rebooted.  I was able to re-connect with PCA but my OT7, HaikuHelper, and Haiku on my phone all wouldn't connect.  Then I noticed none of the automation was running, and security via wireless sensors was all jacked up.  Several power cycles didn't help.  However I know the DCM was working because Alarm Relay called me saying the panel was reporting a battery low trouble.
 
I downgraded to 3.12, and that erased the entire panel.  I had to re-set the IP settings to get back in via PCA and upload everything.  Once I did that everything was working again.
 
I waited 24 hours, and bravely re-flashed to 3.13 and this time it worked fine.
 
So I don't know what happened, I didn't even post about it because I just had a fluke incident.  But apparently not....

So your upgrade back to 3.13 is looking OK eh?

After upgrading to 3.13, you should reupload the entire controller configuration using PC Access. This seems to help.

Pete - Yeah things are working quite well on 3.13 now.  Combined with the new OT7 firmware there are some really nice interface improvements.  Probably my favorite is that the OT7 no longer has a spastic beeping fit after you disarm the alarm during the entry delay.  You get instant feedback that it's disarmed, and the beeping stops.
 
Lupinglade - Yeah, I had tried pushing the programming back to the board the first time I flashed it to 3.13 but that didn't help.  In fact, it made things worse as Haiku would crash as soon as I picked the controller.
 
Downgrading, re-uploading, upgrading back to 3.13, re-uploading, lastly power cycle.  That's what worked for me.

Yeah; here when I downgraded uploaded last saved 3.12 configuration.
 
So then today will upgrade again to 3.13, upload again saved 3.12 configuration, power cycle and finally save the newer 3.13 configuration.
 
Updated back to FW 3.13 and saved newest configuration.  Looks OK so far.

I redownloaded everything from PC Access into the panel and that seems to have solved those problems. Never had any problems with HAIKu (on an iPad) but HAIKu Helper (on a Mac) had connection problems to the panel with 3.13.  I rebooted the Mac, and it seems to be working now, but one weird thing is on the HAIKu Helper web page says WEATHER NOT AVAILABLE Check Weather Location Preferences in HaikuHelper. I checked the preferences and they are fine. Maybe the weather web site is down. Otherwise, I think everything is working.

Yesterday night I went to PCA and while navigating around in the application did notice a few "chirps" coming from the smokes which I have never heard while using PCA. 
 
Wife mentioned to me some early morning "chirping" from the HAI smokes. 
 
Note that this happened without running PCA but connecting to the panel with some IP consoles in place.
 
No central station calls here though.  Nothing in the HAI Logger program that I can see out of the ordinary.
 
Thinking about last night now did notice while watching a movie around 9 PM the UPB lighting dimmed and went off at an unscheduled time where the schedule is to shut them off around midnight. (three UPB switches and single link)
 
With the above I am thinking there is some sort of issue still with the 3.13 HAI OPII firmware upgrade.

Are you sure its the panel smokes that are chirping and not the internected battery smokes? I know in my house, its a challange to tell exactly what is chirping.  Smokes with a battery almost always start chirping in the early morning, because that is when the house is the coolest, and the battery has the lowest voltage.  If its a smoke without a battery that is chirping, that isn't a good sign. I'd replace it.

Thank-you ano
 

Are you sure its the panel smokes that are chirping and not the internected battery smokes?

Click to expand...

 
The chirping here is different between the 120VAC- Battery interconnected smokes and the HAI OPII panel connected smokes.  It is a PITA to listen for cuz the sound is sort of omnidirectional. 
 
I did recently replace all of the interconnected smoke batteries around the last "spring ahead"  time change and and and did replace one smoke detector with a new one.
 
The one I heard in the basement though is about 20 feet from the other one.  The other day as the chirping didn't stop right away; followed it to the source.
 
I haven't heard anything at all today though; just what wife mentioned.