This issue keeps bugging me. Now the lights were on again because of this sensor. According to the app (and developer site) the sensor was last triggered 4 hours ago, but the current movement status is still ‘true’, even though nobody was around for the past 2,5 hours.
This keeps the zone marked ‘active’ and therefore doesn’t turn of the lights.
I’m thinking of replacing the Fibaro with the Xiaomi sensor, but I hope it can be fixed otherwise.
If you have found a solution, I would be very interested in.
I could not detect the problem with the Fibaro HC2. In combination with Homey both the Fibaro MotionSensors and the Aeotec 4in1 sensor get stuck from time to time. Therefore I assume that it is due to Homey and not a special Fibaro MotionSensor problem.
Have you already tried NEO Coolcam?
I don’t have any other Zigbee devices in use, so Xiaomi is not really an option for me. I also don’t find the sensors visually appealing.
We all can contact Athom (support@athom.com) and see what they have to say about it.
The sensor has been working fine for years in the past, so Homey should be able to handle it well. Not sure what changed though.
I don’t have a NEO Coolcam, so I didn’t try it.
Don’t having any other Zigbee devices shouldn’t matter, right? Unless the distance between the sensor and Homey is too much. I do like the looks of the Fibaro more as well, but on the other hand the Xiaomi is very small.
I was wondering what you meant when you said that Xiapmi is not an option, because you don’t have any other Zigbee devices. I myself have tried it out and it worked just fine. Even with just one sensor.
It does build a mesh network, but that also works with just one sensor and Homey.
If I only use battery powered Zigbee devices (e.g. sensors), I’m afraid that I will get some problems with reception. My remaining SmartHome components are mostly Z-Wave devices (except Philips Hue and Ikea Tradfri, both with their own bridge), so I don’t necessarily want to use another standard without repeaters.
I got a simular issue with my motion sensors…Just moved from Vera Edge to Homey Pro, and these devices has worked perfectly on my Vera. inclusion to Homey works fine , and i got all values , like temp ,lux etc. But after a while it stops reporting temp and lux. sabotage and motion sensor seems to work and get reported into the app. i have 4 of these devices and all behaves like this.
Anybody seen behaviors like this?
I have 2 Fibaro Motion Sensor FGMS-001 since a few days.
But I am not satisfied, motion sensor and tamper alarm freeze or do not go off.
Also the movement is not sent reliably to Homey, i.e. the light does not always switch on, if I get up in the morning the motion detector does not switch at all, then the whole day quite reliable, does anyone know advice?
Yes, I do have the same problem after upgrading towards 5.0.0
The fibaro motion sensor triggers the motion detection or the tamper alarm. Randomly one or two do not return to their cancellation ( so the orange exclamation mark stays active and the icon keeps on blinking.
I tried several settings in parameters, removing sensors and connecting them again without result. Looks like a small bug.
Bob Smits
Before and after the installation yesterday of the 3.0.6 version I got a couple of tamper alerts (reported via Heimdall). This sensor never showed this behaviour before v5. I have removed the battery, triple pressed its button and set the sensitivity to 25 (was on 20). Have not received a tamper alert since (half a day). Possibly this has resolved my situation.