Elk M1G Firmware/Software updates caused big issues

deirwin

New Member
I was having issues with ELK not properly synching with software, and of course, the annual time change issues.  So, I udpated everything I could (using Windows 10 PC).  On first glance, it appeared perfect, but then showed confilcts with two thermostats.  I tried to update many time, and it looked like it worked each time, but when I would close-out of RP, It showed conflict.  No most or everything shows as a conflict.  Anyone have any insight or same experience?
Thanks! Dean
 
Did you back up the customer account before you made the updates? If yes then I would create a new customer account and import the back-up accoune. If not then next I would try creating a new account and uploading everthing from teh Elk system to RP2.
 
Mike.
 
I was coming to create a new topic, but will add my experience here.
 
Since I updated to the latest firmware, whenever I reset the panel, all Honeywell wireless zones show "VIOLATED" status and all fire and C/O detectors show "TROUBLE" status.
 
The only was I have found to clear them is to walk around and open, then close each wireless zone (door / window), set off each glass-break by knocking on it with keys, and open each smoke detector (triggering an actual trouble), and then acknowledge at the panel.
 
Once I do this for EVERY zone, all seems well unless I have to reset agian.  Very annoying.
 
Any thoughts? 
 
kevkmartin said:
I was coming to create a new topic, but will add my experience here.
 
Since I updated to the latest firmware, whenever I reset the panel, all Honeywell wireless zones show "VIOLATED" status and all fire and C/O detectors show "TROUBLE" status.
 
The only was I have found to clear them is to walk around and open, then close each wireless zone (door / window), set off each glass-break by knocking on it with keys, and open each smoke detector (triggering an actual trouble), and then acknowledge at the panel.
 
Once I do this for EVERY zone, all seems well unless I have to reset agian.  Very annoying.
 
Any thoughts? 
Only that the Elk 2way wireless behaves the same way
 
mikefamig said:
Only that the Elk 2way wireless behaves the same way
 
Mike - is this the problem you were referring to in this other thread?  If so, those zone problems clear for you by themselves 30-60 seconds after the reboot, right?  @kevkmartin's problem sounds different to me in that he has to manually operate each zone for them to clear.   Or did I miss something?
 
RAL said:
Mike - is this the problem you were referring to in this other thread?  If so, those zone problems clear for you by themselves 30-60 seconds after the reboot, right? 
When I cycle the power on the panel wireless zones start up incorrectly. I am not sure if closed zones appear open of visa versa but I do remember that they are not reporting correctly. I have never waited any length of time to see if they clear themselves because there are only three doors and they are near each other so I go around and open and close the doors and they correct themselves. I have always accepted it normal.
 
Mike.
 
I don't think this is "normal". It is very difficult / inconvenient to resolve; I am concerned what the impact would be if the system lost power in an armed state.

I have 29 wireless zones, and 9 fire zones. Some of them require a ladder to open / close or reset trouble.

I waited nearly an hour today; zones did not reset themselves until I manually cycled them.

This was NOT the behavior prior to firmware update on the m1 main board.
 
I do not have wireless included in system. @mikefamig, I tried creating a new account and and using backup and also loading from ELK to RP.  Same result.  But, now that most, or everything maybe, is a conflict I'm worried.  I did notice I have an R1BU1C, whoes LED is not lit up, but not sure if related.
 
Dean-oh said:
I do not have wireless included in system. @mikefamig, I tried creating a new account and and using backup and also loading from ELK to RP.  Same result.  But, now that most, or everything maybe, is a conflict I'm worried.  I did notice I have an R1BU1C, whoes LED is not lit up, but not sure if related.
 
Have you posted the question on the Elk tech support forum? Brad there is very good. Don't give up hope. I had a similar problem where RP2 kept reporting conflicts no matter what I tried but I can't remember how I solved it. I believe that it was a setting that I had overlooked.
 
Mike.
 
I called ELK tech support today, and they were very aware of the issue.
 
They suggested - for systems that DO NOT need to meet UL Listing certification, that unchecking the "UL Wireless Jam Detect" box on the Globals => Special tab in ELK RP would solve the issue.
 
This appears to have fixed the issue for me.  I'm not certain what the consequences of doing this are; they did not indicate if a "fix" is coming in a future update.
 
Hope this helps others (or maybe helps me to learn why I should / shouldn't do this vs. walking the sensors every time I reboot).
 
Back
Top