Regression: Vision tilt sensor stays tripped

Other Devices & Integrations Door Locks & Sensors
#1

This started happening on my Vera Lite in the last month or so. 1.7.619 exhibits the problem but it might not be the first firmware that demonstrated it.

Symptom: My Vision Garage Door Tilt sensor stays tripped even when the garage door is closed. Actually, it quickly switches from tripped to untripped and then immediately back to tripped.

I know that the sensor is physically fine because I can see the state change in the log when I tilt the sensor to the untripped position in my hand:

06 08/15/15 15:16:34.175 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastUntrip was: 1439615731 now: 1439615794 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2bbc7680> 06 08/15/15 15:16:34.176 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastUntripAlert was: 1439615731 now: 1439615794 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2bbc7680> 06 08/15/15 15:16:34.177 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0xe7e4f8/NONE duplicate:0 <0x2bbc7680> 06 08/15/15 15:16:34.178 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: ArmedTripped was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x111b340/DL_ARMEDTRIPPED duplicate:1 <0x2bbc7680> 06 08/15/15 15:16:34.205 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1439615731 now: 1439615794 #hooks: 0 upnp: 0 skip: 0 v:0x11262b8/NONE duplicate:0 <0x2bbc7680> 06 08/15/15 15:16:34.206 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTripAlert was: 1439615731 now: 1439615794 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2bbc7680> 06 08/15/15 15:16:34.207 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xe7e4f8/NONE duplicate:0 <0x2bbc7680> 35 08/15/15 15:16:34.208 Device_Basic::ProcessSensorTrip device: 158 ignore 1:C;2:C;3:C;4:C/1 armed:0 <0x2bbc7680> 02 08/15/15 15:16:34.208 ZWaveNode::HandlePollUpdate_Alarm node 42 device 158 v1type: 7 v1level: 0 source: 0 status: 255 type: 7 event: 2 parms: 0 code: TRIP_ALARM <0x2bbc7680>

and then when I tilt the sensor into the tripped position I see:

02 08/15/15 15:16:29.025 ZWaveNode::HandlePollUpdate_Alarm node 42 device 158 v1type: 7 v1level: 255 source: 0 status: 255 type: 7 event: 2 parms: 0 code: TRIP_ALARM <0x2bbc7680> 06 08/15/15 15:16:29.026 Device_Variable::m_szValue_set device: 158 service: urn:micasaverde-com:serviceId:HaDevice1 variable: sl_Alarm was: TRIP_ALARM now: TRIP_ALARM #hooks: 0 upnp: 0 skip: 0 v:0x1088bb8/SL_ALARM duplicate:0 <0x2bbc7680>

Note the v1level value switches between 0 and 255.

The battery is at 83% and it seems to have gone through configuration properly.

I’ll raise a support ticket. This post is just to keep tabs on MCV’s progress in fixing the regression.

#2

Mine does the same thing or really never would clear, I put in a ticket a month or so ago. Vera Support said they would fix it with the next update but it never happened. Hopefully they can get it to work.

#3

Mine has started giving some false alarms, and it would normally have to be open for an hour for that to happen.

Sent from my iPad using Tapatalk

#4

Same here with the ZD2102 during, I guess, the heal of the network in the night…
(just triggers the perimeter alarm >:()

#5

MCV replied on the fifth day to say that the bug had already been reported and that it would be fixed in a future firmware release.

Thus nicely demonstrating all of the problems with their support model.

[ul][li]Without a publicly visible bug tracking system, I can’t know if a problem I experience is already known, or how many other people it affects, or if there is a workaround.[/li]
[li]The only fix offered is for me to wait for a future firmware release that will most probably introduce its own regressions.[/li][/ul]

If I really want this sensor to work today my only option is to downgrade the firmware to a version (not sure which) that doesn’t demonstrate the regression. I’d rather spend my time moving more of my setup over to OpenHab.

#6

I’ll continue in this other thread which predates mine.

#7

Two new firmwares and still not fixed… What kind of lip service are they giving??