Fibaro Motion Sensor: Association groups change between firmware versions

[AlCalzone]

the names of the groups in zwavejs2mqtt does differ from the manual

This seems like there are multiple revisions (or differences in the firmware versions of the same device). We likely need to split the device files by version range to model the different association groups.

Originally posted by @AlCalzone in https://github.com/zwave-js/zwavejs2mqtt/issues/2332#issuecomment-1081615502

---

For reference, the split seems to be FW <= 2.8 vs. FW >= 3.2: https://manuals.fibaro.com/de/motion-sensor/

[zwave-js-assistant[bot]]

Because of the large amount of Z-Wave devices, we cannot write all configuration files ourselves. Help from the community is required, so we can focus our time on improving Z-Wave JS itself. 🙏🏻

This issue has been labeled "Help wanted", meaning we kindly ask anyone who wants to help out for support. Here are a few resources to get you started - don't hesitate to ask if you are having problems:

• Contributing configuration files
• Importing from other sources
• Configuration file format
• Style guide

We may get around to doing it ourselves at some point, but community support will speed up this process immensely.

Thanks!

[Floppe]

IIRC they changed chip to Z-Wave+ v1 and those devices uses firmware 3.2+

And with that, a lot of other changes in parameters and more sensors.

[AlCalzone]

We already split the parameters, just the associations slipped through the cracks: https://devices.zwave-js.io/?jumpTo=0x010f:0x0800:0x1001:0.0