Fibaro Motion stopped working with OH 4.1.0

wiewior · March 26, 2024, 8:17pm

OH 4.1.0
Raspberry Pi 4

Hello,
My FIBARO Motion sensor stopped working. At least it does not sends updates to the controller.
I tried to reinitialise the system and the controller (reboot) unfortunately it did not help.
Information in the console is a little wired to me. Pressing wake-up button of the sensor seams not working.- no information on the console.
Z-Wave Network range is OK. (Cheking it by entering the sensor menu)
Is the sensor broken or there is sth wrong with the system updates I made?

2024-03-26 21:08:56.902 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:zwavestick:node5' changed from ONLINE to UNINITIALIZED
2024-03-26 21:08:56.927 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:zwavestick:node5' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2024-03-26 21:08:59.446 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Systeminfo_Cpu_Load1' changed from 0.0 to 0.2
2024-03-26 21:08:59.448 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Systeminfo_SystemUptime' changed from 15.3 to 16.3
2024-03-26 21:09:00.188 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SystemUptimeFormated' changed from 15min to 16min
2024-03-26 21:09:03.947 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Systeminfo_CPUTemperature' changed from 48.2 to 47.7
==> /var/log/openhab/openhab.log <==
2024-03-26 21:09:15.623 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:zwavestick:node5.
2024-03-26 21:09:15.625 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Controller status changed to ONLINE.
2024-03-26 21:09:15.626 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Controller is ONLINE. Starting device initialisation.
2024-03-26 21:09:15.631 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating node properties.
2024-03-26 21:09:15.632 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating node properties. MAN=271
2024-03-26 21:09:15.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating node properties. MAN=271. SET. Was 271
2024-03-26 21:09:15.635 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Properties synchronised
2024-03-26 21:09:15.637 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_64_2
2024-03-26 21:09:15.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_1_2
2024-03-26 21:09:15.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_2_1
2024-03-26 21:09:15.640 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_66_2
2024-03-26 21:09:15.641 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_3_1
2024-03-26 21:09:15.642 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_4_1
2024-03-26 21:09:15.643 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_6_2
2024-03-26 21:09:15.643 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_8_1
2024-03-26 21:09:15.644 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_9_2
2024-03-26 21:09:15.645 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_12_1
2024-03-26 21:09:15.646 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_14_2
2024-03-26 21:09:15.647 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_16_2
2024-03-26 21:09:15.648 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_80_1
2024-03-26 21:09:15.648 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_81_1
2024-03-26 21:09:15.649 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_18_1
2024-03-26 21:09:15.650 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_82_2
2024-03-26 21:09:15.651 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_83_2
2024-03-26 21:09:15.652 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_20_1
2024-03-26 21:09:15.653 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_22_2
2024-03-26 21:09:15.654 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_86_2
2024-03-26 21:09:15.654 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_87_2
2024-03-26 21:09:15.655 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_24_1
2024-03-26 21:09:15.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_25_1
2024-03-26 21:09:15.657 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_89_1
2024-03-26 21:09:15.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_28_1
2024-03-26 21:09:15.659 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_29_1
2024-03-26 21:09:15.660 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_40_2
2024-03-26 21:09:15.661 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_42_2
2024-03-26 21:09:15.662 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_60_2
2024-03-26 21:09:15.663 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration pending removed for config_62_2
2024-03-26 21:09:15.665 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Update ASSOCIATION group_ZWaveAssociationGroup [index=1, name=Lifeline, profile1=0, profile2=1, associations=[node_1]]: Adding Controller (node_1)
2024-03-26 21:09:15.666 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2024-03-26 21:09:15.667 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
2024-03-26 21:09:15.669 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:sensor_binary for OnOffType
2024-03-26 21:09:15.670 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:sensor_binary for OnOffType
2024-03-26 21:09:15.671 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:sensor_binary for OnOffType
2024-03-26 21:09:15.672 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:sensor_temperature for QuantityType
2024-03-26 21:09:15.673 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:sensor_temperature for QuantityType
2024-03-26 21:09:15.675 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:sensor_seismicintensity for DecimalType
2024-03-26 21:09:15.676 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:sensor_seismicintensity for DecimalType
2024-03-26 21:09:15.677 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:sensor_luminance for DecimalType
2024-03-26 21:09:15.678 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:sensor_luminance for DecimalType
2024-03-26 21:09:15.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:alarm_motion for OnOffType
2024-03-26 21:09:15.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:alarm_motion for OnOffType
2024-03-26 21:09:15.683 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:alarm_tamper for OnOffType
2024-03-26 21:09:15.684 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:alarm_tamper for OnOffType
2024-03-26 21:09:15.685 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:battery-level for PercentType
2024-03-26 21:09:15.686 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:battery-level for PercentType
2024-03-26 21:09:15.687 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising cmd channel zwave:device:zwavestick:node5:alarm_general for OnOffType
2024-03-26 21:09:15.688 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising state channel zwave:device:zwavestick:node5:alarm_general for OnOffType
2024-03-26 21:09:15.689 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Polling initialised at 86400 seconds - start in 7430400 milliseconds.
2024-03-26 21:09:15.690 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Device initialisation complete.

JustinG · March 26, 2024, 8:37pm

This happened to me regularly with Fibaro motion sensors and an aeotec gen 5 stick; it is the reason I stopped using those sensors. I had 6 of them and 5 of those six went through this multiple times (in one case as little as 3 weeks in between occurrences). I have not had any other motion sensors ever do this.

Unfortunately, because the device also cannot be excluded properly due to the lack of communication with the controller, the only solution I ever found was to factory reset the device and re-include it in the network (of course, this left zombie nodes which had to be cleaned up as well).

For what’s it’s worth, I have now moved to a zooz 800 series controller. I do not rely on the Fibaro motion sensors any more, but I did connect a couple up to the system to see if the error still occurred. I have not observed this behavior yet in this instance but it has only been a few months. Don’t know what that means, but thought I’d mention it for completeness.

wiewior · March 26, 2024, 8:47pm

Hmmm. Not good information. Thank you anyway. Your experience shows me that I do not do anything wrong.
Indeed i use Aeotec Gen5 z.wave controller. I have two of Fibaro sensors and one with this problems.
Is there any possibilities to not leave the ghost node?

rpwong · March 26, 2024, 9:22pm

I use a Fibaro with a Zooz S2 500-series stick. It was fine for about nine months, and then stopped reporting a few weeks ago. Same as @JustinG, I had to exclude and re-include it to get it functioning again.

I had only been using it for temperature and light until a month or two ago, and recently started to use the motion sensing in my bathroom. This leads me to wonder if the problem is having it send motion reports in a high-traffic area…sheesh.