New "*29 Programming on panel not complete properly" error

[CyborgOne]

Honeywell Vista 20P panel, with Envisalink 3 module attached and configured.

Has been working perfectly for the last year or so.

As of approximately 2 days ago, I'm not able to arm my alarm at all - not via the keypads, and not via the EVL-3 "Eyez-On" web interface. Attempts to arm by entering an appropriate code and hitting "Away", do … nothing. No errors, no "not ready" indications, etc.

Nothing has changed with my system, all sensors appear to be reporting correctly, etc. I get zero feedback from the keypads as to anything which would prevent the system from being armed.

The only hint I have as to the issue is the "Warnings & Errors" dialog indicated within the web app, which gives the above error:

*29 Programming on panel not completed properly.

When initially installing the module, this field was set to "1", as instructed. Again, nothing has changed with this setup in the past several months - but now I'm not able to arm the system at all.

What has caused this issue, and how do I recover from it?

[CyborgOne]

Now resolved. Documenting here, for the benefit of anyone else who might encounter a similar issue.

I had also sent a support request directly to Eyez-On, who responded in email that someone must have gotten in and reprogrammed the panel, removing the correct setting for field *29. However, this was verifiably not the case - as neither my wife nor I (the only ones aware of the applicable user codes) had even attempted any change to programming. No changes to configuration for several months.

So, I also spoke directly to Eyez-On tech support this morning via phone: They verified the issue, and that when entering the (correct) user codes, accompanied by commands to arm or disarm the system, those commands were being recognized (i.e. correct codes, valid commands) - but not acted upon.

We ended up power cycling the panel itself, and the tech support rep also remotely rebooted the EVL-3 module. After everything came up again, it appears to now be working normally - with no errors indicated, and no functional issues apparent any longer.

None of us have any idea what lead to the original issue, but the moral of the story seems to be: When in doubt, cycle power