EVL3 (EnvisaLink3) incorrectly showing zones as tripped

Other Devices & Integrations Door Locks & Sensors
#1

My EVL3 has been working fine for years, even with 2 different Veras. Now, today, it’s showing zones as tripped (open) even though they are not and the DSC alarm panel also says that they are not open.

So I logged into the EVL3 and it’s showing that those zones in dark red and hovering shows “closed: xxx minutes ago”. It seems this it’s no longer, as of today, showing the real-time status and a “dark red zone”, meaning it was closed a wile ago, is still being reported as tripped.

I rebooted the EVL3 . No change. EVL FW is 01.12.191. The FW didn’t change recently, the plugin to vera didn’t change … what’s going on?

Any ideas?

#2

This occasionally happens to me and usually fixes itself or a reload of the LUUP engine does the trick

#3

I re-sync my Vera to my EVL3 on a scheduled basis. I would occasionally find a device out of sync, and this takes care of that:

if (luup.is_ready(14) == true) then
luup.call_action(“urn:micasaverde-com:serviceId:DSCAlarmPanel1”, “SendCommand”, {Command=“001”}, 14)
end