Z-Wave Help

1

I have a couple Fibaro motion sensors (fibaro_fgms001_03_002). I was able to get one connected and seems to be working properly, but the other I cannot get to connect. I’ve manually done the config via a .things file, just like the working sensor but no matter what I do it says offline in paper UI and is reporting no data.

What’s odd is in the Z-Wave logs, it seems the sensor is online. Below is a snippet of NODE 7 in the logs (the node in question):

2024-05-28 15:48:14.016 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller status changed to ONLINE.
2024-05-28 15:48:14.019 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller is ONLINE. Starting device initialisation.
2024-05-28 15:48:14.019 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event listener added.
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising Thing Node...
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_binary for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_binary for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_binary for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_temperature for QuantityType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_temperature for QuantityType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_seismicintensity for DecimalType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_seismicintensity for DecimalType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_luminance for DecimalType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:sensor_luminance for DecimalType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:alarm_motion for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:alarm_motion for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:alarm_tamper for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:alarm_tamper for OnOffType
2024-05-28 15:48:14.020 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:battery-level for PercentType
2024-05-28 15:48:14.021 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:battery-level for PercentType
2024-05-28 15:48:14.021 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising cmd channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:alarm_general for OnOffType
2024-05-28 15:48:14.021 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising state channel zwave:fibaro_fgms001_03_002:controller:OfficeMotion:alarm_general for OnOffType
2024-05-28 15:48:14.021 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Polling initialised at 86400 seconds - start in 41817600 milliseconds.
2024-05-28 15:48:14.021 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Device initialisation complete.

I tried Inclusion and Exclusion many times. I’ve tried to wake the device up. I’ve waited overnight, but it never appears as online in Paper UI. Any tips on what else I can check?

Thanks!

2

One other thing to note is my sensor is actually firmware 03_004, but this wasn’t listed in the ZWave database, so I just used 03_002.

3

Inbox, add new item, z-wave binding, scan – then go thru the inclusion process. dummy me!

4

Sounds resolved. I was going to point you towards this post. Guidance for “unknown” Zwave Device - Tutorials & Examples / Solutions - openHAB Community There needs to be a local XML in the userdata/zwave folder or five lines to validate complete inclusion.
Five Lines of configured node

5

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.