Config file for Fibaro FGMS001 zwave+ version

[manutremo]

I have a FGMS001 zwave+ motion sensor and realized that the xml config file in the current version is made for the former non+ version.

I had a look at the present fgms.xml file and felt brave enough to try and modify it with the modifications:

In particular, the non+ version had 3 association groups:
1 - Basic Report
2 - Tamper Alarm
3 - Lifeline

while in the zw+ version it has 5 association groups:
1st association group – “Lifeline"
2nd association group – “Motion”
3rd association group – “Tamper”
4th association group – “Motion BC”
5th association group – “Tamper BC”

In addition, the zw+ contains additional parameters:
18. Associations in Z-Wave network Security Mode
25. Tamper - alarm cancellation
28. Tamper - broadcast mode (was parameter 26 in former version)
29. Tamper - backward compatible broadcast mode

I modified the file and saved it as fgms001zw5.xml in the Config folder of my domoticz installation. I then modified the manufacturer_specific.xml accordingly. My device reports itself as ID=0x1001 and type=0x0801. I then excluded the device and included it again and... voilà, it works!

Specifically I managed to associate it to a light switch, which I wasn't able to before since one of the significant changes was on the association groups.

I'm attaching the file in case the developers want to add it to an upcoming version. Meanwhile, save the updated versions of both files since they might likely be killed by any update.

Enjoy!

[Mankan]

Hi,

ive tried to do like you, wich means that i tried to change the FGMS configfile but i dont get the sensor to work. ive also made changes in the manufacturing file. Look at the attached file.

Do you have any ideas? Wouldnt the sensor appear as an motion sensor?

Thanks!

[LouiS22]

I have a FGMS001 zwave+ motion sensor and realized that the xml config file in the current version is made for the former non+ version.

I had a look at the present fgms.xml file and felt brave enough to try and modify it with the modifications:

In particular, the non+ version had 3 association groups:
1 - Basic Report
2 - Tamper Alarm
3 - Lifeline

while in the zw+ version it has 5 association groups:
1st association group – “Lifeline"
2nd association group – “Motion”
3rd association group – “Tamper”
4th association group – “Motion BC”
5th association group – “Tamper BC”

In addition, the zw+ contains additional parameters:
18. Associations in Z-Wave network Security Mode
25. Tamper - alarm cancellation
28. Tamper - broadcast mode (was parameter 26 in former version)
29. Tamper - backward compatible broadcast mode

I modified the file and saved it as fgms001zw5.xml in the Config folder of my domoticz installation. I then modified the manufacturer_specific.xml accordingly. My device reports itself as ID=0x1001 and type=0x0801. I then excluded the device and included it again and... voilà, it works!

Specifically I managed to associate it to a light switch, which I wasn't able to before since one of the significant changes was on the association groups.

I'm attaching the file in case the developers want to add it to an upcoming version. Meanwhile, save the updated versions of both files since they might likely be killed by any update.

Enjoy!

You should provide this to openzwave github, as it's the main source of these xmls. There's a detailed howto on their github. Don't worry, you can't screw it

[Kerneldomoticz]

hey,

i wonder if it will fix my motion detection on 3 of my devices that goes crazy and which keep showing as ON for mouvement detection even if there is no motion... nly 3 devices have this problem and i have like 8 installed .. the problem appeared like 2 months ago ...

[Mankan]

Sorry, im new to this, do you know exactly where to find the "how to" solution at github?

[LouiS22]

Sorry, im new to this, do you know exactly where to find the "how to" solution at github?

https://github.com/OpenZWave/open-zwave ... ng-Devices

[Mankan]

perfect, will try this later! looks like its going to take a little time to get this... But ive will try

[manutremo]

Mankan,

Yes my device shows a "Motion" sensor after inclusion. Which is the exact device version, firmware version, ID and type of your device? Also, did you update the manufacturer_specific.xml file accordingly?

Louis22,

I wasn't aware that device config files could be contributed directly in the OZW github. Many thanks for the link to the instructions, I'll certainly send mine.

[Mankan]

Yes, i think i made the change properly in manufacturer_specific.xml

I uploaded your file, fgms001zw5.xml, then i made changes in manufacturer, see attached copy.

[dre68]

http://www.domoticz.com/forum/viewtopic ... 5&start=20
Here a link to an older post of me about the same issue

[manutremo]

Looks good, should work once you exclude and then include the device again.

Yes, i think i made the change properly in manufacturer_specific.xml

I uploaded your file, fgms001zw5.xml, then i made changes in manufacturer, see attached copy.

[Mankan]

Sounds good i havent got it to work yet but i will give it a try tonight or tomorrow......

[Mankan]

1/2
3pictures / 6 pictures

Hi, i still doesnt get it to work..... hmmm. I attached 3 copys, maybe some of you can see that something is really wrong, hopefully

[Mankan]

2/2

Hi, i still doesnt get it to work..... hmmm. I attached 3 copys, maybe some of you can see that something is really wrong, hopefully

[Mankan]

Sorry, the proble is, when i press the switch this attached copy appear

[StanHD]

That message is by design. You can't turn a PIR on/off with a switch. Is the PIR not triggering the switch as expected when motion is sensed? Your settings seem ok. Note that you have the Wake-up set to 2 hours (7200), so any changes could take up to this interval to update. (Unless you Wake-up manualy)

[Mankan]

Cool,then its only a script for notification i have to set.

Thanks for your help!

[kman]

¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
Details of my installation:
Domoticz version: 2.3266
OpenZwave version: 1.3492
Fibaro Motion: v3.2
controller: aeon zstick gen5 usb
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬

Thanks for the above details and the xml file. Currently I have included the controller to Group 1, Group 4 of Fibaro Motion (v3.2)

If some one could clarify my TWO points, please:

1. After including your above suggestions, in my case :
- motion is not detected till I add the controller to Group 4.
- Motion is not detected in Group 2.
As per manual of Fibaro Motion v3.2 - Group 4 (is for backward compatibility for Motion) and Group 5 (backward compatibility for Tamper)
But my controller is Aeon Zstick Gen5 USB controller - which is zwave plus version - so, it should have responded to motion on Group 2? Any comments?

2. Now coming to motion detection that is happening on Group 4, on every motion detection, I also see Alarm Level, Alarm Type, and Burglar. Any comments?
=====
2017-01-04 17:36:46.086 (aeon-GEN5-USB) Lighting 2 (Alarm Type)
2017-01-04 17:36:46.090 OpenZWave: Alarm Level: Secure
2017-01-04 17:33:06.113 (aeon-GEN5-USB) Lighting 2 (Alarm Level)
2017-01-04 17:33:06.118 (aeon-GEN5-USB) Lighting 2 (Burglar)
2017-01-04 17:33:06.170 (aeon-GEN5-USB) Lighting 2 (Sensor)
=====
Anyway to turn off Alarm Type, Alarm Level and Burglar on Motion Detection?

[Bikey]

¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬

1. After including your above suggestions, in my case :
- motion is not detected till I add the controller to Group 4.
- Motion is not detected in Group 2.
As per manual of Fibaro Motion v3.2 - Group 4 (is for backward compatibility for Motion) and Group 5 (backward compatibility for Tamper)
But my controller is Aeon Zstick Gen5 USB controller - which is zwave plus version - so, it should have responded to motion on Group 2? Any comments?

2. Now coming to motion detection that is happening on Group 4, on every motion detection, I also see Alarm Level, Alarm Type, and Burglar. Any comments?
=====
2017-01-04 17:36:46.086 (aeon-GEN5-USB) Lighting 2 (Alarm Type)
2017-01-04 17:36:46.090 OpenZWave: Alarm Level: Secure
2017-01-04 17:33:06.113 (aeon-GEN5-USB) Lighting 2 (Alarm Level)
2017-01-04 17:33:06.118 (aeon-GEN5-USB) Lighting 2 (Burglar)
2017-01-04 17:33:06.170 (aeon-GEN5-USB) Lighting 2 (Sensor)
=====
Anyway to turn off Alarm Type, Alarm Level and Burglar on Motion Detection?

I have exactly the same experience with:
Domoticz Version: 3.6304
OpenZwave Gen5 USB controller
Zwave Version: 1.4-2279-g7c8c27d-dirty:
Using the modified config file from this place.

Motion is only detected properly if I add the controller to Group 4. I also had to put the controller in Group 5 to have proper tamper detection, even though I'm using a Gen 5 USB stick.

I also have that Alarm Level, Type en Burglar are triggered simultaneously with the Motion Detection (although Alarm Level and Type always receive an "off" command). I can not really explain why this is, but this can be ignored of course.

However what can not be ignored is that for each motion detection/cancellation I now also get the "OpenZWave: Alarm Level: Secure" message in the log-file. This is probably related to the previous point, but I really don't want that to be in the log, as it clutters the log and takes up resources.

I have done much experimenting (even removed the controller from all association groups except group 1), but I keep getting the alarm messages in the log.

Has anybody an solution?

[ropske]

hi,

just noticed that some parameters in the new file fgms001zw5.xml according to the manual are not correct.
Some values are not allowed in new zwave+ device
will make an updated file according to the manual of the zwave+ device