[SOLVED] FIBARO MOTION not sending values

wiewior · January 23, 2022, 12:00pm

Hello,
since a while one of my FIBARO Motion has stopped sending the values to the controller.
Looking for a solution I ensured have association group configured to the controller as written in this post

I had several tries to wake up the device manually but it does not send anything.
I am pretty sure the device sees the z-wave network and we see some communication.

I appreciate any feedback or support before I exclude the sensor from network.

My system configuration:
openhab 2.5.12
Raspberry Pi 3
Battery in F.MOTION is new.

2022-01-23 12:50:46.650 [event.ThingStatusInfoEvent] - 'zwave:device:8985008e:node14' updated: UNINITIALIZED
2022-01-23 12:50:46.654 [hingStatusInfoChangedEvent] - 'zwave:device:8985008e:node14' changed from ONLINE to UNINITIALIZED
2022-01-23 12:50:46.799 [event.ThingStatusInfoEvent] - 'zwave:device:8985008e:node14' updated: UNINITIALIZED (DISABLED)
2022-01-23 12:50:46.801 [hingStatusInfoChangedEvent] - 'zwave:device:8985008e:node14' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2022-01-23 12:50:58.602 [event.ThingStatusInfoEvent] - 'zwave:device:8985008e:node14' updated: INITIALIZING
2022-01-23 12:50:58.605 [hingStatusInfoChangedEvent] - 'zwave:device:8985008e:node14' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2022-01-23 12:50:58.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:8985008e:node14.
2022-01-23 12:50:58.653 [event.ThingStatusInfoEvent] - 'zwave:device:8985008e:node14' updated: OFFLINE (BRIDGE_OFFLINE): Controller is offline
2022-01-23 12:50:58.657 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Channel zwave:device:8985008e:node14:sensor_temperature linked - polling started.
2022-01-23 12:50:58.660 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Channel zwave:device:8985008e:node14:sensor_seismicintensity linked - polling started.
2022-01-23 12:50:58.660 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Channel zwave:device:8985008e:node14:sensor_luminance linked - polling started.
2022-01-23 12:50:58.662 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Channel zwave:device:8985008e:node14:battery-level linked - polling started.
2022-01-23 12:50:58.663 [hingStatusInfoChangedEvent] - 'zwave:device:8985008e:node14' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2022-01-23 12:50:58.660 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Channel zwave:device:8985008e:node14:alarm_motion linked - polling started.
2022-01-23 12:50:58.667 [event.ThingStatusInfoEvent] - 'zwave:device:8985008e:node14' updated: ONLINE
2022-01-23 12:50:58.670 [hingStatusInfoChangedEvent] - 'zwave:device:8985008e:node14' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2022-01-23 12:50:58.699 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:8985008e:node14' has been updated.
2022-01-23 12:50:58.706 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:sensor_binary for OnOffType
2022-01-23 12:50:58.709 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:sensor_binary for OnOffType
2022-01-23 12:50:58.713 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:sensor_binary for OnOffType
2022-01-23 12:50:58.718 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:sensor_temperature for QuantityType
2022-01-23 12:50:58.721 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:sensor_temperature for QuantityType
2022-01-23 12:50:58.724 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:sensor_seismicintensity for DecimalType
2022-01-23 12:50:58.727 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:sensor_seismicintensity for DecimalType
2022-01-23 12:50:58.732 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:sensor_luminance for DecimalType
2022-01-23 12:50:58.734 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:sensor_luminance for DecimalType
2022-01-23 12:50:58.738 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:alarm_motion for OnOffType
2022-01-23 12:50:58.741 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:alarm_motion for OnOffType
2022-01-23 12:50:58.745 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:alarm_tamper for OnOffType
2022-01-23 12:50:58.747 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:alarm_tamper for OnOffType
2022-01-23 12:50:58.751 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:battery-level for PercentType
2022-01-23 12:50:58.754 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:battery-level for PercentType
2022-01-23 12:50:58.758 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising cmd channel zwave:device:8985008e:node14:alarm_general for OnOffType
2022-01-23 12:50:58.760 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising state channel zwave:device:8985008e:node14:alarm_general for OnOffType

anon71759204 · January 23, 2022, 2:10pm

Please check the Z-Wave configuration parameters of your device. Many motion sensors have a configuration parameter to switch off the motion detection.

Move your device closer to the controller (interference?).

yab · January 23, 2022, 3:12pm

I had a similar problem when the battery was nearly empty. LED still worked, but z-wave did not function propperly any more. OH 2.5.12 that is on pi 3B+ in this case.

battery renewed: no change
deleted the device from the list and reincluded: no change
excluded the sensor an included it again (new node no → update the items): works fine again

Although I think this is not “normal behaviour” when it’s time to change a battery, I did not investigate further.

wiewior · January 23, 2022, 6:38pm

I moved sensor closer and checked the z-wave range:

No change.

wiewior · January 23, 2022, 6:40pm

battery renewed: no change

deleted the device from the list and reincluded: no change
exactly the same.

Last chance is to check your last point:

excluded the sensor an included it again (new node no → update the items): works fine again

Will let you know…
thanks for the hints

wiewior · January 23, 2022, 7:22pm

I did the following trying to remove the device.

Place the controller into Exclude Devices Mode

image2560×1262 199 KB
Pressed the B button of the sensor three times as described in manual. The sensor was close to the controller. Nothing happened. No removal confirmation.
I removed all channels and deleted the thing. This was successful
Placing the controller into adding mode of the device immediately discovered my sensor with previous node number. So i followed and configured the thing again. Unfortunately observation was the same. I did not received any updates.

I repeated steps 1, 2 and in addition I pressed remove the device from controller under the thing mode
Also without success.

Next step would be more hard, removing the node directly in my controller (USB-ZWave Serial controller Aeotec).

Before doing that maybe someone could provide the feedback on the procedure. Is it the right one? Why I did not receive any feedback from the controller about removing the device?

2022-01-23 20:08:55.526 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 14: Remove failed node not placed on stack due to error 0x18.==> /var/log/openhab2/events.log <==
2022-01-23 20:08:55.575 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:8985008e:node14' has been updated.
2022-01-23 20:08:55.578 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_5, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_4, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]==> /var/log/openhab2/openhab.log <==
2022-01-23 20:08:55.794 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 14: Remove failed node not placed on stack due to error 0x18.
2022-01-23 20:08:56.051 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 14: Remove failed node not placed on stack due to error 0x18.==> /var/log/openhab2/events.log <==
2022-01-23 20:09:24.669 [vent.ItemStateChangedEvent] - FIBAROWallPlugSwitchSensorPower changed from OFF to ON
2022-01-23 20:09:27.016 [me.event.ThingUpdatedEvent] - Thing 'zwave:serial_zstick:8985008e' has been updated.
2022-01-23 20:09:36.582 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:8985008e:node14' has been updated.
2022-01-23 20:09:36.585 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_5, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_4, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]==> /var/log/openhab2/openhab.log <==
2022-01-23 20:09:36.682 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 14: Remove failed node failed as node not found

yab · January 23, 2022, 8:09pm

Seems like the removal didn’t work.

I’d go and exclude the device, remove any leftovers from the controler, reset the device, renew the battery (even if it is brand new) one more and try to include the sensor again.

If inclusion does not work, hte device may be defective.

But maybe others have better ideas.

Good luck!

wiewior · January 23, 2022, 8:18pm

Thanks Marino for your fast reply.
Since I was not able to remove the device (node 14) from he controller i tried to add it again.
So, the sensor has been identified as a new device in the network (node:33). I added channels and suddenly both nodes (14 and 33) were updating the values.
Now I am wondering If I will be able to remove one and the second remains undiscovered…

wiewior · January 23, 2022, 8:27pm

after while…
Node 14 still in the INBOX

yab · January 23, 2022, 8:43pm

Maybe you can just ignore it for now, if node33 works. Update your items to 33 and see, if things/items are working correctly.

Try to remove the 14 once again. If that is unsuccessfull, you may search for how to remove “z-wave zombies” (later). Maybe hints in the attachment works for you.
Z-Wave Zombies.pdf (571.9 KB)

wiewior · January 23, 2022, 8:53pm

many thanks for the pdf. I was not aware about this tool.
Will try it out.

wiewior · January 23, 2022, 8:59pm

Can someone confirm the removal process, please?

Using HABian I go to Z-wave controller, click on Exclude Devices from extended menu

image2560×1262 215 KB
Press B-Button 3 times

image652×529 123 KB

Not I shall receive the confirmation from the HABian that my node has been removed.
Later I could remove the thing and channels. Is this right?

JensH · January 23, 2022, 9:18pm

If node 33 working, don’t touch the motion again.

To delete node 14 as a „ghost node“ I propose to use zwave pc controller on windows system.

Set node14 to failed, then mark and delete failed node 14.

I made the experience nodes not available any more (like your 14) slow down the zwave network over time.

yab · January 24, 2022, 12:17am

The two steps you describe are right.
I’m not shure about a confirmation from OH but i think there is none.

Removing the node in OH will not help, if exclusion did not work correctly. You may delete the node with the help of the “zombie” info above or try the procedure JendH descibes. This should also work on a raspi.

JensHs remark about zombies slowing the z-wave network is also right (from what i red from the community). So i always remove these non-existing devices.

wiewior · January 25, 2022, 7:45am

You’re right there was none all the time I tried to remove the thing

Thanks Jens. I will try a shot. Please tell me only one thing. To install zwave PC Controller I need to download the whole SDK environment from SiliconLabs? Is this meant PC Controller?
Do i understand that I need to unplug my USB zwave Stick from Raspberry and plug it into PC where the SDK is installed?`

If this is the case i will try it out.

JensH · January 25, 2022, 10:23am

If I had this, I stop service openHAB, unplug stick, plug-in on windows pc, Start zwave pc controller and use it to delete node. After that: plug to Linux again and start openHAB.

That’s the way I did successfully

yab · January 25, 2022, 10:32am

What exactly / which software do you “start”? I think, that is part of Jaceks question.

wiewior · January 25, 2022, 10:47am

Yes, Thank you Marino,
I s this the SW meant?

JensH · January 25, 2022, 10:58am

It’s the one from Silabs, named Zwave PC controller 5

With that one I had best effort, since mark as failed and delete failed never worked with openHAB at me.

wiewior · January 25, 2022, 11:51am

OK The problem solved.
I followed your suggestions and installed Simplicity Studio form Silicon Labs.
I had to find the way to install dedicated “plugin” for Z-wave controller but that I followed attached pdf from @yab
I removed the node 14 from the controller and it has not been identified later on in my openhab system.
I am wondering if next device will be assigned to ID=14…

Thank you for your support!