[SOLVED] Fibaro Door/Window sensor 2 (FGDW-002) not sending door open

chris · October 28, 2018, 5:19pm

If you mean exclude/include, then this would probably be a good idea, and then ensure you grab the log so I can see what configuration is set. Doing this should also reset the device, in case it is getting into some strange state.

martindk · October 28, 2018, 5:46pm

Just for the record; I have 5 of these sensors and all are working perfectly on OpenHabian with the latest snapshot… open/close, battery and temp - all reports…

stefan.hoehn · October 28, 2018, 5:51pm

Here you go. I did an exclusion and an inclusion. I reconfigured the items. Same behavior like before.

Interestingly, there is an NPE when trying to handle the setup in the beginning.

2018-10-28 18:34:24.386 [ERROR] [st.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:16117d1edc0:node53/config'

java.lang.NullPointerException: null

	at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleConfigurationUpdate(ZWaveThingHandler.java:767) ~[?:?]

Then it was waiting for some messages to come in which finally made pressing the sensor button three times again and then it did receive the config information.

I have provided the log and the latest config.

network_fed4ea89__node_53.xml (17.7 KB)

Logfile: https://we.tl/t-ZXGV4YUKxE

Thanks for your support!
Stefan

stefan.hoehn · October 28, 2018, 5:52pm

Thanks Martin, it used to be the same here - it worked for months and suddenly it doesn’t anymore.

Stefan

stefan.hoehn · October 28, 2018, 7:28pm

Quite some time later I saw these two lines:

2018-10-28 19:47:31.251 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Polling...
2018-10-28 19:47:31.253 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Polling deferred until initialisation complete

So I pressed again the sensor button three times which resulted into

2018-10-28 19:59:24.975 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update request. Node information received. Transaction null
2018-10-28 19:59:24.977 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update - no transaction.
2018-10-28 19:59:25.231 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Is awake with 1 messages in the queue
2018-10-28 19:59:25.235 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Start sleep timer at 5000ms
2018-10-28 19:59:25.238 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2018-10-28 19:59:25.268 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 53: Node Status event - Node is AWAKE
2018-10-28 19:59:27.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:30.237 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:32.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:35.237 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:37.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:40.237 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:42.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:45.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:47.737 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:50.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:52.737 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
.....

So I pressed the button another three times and then the initialisation finally began and ran through

2018-10-28 19:59:55.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 19:59:57.737 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:00.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:02.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:05.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:07.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:10.239 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:12.739 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:15.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:17.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:20.239 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2018-10-28 20:00:22.087 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update request. Node information received. Transaction null
2018-10-28 20:00:22.090 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update - no transaction.
2018-10-28 20:00:22.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 75: Transaction not completed
2018-10-28 20:00:22.273 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update request. Node information received. Transaction TID 75: [WAIT_DATA] priority=Immediate, requiresResponse=true, callback: 0
2018-10-28 20:00:22.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Response processed after 161ms
2018-10-28 20:00:22.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 75: Transaction completed
2018-10-28 20:00:22.284 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: notifyTransactionResponse TID:75 DONE
2018-10-28 20:00:22.286 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-10-28 20:00:22.289 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@1e6bb19
2018-10-28 20:00:22.290 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Init transaction completed with response COMPLETE
2018-10-28 20:00:22.292 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: Restored from file - skipping static initialisation
2018-10-28 20:00:22.293 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to STATIC_END
2018-10-28 20:00:22.295 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2018-10-28 20:00:22.296 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Updating node properties.
2018-10-28 20:00:22.297 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Updating node properties. MAN=271
2018-10-28 20:00:22.299 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Updating node properties. MAN=271. SET. Was 271
2018-10-28 20:00:22.300 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Properties synchronised
2018-10-28 20:00:22.307 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Setting ONLINE
2018-10-28 20:00:22.310 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising Thing Node...
2018-10-28 20:00:22.313 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising cmd channel zwave:device:16117d1edc0:node53:alarm_motion for OnOffType
2018-10-28 20:00:22.314 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising state channel zwave:device:16117d1edc0:node53:alarm_motion for OnOffType
2018-10-28 20:00:22.316 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising cmd channel zwave:device:16117d1edc0:node53:sensor_temperature for QuantityType
2018-10-28 20:00:22.318 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising state channel zwave:device:16117d1edc0:node53:sensor_temperature for QuantityType
2018-10-28 20:00:22.320 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising cmd channel zwave:device:16117d1edc0:node53:sensor_luminance for DecimalType
2018-10-28 20:00:22.321 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising state channel zwave:device:16117d1edc0:node53:sensor_luminance for DecimalType
2018-10-28 20:00:22.323 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising cmd channel zwave:device:16117d1edc0:node53:battery-level for PercentType
2018-10-28 20:00:22.324 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising state channel zwave:device:16117d1edc0:node53:battery-level for PercentType
2018-10-28 20:00:22.326 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising cmd channel zwave:device:16117d1edc0:node53:alarm_tamper for OnOffType
2018-10-28 20:00:22.328 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising state channel zwave:device:16117d1edc0:node53:alarm_tamper for OnOffType
2018-10-28 20:00:22.330 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Initialising state channel zwave:device:16117d1edc0:node53:alarm_tamper for OnOffType
2018-10-28 20:00:22.332 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Polling intialised at 1800 seconds - start in 1537200 milliseconds.
2018-10-28 20:00:22.334 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 53: Serialise aborted as static stages not complete
2018-10-28 20:00:22.335 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to DYNAMIC_VALUES
2018-10-28 20:00:22.337 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2018-10-28 20:00:22.339 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_SENSOR_MULTILEVEL
2018-10-28 20:00:22.340 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Found 1 instances of COMMAND_CLASS_SENSOR_MULTILEVEL for endpoint 0
2018-10-28 20:00:22.348 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_MANUFACTURER_SPECIFIC
2018-10-28 20:00:22.349 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_CONFIGURATION
2018-10-28 20:00:22.350 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_MULTI_CMD
2018-10-28 20:00:22.352 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_ASSOCIATION
2018-10-28 20:00:22.353 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_CRC_16_ENCAP
2018-10-28 20:00:22.355 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_BASIC
2018-10-28 20:00:22.357 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION
2018-10-28 20:00:22.358 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_SENSOR_ALARM
2018-10-28 20:00:22.360 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Found 1 instances of COMMAND_CLASS_SENSOR_ALARM for endpoint 0
2018-10-28 20:00:22.364 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_VERSION
2018-10-28 20:00:22.366 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_SENSOR_BINARY
2018-10-28 20:00:22.367 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Found 1 instances of COMMAND_CLASS_SENSOR_BINARY for endpoint 0
2018-10-28 20:00:22.369 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 53: Creating new message for application command SENSOR_BINARY_GET
2018-10-28 20:00:22.371 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:22.372 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Command Class COMMAND_CLASS_SENSOR_BINARY is NOT required to be secured
2018-10-28 20:00:22.373 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: ZWaveCommandClassTransactionPayload - send to node
2018-10-28 20:00:22.375 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:22.376 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Command Class COMMAND_CLASS_SENSOR_BINARY is NOT required to be secured
2018-10-28 20:00:22.377 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1a5628a
2018-10-28 20:00:22.379 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Bump transaction 435 priority from Get to Immediate
2018-10-28 20:00:22.381 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Adding to device queue
2018-10-28 20:00:22.383 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Added to queue - size 9
2018-10-28 20:00:22.390 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 09 00 13 35 02 30 02 25 67 A2 
2018-10-28 20:00:22.418 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: sentData successfully placed on stack.
2018-10-28 20:00:22.421 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 435: Transaction not completed
2018-10-28 20:00:22.493 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: SendData Request. CallBack ID = 103, Status = Transmission complete and ACK received(0)
2018-10-28 20:00:22.498 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 435: Transaction not completed
2018-10-28 20:00:22.503 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Application Command Request (ALIVE:DYNAMIC_VALUES)
2018-10-28 20:00:22.505 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2018-10-28 20:00:22.507 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:22.509 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2018-10-28 20:00:22.512 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 53: Sensor Binary report, type=Unknown, value=255
2018-10-28 20:00:22.514 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2018-10-28 20:00:22.517 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 255
2018-10-28 20:00:22.520 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Updating channel state zwave:device:16117d1edc0:node53:alarm_motion to ON [OnOffType]
2018-10-28 20:00:22.525 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Commands processed 1.
2018-10-28 20:00:22.528 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1dcd51.
2018-10-28 20:00:22.530 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1dcd51.
2018-10-28 20:00:22.532 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: notifyTransactionResponse TID:435 DONE
2018-10-28 20:00:22.534 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-10-28 20:00:22.539 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@11675ff
2018-10-28 20:00:22.540 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Init transaction completed with response COMPLETE
2018-10-28 20:00:22.541 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_WAKE_UP
2018-10-28 20:00:22.542 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_BATTERY
2018-10-28 20:00:22.546 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Found 1 instances of COMMAND_CLASS_BATTERY for endpoint 0
2018-10-28 20:00:22.547 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:22.549 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Command Class COMMAND_CLASS_BATTERY is NOT required to be secured
2018-10-28 20:00:22.551 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: ZWaveCommandClassTransactionPayload - send to node
2018-10-28 20:00:22.553 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:22.554 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Command Class COMMAND_CLASS_BATTERY is NOT required to be secured
2018-10-28 20:00:22.556 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@900d9b
2018-10-28 20:00:22.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Bump transaction 436 priority from Get to Immediate
2018-10-28 20:00:22.560 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Adding to device queue
2018-10-28 20:00:22.562 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Added to queue - size 9
2018-10-28 20:00:22.570 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 09 00 13 35 02 80 02 25 68 1D 
2018-10-28 20:00:22.597 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: sentData successfully placed on stack.
2018-10-28 20:00:22.602 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 436: Transaction not completed
2018-10-28 20:00:22.626 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: SendData Request. CallBack ID = 104, Status = Transmission complete and ACK received(0)
2018-10-28 20:00:22.630 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 436: Transaction not completed
2018-10-28 20:00:22.636 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Application Command Request (ALIVE:DYNAMIC_VALUES)
2018-10-28 20:00:22.638 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2018-10-28 20:00:22.640 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:22.642 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Received COMMAND_CLASS_BATTERY V1 BATTERY_REPORT
2018-10-28 20:00:22.644 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 53: Battery report value = 100
2018-10-28 20:00:22.646 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-28 20:00:22.648 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BATTERY, value = 100
2018-10-28 20:00:22.650 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Updating channel state zwave:device:16117d1edc0:node53:battery-level to 100 [DecimalType]
2018-10-28 20:00:22.654 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Commands processed 1.
2018-10-28 20:00:22.656 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12187df.
2018-10-28 20:00:22.658 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12187df.
2018-10-28 20:00:22.660 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: notifyTransactionResponse TID:436 DONE
2018-10-28 20:00:22.662 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-10-28 20:00:22.668 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@7c56e3
2018-10-28 20:00:22.669 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Init transaction completed with response COMPLETE
2018-10-28 20:00:22.671 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: DYNAMIC_VALUES - checking COMMAND_CLASS_NO_OPERATION
2018-10-28 20:00:22.673 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: Initialisation complete!
2018-10-28 20:00:22.674 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to DYNAMIC_END
2018-10-28 20:00:22.675 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2018-10-28 20:00:22.677 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 53: Serializing to file /var/lib/openhab2/zwave/network_fed4ea89__node_53.xml
2018-10-28 20:00:22.739 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 0 Messages waiting, state DYNAMIC_END
2018-10-28 20:00:22.742 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to DONE
2018-10-28 20:00:22.744 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2018-10-28 20:00:22.747 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 53: Serializing to file /var/lib/openhab2/zwave/network_fed4ea89__node_53.xml
2018-10-28 20:00:25.239 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: WakeupTimerTask 0 Messages waiting, state DONE
2018-10-28 20:00:25.241 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: No more messages, go back to sleep
2018-10-28 20:00:25.242 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2018-10-28 20:00:25.244 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: SECURITY not supported
2018-10-28 20:00:25.245 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2018-10-28 20:00:25.247 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@188bff6
2018-10-28 20:00:25.249 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Bump transaction 437 priority from Immediate to Immediate
2018-10-28 20:00:25.250 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Adding to device queue
2018-10-28 20:00:25.252 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Added to queue - size 9
2018-10-28 20:00:25.259 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 09 00 13 35 02 84 08 25 69 12 
2018-10-28 20:00:25.285 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: sentData successfully placed on stack.
2018-10-28 20:00:25.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 437: Transaction not completed
2018-10-28 20:00:25.305 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: SendData Request. CallBack ID = 105, Status = Transmission complete and ACK received(0)
2018-10-28 20:00:25.306 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: resetResendCount initComplete=true isDead=false
2018-10-28 20:00:25.308 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: Response processed after 44ms
2018-10-28 20:00:25.310 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: TID 437: Transaction completed
2018-10-28 20:00:25.311 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 53: notifyTransactionResponse TID:437 DONE
2018-10-28 20:00:25.312 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 53: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-10-28 20:00:25.317 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Went to sleep COMPLETE

Then I tried to assign the Controller to 3: Controller updates.
I again get the exception from above.
I restarted OH
I still get the exception and therefore cannot apply the Controller to param 3:
I reinitialized the device
pressed again the button 6 times
finally the device is reinitialized
I am finally able to set the controller to param 3
And I am getting the 3 values but no door and tamper switch information

I provided another log file: https://we.tl/t-vf0IN6UUF5

stefan.hoehn · October 28, 2018, 7:44pm

Now it is getting really spooky: all of a sudden I DO get the values … I am totally confused. Why the heck does it work now?

For consistency here is the latest logfile: https://we.tl/t-rcZjl9AvQN

joedirt · December 5, 2018, 6:54am

im running m7 and have just got the fibaro door sensor 2 and have the same issues that you had, im getting the battery and temp readings and for about 15 mins after adding the device I get the updating open and close but nothing after.

ive tried doing a exclusion and an inclusion with no luck. any ideas?

stefan.hoehn · December 7, 2018, 9:02pm

I don’t - fortunately it is working ever since…

gaetan_claeys · December 15, 2018, 4:16pm

Hi, I’m also having issues with these sensors. I installed one a week ago and it was correctly reporting tamper, open/close status, temperature… but for an unknown reason, the sensor stopped reporting after two days while I didn’t change any configuration parameter. I then completely reinstalled it (removed binding, reset of the device, reinclusion close to the controller…) and it was working again but stopped again sending status updates after 1-2 days. Any idea how to debug this problem and what it could be? It’s very frustrating.
Thanks
Gaetan

joedirt · December 21, 2018, 10:22am

try going into habmin and setting all the association groups to controller and Configuration Parameter 3 to none sent as secure. thats just worked for me!!! ill post an update if it stops working

ps im now running 2.4 final

joedirt · December 21, 2018, 10:26am

@chris I don’t suppose there is a way to make the z-wave binding auto set the associations to controller?

chris · December 21, 2018, 10:28am

Yes, it does this during the device initialisation. If you select the reinitialise option, then it will do this again.

I’m also in the process of add a feature to prevent “required” associations being removed, so that errors from the UI, or lack of understanding by users doesn’t render the device “unusable”. I hope to add this in the coming days.

github.com/openhab/org.openhab.binding.zwave

Force associations in specific circumstances

openhab:master ← cdjackson:force_association

opened 05:44PM - 20 Dec 18 UTC

cdjackson

+61 -10

This will prevent associations being removed if the system needs them, and the c…ontroller is configured as ```master```. The PR searches to see if the database has an association configured, or if the association is the ZWave Plus ```Lifeline``` group. If so, it will set the association - thus preventing the user from removing it. This is to avoid the system becoming unusable due to either lack of knowledge by users, or, through UI problems causing associations to be removed. It also transpired that somewhere in the system (either in the UI, or in ESH) the arrays/lists are not being parsed correctly and the array is being presented as a string (eg ```[node_1, node_2]```). Code has now been added to handle this format! Signed-off-by: Chris Jackson <chris@cd-jackson.com>

skeltob · June 10, 2019, 4:24pm

I have tried adding the same sensor to my network (using Open Hab 2.4), however; I didn’f find the “development version”, you are talking about.

sihui · June 10, 2019, 4:49pm

Because this post is already very old.
The development version has been merged into master, means it is available in 2.4 stable and 2.5 snapshot binding version:
https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.addons.bundles$org.openhab.binding.zwave/

pedrolima · May 30, 2022, 11:18am

I’m sorry to be digging on such a old topic, but I’m affraid I’ve just installed 24 units “for nothing”…

Although all could be found when I discovered them in OH (v3.3.0.M5), only 3 actually sent information and even those are not sending any info anymore.

So I’m now sitting with more than 1k€ in sensors that “do not work”. Marvelous!

I’m seriously tempted to just send this back, since this was bought from Amazon, and just buy some basic 433Mhz sensors which I use in other house with a cheap alarm and it just works, with batteries lasting more than 2 years now.

stefan.hoehn · May 30, 2022, 11:51am

I wonder what is happening here because I have quite a few of them and all work well on the same version like yours. Are the devices blinking when you open the window? Did you check to OH Zwave logs on Debug when you open the window?

An alternative that I also use are the zigbee ones from aqara (which unfortunately are a bit bulky) and the wifi ones from Shelly.

pedrolima · May 30, 2022, 11:55am

This is something that I found very weird, because it is not.

Yes, and nothing shows in my log.

Those are definitely some good alternatives. The ZigBee I wanted to avoid because I already have a big network and I don’t want nothing to disrupt the wifi signal anymore.

But the ones from Shelly since they connect via wifi, those are some I already thought that could be a good fit.

I will definitely see if I can reset these ones and try to make them work, one-by-one. But it will definitely take time with so many sensors.

stefan.hoehn · May 30, 2022, 11:57am

Can you check the second setting 2: for any of the device? (taken from my sensor config)

pedrolima · May 30, 2022, 12:00pm

Yup, it seems that they might be all in 0.

Anyway, that’s only an indication of the state. I think it has no influence on the communication. Or does it?

stefan.hoehn · May 30, 2022, 12:03pm

Yes, this is true, it still should send the information even though it is not indicating it. However, thourgh this you can make sure your sensor is installed correctly. I once had sensors installed with the magnet on the wrong side or too much shifted to any direction, so it wouldn’t detect the closing state. So, therefore the indication is a real life saver for the right setup.