EyezOn Forum

Ok, thanks. I thought I'd try here first, just in case its common and had a trivial fix. I guess, no such luck.

Coincident with a recent update to the Envisalink_new integration in Home assistant (3rd party), my two keypads have "locked up". That is, they both show 12:00AM / OPEN / green READY LED, and the keys do absolutely nothing. In addition, the two keypads sound their chime every 2 seconds, endlessly ...

Your DSC FOBS should just work like they did before as they are still programmed into the 5132. We are currently working on FOB programming so there is no way to make changes yet. Yup, the two fobs - all four buttons - work fine, even though I haven't added them via ESN under Settings / Fobs ...

The UNO is advanced enough to be able to download all of the settings within the PC5132 open power-up and after about 30 seconds you will see all of this programming in your local Zones programming page of the portal. Its really cool. Huh ... then I might have some problem but not sure. I did the ...

Thanks - I've already downloaded and read the manuals, and spent some time on the phone talking with support. Everyone I've communicated with about this transition has been patient and forthcoming with info. The outcome of the phone conversation told me more or less the same thing you mentioned ...

I recently bought the EyezOn UNO-IP (confusingly packaged as the Connect2Go UNO-IP Hybrid Security Alarm System) replacement board for my aging Power832 (PC5010) alarm motherboard. For the past 6+ yrs I've been interfacing to the PC5010 via an EVL4 board ... worked great once the initial bugs were ...

I know this thread is ancient by most fora standards, but ... what's the consequence of ignoring the delinquency message? I got this terse message today on the one month anniversary of the last time I armed-disarmed my system via the EnvisaLink 4 card and EyezOn iOS app. Now that I know what it ...

I've submitted a support request via the Portal, under "Alerts and Messages" and mentioned that I posted the issue here in the forums. Hope that's sufficient - if not, let me know what you need me to provide. I kinda wondered why this debug "info" just gets output and repeated over and over, it made ...

Is there a way to either fine tune the debug entries in my syslog files, or disable debug logging while leaving the general event logging enabled? Not that I never ever want to see debug info, but if all I ever get is as follows, when the EnvisaLink is running ok: xxx@deb-box:/var/log$ sudo cat ...