Wireless device goes "missing" - ELK Products

Wireless device goes “missing”

Alarm Engine Support Forum Wireless device goes “missing”

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #9732
    Keith Belt

      I have a 2-way CO monitor connected to the E27 that periodically goes “missing” for no apparent reason, generating nuisance trouble alarms.  There’s no obvious cause:  other wireless sensors (e.g. window switches) don’t report any issues, there’s no electrical problems in the panel, and no radio interference that I’m aware of, etc.   Even while reporting “missing” its also reporting good signal strength (the CO unit is less than ten fee away from the panel) and good battery status.  Not sure how its getting that info if its “missing”.  I have to cycle the power on the main board to restore back, which is kind of a pain.

       

      #9734
      Michael Burrell

        Keith,

        Wireless devices are supervised by system, this is achieved by the devices sending a “check in” signal every 60 mins. The system must see a Security related device checked in at least once in 24 hours to prevent a missing trouble condition. Fire and CO devices must check in once every four hours.

        The missing trouble condition is triggered when the system does not see the CO device send a signal for in four hours.

        If this is not range related it could be a sensor going bad. We’re happy to work with you get it swapped out.

        Thanks,

        Mike

        #9736
        Keith Belt

          Thanks for the fast response — on a Sunday no less!   A follow up:  the keypad started beeping again, so I went back in.  While the Zone is now showing green and OK (the zone was highligted orange before), its also reporting a “missing” trouble again.   And its only been maybe 20 minutes.  The combination of appearing good while also saying its “missing” is maybe even more concerning now.

           

          #9737
          Michael Burrell

            Keith,

            Power cycling the control only clears the trouble. It does not clear the actual condition. Since the device was missing before the power cycle, it will go missing again quickly. A transmission from the CO detector will reset the missing timer, but a power cycle will not.

            To confirm it is communicating with the control, go to Wireless Transmitters and then select the specific Wireless CO detector. At the bottom of the details page there is a section called Testing. If the device has communicated with the control, there will be a signal strength shown. If it shows Unknown, then the system has not talked to it since the power cycle or since it entered the missing condition. If that is the case, check the device, as there could be an issue with it.

            Also, let me know what firmware you are running on the control. We just released an update. We are also planning an app update early in January and are currently flushing out a few bugs. One notable item in the upcoming app update is the ability to update the onboard wireless RF9 board. We have been updating that as well, and it has improved trouble and signal handling. If you are interested, email me at michael.burrell@elkproducts.com with the email tied to your Apple or Android account and I can add you to the beta test for the new app. Just be aware it is beta at the moment, but there are a lot of nice features and improvements in it.

            If that CO detector is not responding, use the same email address to work with me and we will get it swapped out.

            Thanks again,

            Mike

            #9786
            Keith Belt

              Follow-up:

              Last night the CO2 sensor started beeping (about once a minute) while flashing the “fault” light.  The unit had previously been left “disabled” and not reporting, so the E27 did not report  any issues.  I physically removed the unit which is when I discovered that the AAA batteries were damaged.  One had expanded and split open so the battery slot was all corroded.  Its possible I got a bad battery, but I’ve never seen that occur before in a relatively new battery (less than a year old).  Has any one reported a similar experience?  Could a flaw in the power supply of the CO2 sensor cause the battery to be over-drawn, and maybe have been the source of the communications issues?  If you’d like to examine this one, I’d be happy to send it back.

              #9787
              Michael Burrell

                Keith – please work with Tech Support to get that one sent back to us for evaluation. You can email them at techsupport@elkproducts.com. I will give them a heads up to get the CO replaced.

                I agree. It’s either bad battery or device, either way I would like to have engineering look it over.

                thanks

                Mike

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.
              Scroll to Top