Fibaro Motion Sensors FGMS-001 stuck at tripped/motion detected mode

Community Playground General Discussions
#1

I have several of Fibaro Motion sensors (FGMS-001) that sometimes gets stuck in tripped mode. I have to manually walk pass them again to have them reset back to normal. This can be a problem when going away without first notice that one or more sensors are stuck in tripped mode.

So, can anyone help me to create a scene or something that can reset the sensor back to “no motion dectection” without having to walk pass them?

#2

Bump
What he said ↑

#3

This can happen if your unit is restarting when the motion sensor resets to untripped. If you are getting a lot of restarts you need to file a ticket with vera support.

#4

Good to know, thanks.
How do I recognize a restart in the luaupnp log?

#5

I usually search for “Netstat” changes, and “Mongoose”. After looking at logs for a while you will get to notice problem areas as you scroll thru, usually areas with a lot of yellow and red. Don’t worry about “UserData::TempLogFileSystemFailure 5112 res:1” these are normal.

#6

Alright, thank you. It doesn’t seem to be related to restarts, in my case. So the initial question remains.

#7

You could check your logs for"WakeupRatings" for that device. Anything less than 5.00 indicates that it may have a problem. Too far from the controller or other devices flooding the network. The last time I had that problem Vera support found that I had a bad device that was flooding my Zwave network.

Good Luck

#8

If you can’t solve your problems, you can clear the tripped state of the sensor using some LUA code (that you can put in a scene).

The code:
luup.variable_set (urn:micasaverde-com:serviceId:SecuritySensor1, “Tripped”, 0, device)

will do it where you have to change the word device to the device ID number.

Thought I have never had to do that with a Fibaro so it points to you are having a battery problem on the sensor or a problem with the vera. Other sensors are more finicky so resetting them using the LUA code is useful.

#9

I cant believe that this bug still exists.

GRRR. Mios can you please resolve this.

#10

[quote=“onepointbrewing, post:9, topic:197563”]I cant believe that this bug still exists.

GRRR. Mios can you please resolve this.[/quote]

Hello, I’ve sent you an email regarding this matter and also opened a ticket into our ticketing system, please reply to the email with the requested information so we could see this through.

Thank you!

#11

[quote=“Ionut S, post:10, topic:197563”]Hello, I’ve sent you an email regarding this matter and also opened a ticket into our ticketing system, please reply to the email with the requested information so we could see this through.

Thank you![/quote]

I’m still having this issue too! Please share the solution or is it possible to add me to the ticket?

#12

Hello Joenoo, I’ve emailed you regarding this, please reply to the email with the requested information. Thank you!

#13

Melih, I am having this issue too…

#14

@Sender,
Melih is the Chairman of the Board and as he promised, he’s constantly taking the pulse of this community.
This is a matter that can be easily handled by our Customer Care team.

Fibaro FGMS-001 is officially integrated into Vera and if the Customer Care discovers any issues with it, it will be reported and sorted ASAP.

#15

[quote=“Sorin, post:14, topic:197563”]@Sender,
Melih is the Chairman of the Board and as he promised, he’s constantly taking the pulse of this community.
This is a matter that can be easily handled by our Customer Care team.

Fibaro FGMS-001 is officially integrated into Vera and if the Customer Care discovers any issues with it, it will be reported and sorted ASAP.[/quote]

Sorin,

thank you for replying.

“This is a matter that can be easily handled by our Customer Care team.”

so if it is easy? why isn’t it solved then for so many people?

#16

Sorin, any progress with this? Still having issues with all my motion sensors not being very rliable. Sometimes seeing the led blink but nothing happens in zwave and vera… and it is tripped but stucked in tripped mode.