HSM02 door sensor untrip fails
-
I'm going to throw this in here, but I don't actually expect a solution, but it might help someone else.
I have three of these magnetic sensors and the work. Kind of.
The issue is that if you open and close the door within about 2 seconds, they trip correctly and then will not untrip unless the door is opened and closed (for more than about 2 seconds) .
This makes them virtually useless for any security application unless you are very slow through the doors.
Even forcing setting 'Tripped' to zero using lua fails. Well it doesn't fail but it's simply reversed:
2020-07-03 15:01:24.783 luup_log:0: ALTUI: runLua(luup.variable_set("urn:micasaverde-com:serviceId:SecuritySensor1", "Tripped", "0", 20780) 2020-07-03 15:01:24.783 luup.variable_set:: 20780.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 1 now: 0 #hooks:0 2020-07-03 15:01:25.044 luup.variable_set:: 20780.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:0
So there it is. Unless anyone has any smart ideas (apart from not opening and closing the doors quickly, I'd avoid buying these.
(PS the only apparent setting that might affect this is the the delay before sending 'untripped' but even setting that to 10 seconds makes no difference. In short, it seems that thee devices have a hardware limitation in how soon they can be tripped.
C
-
I have a pretty funny story about these sensors. They were my first zwave compact door sensors and they all worked reasonably well. Eventually what made me swap them out was the battery consumption and their relatively higher cost of button batteries on the vera. Shortly after swapping them all out but one, I first discovers the vera dreadfull wakeup nnu which was sucking out their batteries... So I kept my one leftover device for over 4 months without battery change until I moved to z-way and ran it until the last set of battery got consumed and moved to zwave+ sensors with AAA rechargeable batteries.