Fibaro Motion Sensor (FIBEFGMS-001-ZW5)

Hi Patrick ,

i just got a new fibaro motion sensor (FIBEFGMS-001-ZW5).

The Firmware of my sensor is v3.5.

This is the support page of the device: https://manuals.fibaro.com/motion-sensor/

 

I added it to my devices and want the sensor to turn lights on and off. Basically i want to turn on lights when someone enters a room and turn off the lights when the person leaves.

 

When motion or vibration is detected, the event history shows "Fibaro Motion Sensor: Burglar Alarm went off!". (like stated in an earlier post). I can use this event to turn on lights/ start a recipe.

But: After an "alarm cancellation delay" of 30 sec (Parameter 6) the sensor should cancel the alarm when there is no movement. This event is not shown in the event history.  Edit: the alarm cancellation is also displayed as "...: Burglar alarm went off!" in the event history, see next post.

Therefore i can not use the sensor to turn off the light after the person has left the room.

 

Furthermore i would like to know whether motion OR vibration is detected (and see this in the event history).

 

Please check that.

Reply
45replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Hi Patrick  Jeff ,

    I noticed somothing else thats buggy (and bugs me): The alarm cancellation timer (Parameter 6) is set to 30 seconds. This basically means if the sensor senses no motion for 30 seconds it send a notification about the alarm cancellation to the controller.

    It seems, that "all" reports of the motion sensor are summarized under "...: Burglar alarm went off!". This leads to the following buggy situation: If the light is turned on by the sensor, and i turn it off within those 30 seconds, the alarm cancellation report is interpreted as "...: Burglar alarm went off!" and the light goes back on.

    Reply Like
      • Jeff@NEEO
      • Head of Customer Experience
      • Jeff
      • 6 mths ago
      • Reported - view

      Markus M Hi Markus!

      As Ingrid said, we apologize for the delayed response. I can assure you that we are working on a fix. Once I have a better idea as to when the fix will be implemented into a firmware release I will update you separately.

      Thanks!

      Reply Like
  • Hi Patrick , Jeff , Ingrid ,

    it is now a week ago that Ii have described my problem with the motion sensor.

    Has anyone already taken care of that?

    Reply Like
    • Hi, Markus M. Thank you very much for reporting this and all detailed information so far. I'm sorry for the late response. I will forward it to the team and come back to you as soon as possible. 

      Reply Like
      • Markus M
      • Markus_M
      • 6 mths ago
      • Reported - view

      Ingrid 

      Do you think i can use the sensor soon?

      Reply Like
    • Markus M Thank you very much for coming back to us. The team has contacted the manufacturer, and they are now waiting for a response. I'm afraid that we still can't set a timeframe yet. Have a nice weekend! 🙂Stay tuned! 

      Reply Like 1
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Ingrid Was this part of the recent firmware 0.51.13 update?

      I still can not get the sensor to work.

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Hi Ingrid 

      I'm waiting patiently and hope for a speedy solution.

      Reply Like
  • Patrick Ingrid Jeff

    Today, I've tried to reset my Z-Wave controller to re-add all my Z-Wave devices and set up the Z-Wave devices again from the beginning.

    Unfortunatelly the motion sensor remains in the device list and is listed in the "living room". When i try to change the room of this device comes a message: "There was something fishy going on: "n is undefined"". When i try to use the device exclusion, the device remains in the list.

    Also the sensor is shown under "offline devices - plugged in?".

    How do i get rid of that?

    Reply Like
  • Markus M Patrick Ingrid Jeff

    Open the context sensitive menu of your device and select Delete. This will start the exclusion process. If you are unable to exclude the device, use Force Delete to remove the device. Your device should be removed this time.

    You should do another reset z-wave controller. I would not be surprised if your device reappears. In that case, you are having a Phoenix device.

    Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Hi Paul Spee ,

      thank you for the advice!

      The "Phoenix device" is exactly what I am experiencing.

      What does that mean? Is this a know problem? 

      Reply Like
    • Markus M Patrick Michael Kohler

      It means that you will not be able to get rid of the device and will have to do a factory reset the device. I consider this a problem.

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Paul Spee 

      And by "factory reset" you mean resetting the neeo bridge? I would like to avoid that. ^^

      Will the phoenix device affect the the functionality when i re-add the sensor?

      Reply Like
    • Markus M 

      I think Patrick and Michael Kohler are in a better position to answer that.

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Hi, Paul Spee Patrick  Michael Kohler

      can you please clarify the situation.

      I'm waiting for about a month now. Please make the sensor work soon™.

      (yes, there is some sarcasm in my request)

      Reply Like
    • Markus M No, if you correctly factory-reset the Motion Sensor (if not fully excluded yet) and add it again, I would not expect any negative effect from the "phoenix device".

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Michael Kohler

      Thank you.

      So the "phoenix device" is a bug neeo is suffering from?

      Will this be fixed with a future update?

      Are you making progress with integrating this sensor so that it can be fully utilized?

      Reply Like
    • Markus M

      yes, the "phoenix device" is a bug NEEO is suffering from. We are investigating this, but it turns out that this can't reliably be reproduced up to now.

      Markus M said:
      If the light is turned on by the sensor, and i turn it off within those 30 seconds, the alarm cancellation report is interpreted as "...: Burglar alarm went off!" and the light goes back on.

       This will be fixed in an upcoming release (0.52.x). Is there anything else blocking you from using this device?

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Michael Kohler 

      Thank you for the detailed answer.

      At the moment I can not start any actions based on the values of this sensor. But I think this is a general problem Neeo currently has - Starting actions based on sensor values.

      The sensor values currently (0.51.13) do not appear in the "NEEO Event history". In 0.50.6 they appeared as "...: Burglar alarm went off!".

      Reply Like
    • Markus M Michael Kohler

      The NEEO event history would get very long if all sensor events would be in the history and would require some kind of filtering option. I recommend to limit the history specifically to events related to the Brain and an event list for a specific device accessible from the context menu of the device.

      Reply Like
  • Michael Kohler

    Markus M said:
    At the moment I can not start any actions based on the values of this sensor. But I think this is a general problem Neeo currently has - Starting actions based on sensor values.

    Why is it not possible to start recipes based on the values of this sensor? Is this a general problem or do i really need to factory reset my brain?

    Reply Like
    • Markus M Can you please attach a screenshot of all the sensors that you can choose from this device when creating a recipe? Which one of those did you try? Are all of them not working or just one? If so, which one?

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Hi Michael Kohler

      these are the sensors I fan choose from.

      I can not start a recipe with any of them.

      As I understand the burglar alarm should be the actual motion alarm.

      Reply Like
      • Markus M
      • Markus_M
      • 5 mths ago
      • Reported - view

      Michael Kohler 

      Actually I have also tried to create recipes based on different sensor values.

      For example the power status or dimmer level of a Hue bulb. Those didn't work either. 

      Reply Like
      • Markus M
      • Markus_M
      • 12 days ago
      • Reported - view

      Michael Kohler  Patrick

      I found the following in the release notes of the latest update (0.53.8).

      • Fixed Z-Wave alarms not correctly triggering recipes

      Unfortunatelly i still can not get my z-wave motion sensor to work?!?

      Do i have a broken sensor or a broken brain?

      Please help me to solve this as long as you are there...

      Reply Like
      • Markus M
      • Markus_M
      • 12 days ago
      • Reported - view

      Jeff  Patrick

      BTW: recipes based on the status of philips hue lamps do work now.

      I do not get a z-wave based recipe to work!?

      Reply Like
      • Jeff@NEEO
      • Head of Customer Experience
      • Jeff
      • 11 days ago
      • Reported - view

      Markus M Hello. Have you tried to reboot your NEEO Brain? What if you exclude that device and then include it once more?

      Let me know if that helps. 

      Reply Like
      • Markus M
      • Markus_M
      • 11 days ago
      • Reported - view

      Jeff Hi, i have already tried both.

      Reply Like
      • Markus M
      • Markus_M
      • 7 days ago
      • Reported - view

      Jeff do you have any other ideas?

      Reply Like
      • Jeff@NEEO
      • Head of Customer Experience
      • Jeff
      • 7 days ago
      • Reported - view

      Markus M You can try to perform a full reset of the z-wave controller or the NEEO Brain to see if that helps. I will pull in  Michael Kohler to see if he has any other ideas. 

      Reply Like
      • Markus M
      • Markus_M
      • 6 days ago
      • Reported - view

      Jeff I just performed the reset of the z-wave controller (again). The sensor still remains/ apears in the device list as he used to before (see above).

      Didn't you fix the "pheonix device" in the latest update?

      After readding the sensor i still can not get it to work?!

      Reply Like
      • Markus M
      • Markus_M
      • 6 days ago
      • Reported - view

      Jeff I just went all in and did the factory reset on my brain.

      For testing i just added the sensor and the TV to see whether i can toggle the power with the sensor.

      Now my entire setup is gone and the sensor still does not work.

      Reply Like
      • Markus M
      • Markus_M
      • 6 days ago
      • Reported - view

      Jeff btw: is Michael Kohler still around? his last post is one month old.

      Reply Like
      • Jeff@NEEO
      • Head of Customer Experience
      • Jeff
      • 6 days ago
      • Reported - view

      Markus Has this device ever worked as intended? I am not familiar with Z-wave devices. How does the device work that you own without NEEO as the controller? 

      Reply Like
      • Markus M
      • Markus_M
      • 6 days ago
      • Reported - view

      Hi Jeff the device never worked. I have no other z-wave controller to test the device with.

      I had a chat to the seller today and he will send me a replacement sensor just to be sure its not the sensor...

      On the other hand i have a Fibaro Dimmer 2 and i was not able to create a working recipe with those sensor values either.

      Reply Like
      • Markus M
      • Markus_M
      • yesterday
      • Reported - view

      Hi Jeff , so i have tested the replacement Sensor. It does not work with this either.

      So the only thing left is, that something is wrong with the brain. Either the software or the hardware. Can you replace the brain or suggest a different solution?

      Reply Like
      • Markus M
      • Markus_M
      • 11 hrs ago
      • Reported - view

      Hi Jeff , lately you were asking:

      Has this device ever worked as intended?

      And i have answered:

      the device never worked.

      When I think back, the answer is actually a bit more complicated:

      When i first started this request, i was able to start a recipe with this sensor (kind of): When the motion alert was triggered, the event history was displaying "Burglar alarm went of" and the recipe was started. After the alert is over the sensor sends a alarm cancellation to the controller. Because this cancellation was also interpreted as "Burglar alarm went of", the same recipe was then started a second time.

      So due to this misinterpretation i was not able to use the sensor back then.

      Later the firmware 0.51.13 was published, which did not fix my problem. Instead the event history was not displaying the "Burglar alarm" from this Version on. And from that point on I could no longer use the sensor to start any recipe.

      Then Michael Kohler told me this would be fixed in 0.52.x.

      Now we have 0.53.8 and i still have the problem.

       

      PS: you can find all of that in this thread

      Reply Like
  • The problem is not directly related to the fibaro motion sensors.

    None of the motion sensors I installed can trigger any event. Clearly a generat NEEO problem.

    However, as NEEO abandoned Z-Wave, there will be no solution to this problem.

    Reply Like
      • Jeff@NEEO
      • Head of Customer Experience
      • Jeff
      • 4 mths ago
      • Reported - view

      Christian Hi Christian, sorry to see you feel we have abandoned Z-wave. I can assure you this is not the case. Michael Kohler is actually one of our Z-wave devs. He is pretty active on here, and he's trying hard to fix all the issues we're experiencing with Z-wave. I am VERY confident we will solve these issues as we progress :).

      Best,

      Reply Like
  • Patrick  

    Christian said:
    However, as NEEO abandoned Z-Wave, there will be no solution to this problem.

     I have not read such information anywhere. Is this an official statement of Neeo?

    Reply Like
  • The only problem is that we don't see any progress.

    Winter is coming and the radiators are not working.

    Motion Sensors or any sensors at all are not working.

    Can you see the power consumption of any switch?

    Can you move the roller shutter half way down?

     

    Nothing really works, you can add the devices but you are not able to really use them as long as it is not as simple as an on/ off switch. 

     And the only answer you get is that they are working on it (in many cases since ages) or they move the topic to the vote section.

    Reply Like
      • Jeff@NEEO
      • Head of Customer Experience
      • Jeff
      • 4 mths ago
      • Reported - view

      Christian  Hi Christian. I completely understand you’re frustration. As a small company we’re trying to allocate our resources into features that will have a bigger impact on the community. I am more than confident Michael Kohler and team will get this sorted out :). I know it’s taking a lot longer than expected, but believe me that we’re working hard to make things happen. I sincerely appreciate your patience in this matter and you have my word that these wrinkles will get ironed out sooner rather than later.

      -Jeff

      Reply Like
    • Jeff  is the actual work on Zwave still as you mentioned some months ago or has everything been shut down regarding z-wave development after the well off?

      Reply Like
  • Hi,

    Is it possible to display the temperature coming from this sensor?

    Reply Like
Like Follow