Sometimes my motion sensor stops working and needs a power cycle to start working again. I noticed that very often when it stops detecting motion, it also has stopped reporting luminance. So I could use a trigger where if the timestamp has not been changed for x minutes... then I can use a on/off module to power cycle automatically (I do that manually now). I had a look in easytrigger, I thought there was a condition there but cant find it. I cannot use if the value hasnt changed for x time, as at night its stuck on 2 Lux for a long time, but I think the time stamp still changes
Announcement
Collapse
No announcement yet.
Trigger event on no change on device timestamp not changed for x minutes
Collapse
X
-
Originally posted by mikee123 View PostThe problem is at night (2 Lux) or when its bright during the day (2000 lux) the device value does not change. But the time stamp updates.
Comment
-
Yes that should work. Then trigger the timer. My brain is not switched on today I think
It does work. Just set up the event and timer. Now I need to try to find out what time of no change I should use to reboot the sensor. At the moment I am only sending notifications on 10 minutes no change. Lets see how that works. Trial and error now trying to find the sweet spot
Comment
-
I run a script every ten minutes that check all kinds of things and perform automation tasks. This allows me to simulate events that do not exist in HS3. If cheap RF temp sensor enters a range, turn floor heat on, etc. If garage door has been open for more than 30 minutes, announce message on sonos speakers and leave notification on Alexa speakers. You could do same here, checking if the datetime of device is older than xxx seconds.tenholde
Comment
-
Originally posted by mikee123 View PostNow I need to try to find out what time of no change I should use to reboot the sensor. At the moment I am only sending notifications on 10 minutes no change.
As far as "what time..." I'm not clear about what you mean for "I am only sending notifications on 10 minutes no change".
The one I use is an Aeon Multi-sensor 6 (Powered). It report every few seconds so let's say the time stamp changes +/- every 5 Sec. I would probably start to worry if the timer reaches >15 Sec. It depends on how critical the application is.
Comment
-
The motion sensor is a mains powered Steinel IS140 Z-Wave. I have the same sensor not far away on my garage, never had an issue. I thought it was a faulty sensor, so I swapped it for a new one. Stuck after just a day... weird.
Even more strange. The sensor has a z-wave controllable switch. That still reacts. Just the motion sensor does not report any movement any more until I power cycle.
Comment
-
Originally posted by mikee123 View PostSometimes my motion sensor stops working and needs a power cycle to start working again. I noticed that very often when it stops detecting motion, it also has stopped reporting luminance. So I could use a trigger where if the timestamp has not been changed for x minutes... then I can use a on/off module to power cycle automatically (I do that manually now). I had a look in easytrigger, I thought there was a condition there but cant find it. I cannot use if the value hasnt changed for x time, as at night its stuck on 2 Lux for a long time, but I think the time stamp still changesCode:Sub Main(ByVal Parm As Object) Try Dim ListOfDevices() As Integer = {280, 278, 270, 269, 137, 89, 136, 134, 122, 125, 134, 133, 124} 'Boiler Supply, Boiler Return, BP S, BP R, LR S, LR R, MBR S, MBR R, RO S, RO R, MO S, MO R For Each Device As Integer In ListOfDevices If hs.DeviceTime(Device) > 45 Then hs.triggerevent("Bump heating valves") End If If hs.DeviceTime(Device) > 50 Then hs.writelog("Sensor Error", “”& hs.DeviceName(Device) & " has not updated in over " & hs.DeviceTime(Device) & " minutes") End If Next Catch ex As Exception : hs.writelog("DeviceLastChange", "Error: " & ex.message) End Try End Sub
Comment
Comment