Motion Sensor problem (FGMS001)

[mattgo 0]

Hello,

I have a strange issue with a Fibaro Motion Sensor.

When I include it in Z-Wave network it works well for 2 days and then the main motion sensor turn into a temperature sensor and his icon goes away. So I try to exclude the module, re include it, then it's works well for some days and it turn itself into temperature sensor again...

Is there someone else getting this problem ?

Any idea ?

Thanks,

Matt

[fuuss 25]

Hi there

Could we have some more Information

Do you run HC2 or HCL , which Version.

Thx

[mattgo 0]

Yes, here's the details :

Home Center 2

Version 3.591 beta

FGMS001 Motion Sensor EU

Firmware v2.6

Thanks,

[Tibus31 0]

Hi there!

Very strange as I have also my Aeon Labs Multisensor on which the Motion sensor turned to T° and Icon disappears as well...

Unable to tell you the frequency as this aeon labs is not stable so I didn't pay attention to it for a while

Maybe it can help...

[jojo1967 1]

I have a strange problem with my fibaro sensor too: The integrated lux sensor doesn´t change the current value. Do I have to change the parameters or the settings for checking the current lux i.e. every 10 min?

[mattgo 0]

Hi jojo1967,

For this I have a clue, you need to change some parameters to have a realtime luminosity report.

Personally, I set the parameter 40 to 25 lux instead of 200.

(It determine the value change needed to report the new value to your controller)

And I also set the parameter 42 to 900 sec to have the real value each 15min.

[jojo1967 1]

Thanks - I´ll try it this evening!!

[ Added: 2014-06-08, 10:40 ]

Sorry for asking again, but I still got problems to load new parameters

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

What´s the correct order to change parameters?

1. Pressing button "add parameters"

2. Changing values

3. Pressing button "add parameters" again for more parameters

4. Pressing "Save-Symbol"

5. Pressing button "Reload Parameters" (or just reload the page?)

Could anyone share this basic knowledge with me pleeeease?

Please login or register to see this image.

/emoticons/default_icon_rolleyes.gif" alt=":roll:" />

[mattgo 0]

You don't need to add parameters manually (there is parameters template for Fibaro modules)

Go to your master module (the motion sensor), and edit the right parameters.

Then click save (icon on the right) and wake up your module by pressing the button inside.

[jojo1967 1]

Thanks mattgo - what a stupid mistake. I allways tried to add parameters in the lux module and to change parameters there. Now it works fine!!!!

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

[mheldt 0]

I have a strange problem with my fibaro sensor too: The integrated lux sensor doesn´t change the current value. Do I have to change the parameters or the settings for checking the current lux i.e. every 10 min?

[ Added: 2014-06-12, 18:51 ]

Hello,

I have a strange issue with a Fibaro Motion Sensor.

When I include it in Z-Wave network it works well for 2 days and then the main motion sensor turn into a temperature sensor and his icon goes away. So I try to exclude the module, re include it, then it's works well for some days and it turn itself into temperature sensor again...

Is there someone else getting this problem ?

Any idea ?

Thanks,

Matt

Hi guys

Same problem here, motion icon disappears, and is showing temp instead, 1 degree for motion, and 0 degree for no motion, keep restoring backup to get it back again.

HC2 3.590 and firmware 2.4 and 2.6 on sensors.

Any news on this?

[MalvinYNJ 4]

Seems like there is many problems with the new motion sensor?

[m.roszak 763]

MalvinYNJ, every multichannel device (2in1, 3in1, 4in1) has this issue, this is a problem with current version of Zwave engine.

We solved this by implementing new Zwave engine, for now only available in alpha stage (3.902 alpha software for HC2).

[j.nowacki 5]

If your motion sensor becomes temp. sensor try to change following parameters:

- parameter 60 and 62 to 0

- parameter 64 to 900

- wake up interval 43200

[mheldt 0]

Thx, the sensors have been working okey the last 2 days after I changed the parameters.

BTW, changing parameter 60, 62 and 64 didn't work, but changing the wakeup did.

Another "problem" is that the motion sensors work for a time, then suddenly reports "motion" and just "hangs" there, there is none in the room, no moving curtains, bugs, heaters. Im entering the room, and leave, then the sensor shows "no motion". Until it happens again.

This is not happaning to just one of the Fibaro sensors, but several.

Any clues??!!

Please login or register to see this image.

/emoticons/default_icon_exclaim.gif" alt=":!:" />

[mgmidget 2]

I have similar problems with 2 sensors, But only when they are amed and breached. The breached sensor never goes back to safe mode.

[mheldt 0]

Okey.

These are not armed, and nobody is at home to make them go off.

[Brick 13]

Hello,

I have a strange issue with a Fibaro Motion Sensor.

When I include it in Z-Wave network it works well for 2 days and then the main motion sensor turn into a temperature sensor and his icon goes away. So I try to exclude the module, re include it, then it's works well for some days and it turn itself into temperature sensor again...

Is there someone else getting this problem ?

Any idea ?

Thanks,

Matt

This kind of issue has been already commented in previous threads:

Please login or register to see this link.

As Fibaro guys declare, there's a problem with current z-wave engine and multichannel sensors. Something that worked for me (with AEOn 4 in 1) was to increase the time between sensor reports to the HC2. And I mean any report, concerning any of the built-in sensors. Any time below 30 seconds between reports could originate strange behaviours.

Of course, reducing the report frequency may kill some functionality (I have had to switch some scenes off because of this) but at least the device will still work until next z-wave engine version.

[cWal 0]

I have similar problems with 2 sensors, But only when they are amed and breached. The breached sensor never goes back to safe mode.

I also have (almost) the same problems with 2 Fibaro motion sensors : sometimes the sensor reports a breach (real) but doesn't go back to safe state, even when the breach is gone, as it should do 40s later. In this case, if another breach happens any time later then it reports it as "safe state"... The device being armed or not does not matter.

This seems random, a breach is always reported but the sensor can stay in a breached state, or not, until another breach occurs. So there can be :

- a breached then return to safe mode 40s later, and here is the normal default behaviour.

- a "stay breached" mode until another breach occurs. But in this case there is never a breached mode again about this breach : it is reported as safe and stay safe. Until the next breach and then the cycle can go on...

Strange and somehow annoying as there is no way to be sure meantime that the breach is over or not...

Is it a bug ? From the sensor, the software, the HC2 or the Z-wave ?

[jojo1967 1]

I got the same problem with my Fibaro Motion Sensor (changing to temperature sensor). Changing the parameters like J.Nowacki described didn´t work for me.

Any other ideas to reactivate my Fibaro Sensor?

[mheldt 0]

Hi guys

Halleluja...

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> Same problems as you guys.

Motion detectors disappears completely, or motion is turned into temp sensor, and so on.

Always had to restore from backup to get it back.

Also tried to set

- parameter 60 and 62 to 0

- parameter 64 to 900

- wake up interval 43200

But didn't work.

But now the system has been 99.99 % stable.

And that happened after I turned off "Remote Access". And removed fibaro app from pads and phones, so they don't try to access the HC2 through local network.

Wakes up in the morning, and all the sensors are there!!!!

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />)))) So for 3 days after making the change, the sensors are 99 % stable.

At least I can live with without remote until new firmware on my HC2.