Running 2.4 snapshot with the binding within in, 2.4.0
This has been driving me mental for weeks - the Timer which turns on/off the lights keeps resetting, despite no motion at all. I know this is not a rule issue because it works for many other users without a drama - it has worked for me on and off, which makes me think its a ZWave/Fibaro issue.
Ive recently upgraded to 2.4 OH2 in a hope to fix it. All other zwave devices (which are powered, work fine)
18:36:07.783 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
18:36:15.050 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_device_0a604f67_node12_meter_watts changed from 18 to 11.1
18:36:26.472 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Memory_Used_Percent changed from 8.8 to 8.9
18:36:26.478 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load5 changed from 0.2 to 0.1
18:36:26.483 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Network_DataSent changed from 35 to 36
18:36:34.176 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticVoltage changed from 236 to 233
18:36:34.179 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticCurrent changed from 0.948 to 0.946
18:36:34.181 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticWatts changed from 270 to 273
18:36:34.183 [INFO ] [smarthome.event.ItemStateChangedEvent] - AttickWhToday changed from 2.42 to 2.443
18:36:34.186 [INFO ] [smarthome.event.ItemStateChangedEvent] - AttickWhTotal changed from 208.227 to 208.25
18:36:34.187 [INFO ] [home.event.GroupItemStateChangedEvent] - gPowerUsage changed from 256.857 to 256.88 through AttickWhTotal
18:37:09.945 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticTemp changed from 16.0 to 15.9
18:37:09.947 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticHumidity changed from 46.4 to 47.0
18:37:26.488 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Memory_Used_Percent changed from 8.9 to 8.8
18:37:26.498 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load changed from 0.6 to 0.8
18:38:07.789 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
18:38:26.502 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Memory_Used_Percent changed from 8.8 to 8.9
18:38:26.507 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Network_DataRecevied changed from 6 to 7
18:38:26.512 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Network_DataSent changed from 36 to 38
18:39:26.529 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load changed from 0.8 to 0.4
18:39:26.531 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load15 changed from 0.3 to 0.2
18:40:07.794 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
I dont know if its the device or the binding. It has a brand new battery and is a Fibaro Motion Sensor FGMS0001. It’s about 1meter away from an Aeon Plug in Power Point socket, so there is NO issues with Zwave reception.
Any thoughts to work out why this is occuring? I’m about to throw the thing in the bin!
RULE:
rule "FibaroEye1 motion detection turns ON Living Room Lights when Lux is less than 20, with a 2 Minute Inactivity Timer"
when
Item FibaroEye1Alarm changed to ON
then
if (FibaroEye1Lux.state < 20) {
if (Eye1_Timer !== null) {
LivingRoomDim1.sendCommand("5")
logInfo("FibaroEye1Motion","Eye1 Timer rescheduled for " + Eye1_TimeOut + " minutes")
Eye1_Timer.reschedule(now.plusMinutes(Eye1_TimeOut))
} else {
logInfo("FibaroEye1Motion", "Eye1 Motion Detected! Turning ON Living Room Lights")
LivingRoomDim1.sendCommand("5")
logInfo("FibaroEye1Motion","Eye1 Timer created with " + Eye1_TimeOut + " minutes")
Eye1_Timer = createTimer(now.plusMinutes(Eye1_TimeOut))
[ |
if (FibaroEye1Alarm.state == ON) {
logInfo("FibaroEye1Motion","Eye1 Timer triggered, but rescheduled again for " + Eye1_TimeOut + " minutes")
Eye1_Timer.reschedule(now.plusMinutes(Eye1_TimeOut))
} else {
logInfo("FibaroEye1Motion", "Eye1 No Motion Detected! Turning OFF Living Room Lights")
LivingRoomSw1.sendCommand("OFF")
Eye1_Timer = null
}
]
}
}
end
Im running OH2.4 Snapshot and the 2.4.0 Snapshot Zwave Binding with Firmware 3.2 on the Motion sensor
You don’t explain your problem well enough.
What timer do you talk about ? Eye1_Timer ? And what do you mean by “it is getting reset” ? It isn’t.
Do you instead mean to say that your light turns off and you don’t know why?
If so that’s probably because FGMS will send Alarm OFF after a fixed number of seconds without motion.
It’ll do that no matter what you do in your rules.
And you likely have another rule to trigger on that.
You can change that timeout as a zwave parameter of the FGMS.
Or you might have a direct association from the Eye to you light actuator.
To find out, I suggest you enable debugging on zwave.
I have two of these devices (both with firmware version 3.2).
Your device looks like it’s triggering every two minutes. Is the Motion Detection Alarm Cancellation Delay set to 120 seconds?
I’ve seen this behavior with both of my devices, and I’m convinced it’s a device issue. My Alarm Cancellation Delay is set to 240 seconds, and without fail it would trigger motion every 4 minutes, even if there was absolutely no motion.
In both cases, pulling the battery for a few minutes, then replacing it with a new one solved it for me. I know you said you replaced the battery, but maybe that battery was not fresh?
Your other option would be to exclude it from your network, do a factory reset (manual should say how to do that), then include back into the network. Have you tried to do that?
When theres no motion, the system creates a 2 minute timer (Eye1_Timer). Its reset of theres motion, if it expires due to no motion it turns the lights off. But what happens, is the timer keeps getting reset (because theres motion, apparently)
Find out what’s causing your problem first before pointing somewhere.
If you haven’t even enabled zwave debugging, you are not even close to understanding what the problem is.
Many people use FGMS without problems. I have many of them in use, of different firmware, and never encountered false positives. And if there ever were problems, they have been there right from the beginning.
I believe you never properly completed installation of yours.
Yes you might need to factory reset them, reincludeand carefully adjust sensitivity and other parameters afterwards.
I think he’s saying that his FGMS001 is reporting motion constantly even when there’s no motion. At least that’s what I saw in the log snippet.
18:36:07.783 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
18:38:07.789 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
18:40:07.794 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
It was the sensor_binary that tripped under motion, but these logs of me walking into the room now indicate its alarm_motion, not even defined in my items file as seen here:
21:11:44.727 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_device_512_node14_alarm_motion changed from OFF to ON
21:12:28.625 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_device_512_node14_alarm_motion changed from ON to OFF
Yeah, but it was a misleading description (it is not getting reset but he’s actively rescheduling it because the rule gets called again and again).
Strictly speaking that log is just proving the rule is being called every 120 secs and we cannot be sure that’s because the FGMS sends alarm ON. I admit that’s the most likely reason but there’s other potential reasons (other rules).
Agreed. I made a bit of a leap in assuming the behavior he was seeing was similar to mine. What I saw in his event log had the same signature as mine (although as you point out the root cause certainly could be different). In my case, I could see the binding receiving the motion alarm (ON) every 240 seconds, immediately after the binding received the cancellation (OFF).
The zwave debug log will definitely show if it’s the device.
My wife almost crushed one of my FGMS001. Whenever she turned off the light, it would come right back on a couple minutes later. She thought I was messing with her, when it was just the FGMS001 gone rogue. LOL
So after updating the items file, the motion triggered and the lights turned on. I left the room over 2 minutes ago and then the log updates with:
21:50:39.885 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
The lights are still on and theres no motion for over 2 minutes now. All options are default on the Fibaro sensor
update: and a bit later…
21:50:12.067 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load1 changed from 0.1 to 0.0
21:50:12.074 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load changed from 1.0 to 0.5
21:50:12.076 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load15 changed from 0.2 to 0.1
21:50:39.885 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
21:51:12.086 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load changed from 0.5 to 0.9
21:52:12.098 [INFO ] [smarthome.event.ItemStateChangedEvent] - OpenHAB_Cpu_Load changed from 0.9 to 0.4
21:52:26.610 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticVoltage changed from 234 to 236
21:52:26.612 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticCurrent changed from 0.902 to 0.949
21:52:26.615 [INFO ] [smarthome.event.ItemStateChangedEvent] - AtticWatts changed from 272 to 280
21:52:26.616 [INFO ] [smarthome.event.ItemStateChangedEvent] - AttickWhToday changed from 3.308 to 3.332
21:52:26.618 [INFO ] [smarthome.event.ItemStateChangedEvent] - AttickWhTotal changed from 209.115 to 209.138
21:52:26.619 [INFO ] [home.event.GroupItemStateChangedEvent] - gPowerUsage changed from 258.325 to 258.348 through AttickWhTotal
21:52:33.292 [INFO ] [smarthome.event.ItemStateChangedEvent] - C3945_CPU5Min changed from 2 to 3
21:52:39.889 [INFO ] [arthome.model.script.FibaroEye1Motion] - Eye1 Timer triggered, but rescheduled again for 2 minutes
This section of the rule triggers it, checking the console the alarm is still ON. Even after much time, this is still ON in the console.
if (FibaroEye1Alarm.state == ON) {
logInfo("FibaroEye1Motion","Eye1 Timer triggered, but rescheduled again for " + Eye1_TimeOut + " minutes")
Eye1_Timer.reschedule(now.plusMinutes(Eye1_TimeOut))
openhab> smarthome:status FibaroEye1Alarm
ON
openhab>