Envisalink web shows zones opposite of their actual state

[erkme73]

I've had the EVL3 on my DSC1551 at my primary home working like champ for the last few years. I'm running 100% wireless sensors throughout the home (26 of them). Never an issue with the EVL3's LAN IP showing realtime what the state of each sensor is... including how long ago they closed.

So, have just built a vacation home, I installed a DSC1864 (4.6 firmware), three RFK5564 wireless keypads, and the latest EVL3 (running 01.07.88).

All appears to be working well, as all three keyboard LCD's show precisely which zones are open/closed. However, when I log into the EVL3's LAN IP, about half of the sensors show the wrong state - and those that show closed, show "Closed: 0 min ago" on zones that have been closed for hours.

Am I missing a critical setting either on the EVL or the DSC panel/keypad?

As a consequence, any device pulling data from the EVL (including my home automation VERA Edge) reports inaccurate zone statuses.

Any ideas?

[GrandWizard]

That's EVL factory firmware and has all sorts of bugs. You need the latest firmware. If the module hasn't downloaded it already you have some sort of networking problem. Submit a tech support ticket and we can help you out there.

[erkme73]

That's EVL factory firmware and has all sorts of bugs. You need the latest firmware. If the module hasn't downloaded it already you have some sort of networking problem. Submit a tech support ticket and we can help you out there.

Thanks for pointing me in the right direction. Firmware 1.07.88 is A BIT dated, I see. I had set the DHCP to static, and never realized that it was unable to connect to the eyezon servers (I don't use that feature). I turned on the DHCP again, and restarted the EVL. When it came back up, the IP, subnet, and domain remained unchanged (I have the IP assigned statically on the router), but this time, it connected. It's still showing the old firmware, but suspect that will update automatically?

Thanks again...

ETA: yup - it updated to 01.12.172! Fingers crossed.

I thought perhaps because I have THREE wireless keypads (RFK5564) they weren't playing nice - so I ordered two non-RF keypads. They'll get here tomorrow, but if by then I can tell the problem is resolved, I'll return them (Amazon!).

Thanks