Issues with FGMS001v2 not reporting movement

[strips 4]

Hi,

 

I have 4 multisensors,

1 Aeotec gen5 ZW074

1 Fibaro MultiSensor ("type": "com.fibaro.FGMS001", older non Z-wave Plus) 

2 Fibaro MultiSensor ("type": "com.fibaro.FGMS001v2", z-wave plus)

 

The two first ones on the list works fine but the two Fibaro v2 sensors will not work properly. I have done multiple excludes / includes and reconfigures but still nothing.

 

They kind of freeze up and stay breached for several hours and suddenly I get a false alarm when no one is in the room. I have enabled push messages to monitor them. 

 

I do not believe the "Lux bug" is the problem here as I have default Parameter 40 (200 lux).

 

Had an idea it was because they are z-wave plus and I did not include them with security. But if I try enabling security at inclusion they will not get configured properly.

 

If it was only one sensor I would return it as faulty but I have the same problem with both newer sensors.

 

Any ideas?

 

Regards

Stian

[strips 4]

With the help from A.Socha we figured this was a corruption in my z-wave settings. Something bad probably happened when I added Domoticz or when I tried to add VeraEdge as secondary controller.

 

To test this we did a backup and reset HC2. Reincluded the MultiSensor and it worked fine.

 

Restoring any recent backup still does not work and I would give myself more hazzle restoring it too far back. So I will do a reset on HC2 and add everything again

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> Now I know I need a backup before doing anything stupid and what to test after adding secondary controller.

 

Thanks A.Socha!

[chaicka 195]

Tip: With Fibaro HC2/HCL, every change = backup before implement change, every significant change (e.g. firmware) = backup and reboot before implement update/upgrade.  :->