Network trouble slow to clear from keypad

[Keith Belt]

I accidentally momentarily disconected the cable modem.  It triggered a “network” TROUBLE event, which was quickly acknowleged and RESTORED.  The main keypad screen however, continued to indicate a TROUBLE event >>, for several minutes.  When I scrolled right, it said “No troubles”, and when scroll left back to the main screen, it still said there is a TROUBLE>>.  The app cleared quickly saying there are no troubles. But the main keypad screen took a long time to catch up and clear.

[Michael Burrell]

Troubles on the keypad can take as longer to clear. This is intentional implemented due to the requirement of a pin number to silence of trouble. The way the keypad works is if you activate a trouble and you silence, it will not sound a trouble again until the keypad sees the trouble clear and reactive or a new trouble is detected. If the keypad did not have a delay, a trouble that comes and goes quickly would create an issue of not being able to silence it. For example, the network dropping in and out. We felt the delay was the better choice than the need to continually silence.

This delay was shortened in Control Firmware 0.5.22 and Keypad Firmware 0.2.40. I believe it used to be a longer delay and we did have a “sync” issue with the troubles not clearing quick enough on the keypad in older firmware.

Please confirm your control and keypad are running the most updated firmware.

E27CB – Control – 0.5.22 Firmware

AEKP – Keypad – 0.2.40 Firmware

Edit: I just reviewed the internal release notes and it appears some general timings were adjusted in 0.2.40 Keypad Firmware. Not sure if it addressed the trouble timings or not, but I do know that we touched the timings in that keypad firmware.

[Author]

Posts