One more question… just to be on the safe side.
I did not mount the sensor yet.
Does is matter, if the sensor is closed or open?
Means, do I need to place the rectangular magnet next to the strip while waiting for the wake up?
No, doesn’t matter.
Great! Thanks
Just an update…
After >20 hrs I still have Node initialising: DYNAMIC_VALUES and no Last Wakup Time in Attributes.
But I found some entries of a wakeup event - which looks encouraging:
2016-12-26 05:51:12.152 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 08 02 84 07 7A
2016-12-26 05:51:12.157 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-26 05:51:12.161 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 08 02 84 07 7A
2016-12-26 05:51:12.171 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 08 02 84 07 7A
2016-12-26 05:51:12.175 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 02 84 07
2016-12-26 05:51:12.185 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Application Command Request (ALIVE:DYNAMIC_VALUES)
2016-12-26 05:51:12.187 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class WAKE_UP
2016-12-26 05:51:12.191 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Received Wake Up Request
2016-12-26 05:51:12.196 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Received WAKE_UP_NOTIFICATION
2016-12-26 05:51:12.200 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Is awake with 1 messages in the wake-up queue.
2016-12-26 05:51:12.205 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2016-12-26 05:51:12.209 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Wakeup during initialisation.
2016-12-26 05:51:12.211 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - DYNAMIC_VALUES: queue length(5), free to send(false)
2016-12-26 05:51:12.212 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: loop - DYNAMIC_VALUES try 1: stageAdvanced(false)
2016-12-26 05:51:12.214 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ZWAVE_PLUS_INFO
2016-12-26 05:51:12.215 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ALARM
2016-12-26 05:51:12.217 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found ALARM
2016-12-26 05:51:12.218 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of ALARM
2016-12-26 05:51:12.220 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Creating new message for application command NOTIFICATION_GET V4
2016-12-26 05:51:12.222 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Creating new message for application command NOTIFICATION_GET V4
2016-12-26 05:51:12.225 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - queued packet. Queue length is 1
2016-12-26 05:51:12.227 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-12-26 05:51:12.227 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-12-26 05:51:12.228 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking NO_OPERATION
2016-12-26 05:51:12.230 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking POWERLEVEL
2016-12-26 05:51:12.231 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 08 03 71 04 07 25 4F F5
2016-12-26 05:51:12.231 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found POWERLEVEL
2016-12-26 05:51:12.233 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of POWERLEVEL
2016-12-26 05:51:12.235 [DEBUG] [andclass.ZWavePowerLevelCommandClass] - NODE 8: Creating new message for application command POWERLEVEL_GET
2016-12-26 05:51:12.235 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 8: Sending REQUEST Message = 01 0A 00 13 08 03 71 04 07 25 4F F5
2016-12-26 05:51:12.237 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ASSOCIATION
2016-12-26 05:51:12.239 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking BATTERY
2016-12-26 05:51:12.241 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found BATTERY
2016-12-26 05:51:12.243 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of BATTERY
2016-12-26 05:51:12.244 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 8: Creating new message for application command BATTERY_GET
2016-12-26 05:51:12.245 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking BASIC
2016-12-26 05:51:12.247 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking MANUFACTURER_SPECIFIC
2016-12-26 05:51:12.249 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ASSOCIATION_GROUP_INFO
2016-12-26 05:51:12.250 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking WAKE_UP
2016-12-26 05:51:12.251 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking SENSOR_BINARY
2016-12-26 05:51:12.252 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found SENSOR_BINARY
2016-12-26 05:51:12.253 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of SENSOR_BINARY
2016-12-26 05:51:12.254 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 8: Creating new message for application command SENSOR_BINARY_GET
2016-12-26 05:51:12.254 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2016-12-26 05:51:12.256 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking DEVICE_RESET_LOCALLY
2016-12-26 05:51:12.257 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking CONFIGURATION
2016-12-26 05:51:12.258 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking VERSION
2016-12-26 05:51:12.259 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - queued 5 frames
2016-12-26 05:51:12.261 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Wakeup during initialisation.
2016-12-26 05:51:12.262 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - DYNAMIC_VALUES: queue length(5), free to send(false)
2016-12-26 05:51:12.263 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: loop - DYNAMIC_VALUES try 1: stageAdvanced(false)
2016-12-26 05:51:12.264 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ZWAVE_PLUS_INFO
2016-12-26 05:51:12.265 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ALARM
2016-12-26 05:51:12.266 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found ALARM
2016-12-26 05:51:12.267 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of ALARM
2016-12-26 05:51:12.268 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Creating new message for application command NOTIFICATION_GET V4
2016-12-26 05:51:12.269 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Creating new message for application command NOTIFICATION_GET V4
2016-12-26 05:51:12.271 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - queued packet. Queue length is 1
2016-12-26 05:51:12.273 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-12-26 05:51:12.274 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking NO_OPERATION
2016-12-26 05:51:12.275 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 4F 00 00 02 A6
2016-12-26 05:51:12.276 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking POWERLEVEL
2016-12-26 05:51:12.277 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found POWERLEVEL
2016-12-26 05:51:12.278 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of POWERLEVEL
2016-12-26 05:51:12.279 [DEBUG] [andclass.ZWavePowerLevelCommandClass] - NODE 8: Creating new message for application command POWERLEVEL_GET
2016-12-26 05:51:12.281 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ASSOCIATION
2016-12-26 05:51:12.282 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking BATTERY
2016-12-26 05:51:12.283 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found BATTERY
2016-12-26 05:51:12.284 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of BATTERY
2016-12-26 05:51:12.285 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 8: Creating new message for application command BATTERY_GET
2016-12-26 05:51:12.287 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking BASIC
2016-12-26 05:51:12.288 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking MANUFACTURER_SPECIFIC
2016-12-26 05:51:12.289 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking ASSOCIATION_GROUP_INFO
2016-12-26 05:51:12.290 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking WAKE_UP
2016-12-26 05:51:12.292 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking SENSOR_BINARY
2016-12-26 05:51:12.293 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - found SENSOR_BINARY
2016-12-26 05:51:12.294 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Found 1 instances of SENSOR_BINARY
2016-12-26 05:51:12.296 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 8: Creating new message for application command SENSOR_BINARY_GET
2016-12-26 05:51:12.298 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking DEVICE_RESET_LOCALLY
2016-12-26 05:51:12.299 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking CONFIGURATION
2016-12-26 05:51:12.300 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - checking VERSION
2016-12-26 05:51:12.301 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: DYNAMIC_VALUES - queued 5 frames
2016-12-26 05:51:12.302 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveWakeUpEvent
2016-12-26 05:51:12.308 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 2. Queue={}
...
2016-12-26 05:51:12.318 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 8: Sent Data successfully placed on stack.
2016-12-26 05:51:12.319 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-26 05:51:12.321 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 4F 00 00 02 00 00 A8
2016-12-26 05:51:12.323 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 4F 00 00 02 00 00 A8
2016-12-26 05:51:12.325 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4F 00 00 02
2016-12-26 05:51:12.326 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 8: SendData Request. CallBack ID = 79, Status = Transmission complete and ACK received(0)
2016-12-26 05:51:12.329 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=8, callback=79, payload=08 03 71 04 07
2016-12-26 05:51:12.331 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4F 00 00 02
2016-12-26 05:51:12.332 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=79, expected=ApplicationCommandHandler, cancelled=false MISMATCH
2016-12-26 05:51:14.150 [ERROR] [ny.internal.simpleip.SimpleIpHandler] - Error connecting: java.net.NoRouteToHostException: No route to host (Host unreachable)
2016-12-26 05:51:14.152 [INFO ] [ny.internal.simpleip.SimpleIpHandler] - Will try to reconnect in 10 seconds
2016-12-26 05:51:17.241 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left!
2016-12-26 05:51:17.243 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Is sleeping
2016-12-26 05:51:17.244 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Putting message SendData in wakeup queue.
So it looks like there is still some initialization going on, which might take some more time.
And OH is waiting for this to complete:
The log shows every 30 min:
2016-12-26 06:52:22.904 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Polling...
2016-12-26 06:52:22.906 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Polling deferred until initialisation complete.
However, it’s still confuses me that there is no wake up time in the hambin settings yet even though a wake up did take place.
Possibly it’s just update if initialization is completed!?
So I need some more patience 
Battery Powered devices are quite complicated…
This looks all good.
Yes, but if you have a look at the log, it’s “another” DYNAMIC_VALUES. It’s proceeding. There is still a queue with data to be transferred. The wakeup is very short and the device went to sleep again before all data was transferred. So up to the next wakeup. 
Yes, that’s confusing for me too. But let’s wait until the initialization has completed.
Yes, I will definitely get back to you after this
@NCO I’m just as far as you are. The only difference is: I’v have a wake up time in the hamin settings.
Because of the problems I started from scratch and did a complet new installation with openHABian.
Now I have only included the sensative strip to my z-wave-controller (raZberry) to be shure nothing else matters.
My config at the moment:
The sitemap automatically created from HABmin looks like this
I have mounted the sensor at the door and when I open the door, the item “General alarm” turns to ON and don’t change anymore.
When I change it to OFF by myself and then close the door it changes to ON again.
I’m missing the open/close item too.
Now I set Association Groups to openHAB Controller, like you did.
By the way: A few days ago, one time Battery Level showed 100. I’m confident this will come back.
@anfaenger: you have to change the notification type to “binary sensor report”.
The ON/OFF state when you open the window will then be shown by the binary sensor, not by the general alarm. At least when all pending data was transferred and the device was fully initialized.
Done. Thank you.
and
@jaydee73 / @anfaenger
I am glad that this seems to be a common problem and not necessarily related to my capabilities
By the way:
Wouldn’t it be a good idea to set the wake up time to let’s say 10 min until the node is fully initialized?
I could then set it back to 84600 (default)!?
Yes you can! 
Ok, I also set it to 600.
Do you know, how long the strip stays awake?
You should be aware that most devices will limit the minimum wake up period to something considerably longer than this and if you try to set a value lower than the min it will be ignored.
The device will normally stay awake for 1 second after the binding has sent everything it needs to send.
I decided to be a little more patiente and obviously it’s paying off:
I got an update of the sensor the first time !!!
2016-12-26 13:33:56.723 [hingStatusInfoChangedEvent] - 'zwave:device:49ede2f3:node8' changed from ONLINE to ONLINE: Node initialising: DETAILS
2016-12-26 13:33:56.739 [hingStatusInfoChangedEvent] - 'zwave:device:49ede2f3:node8' changed from ONLINE: Node initialising: DETAILS to ONLINE: Node initialising: GET_CONFIGURATION
2016-12-26 13:33:56.885 [hingStatusInfoChangedEvent] - 'zwave:device:49ede2f3:node8' changed from ONLINE: Node initialising: GET_CONFIGURATION to ONLINE: Node initialising: DYNAMIC_VALUES
2016-12-26 13:33:57.023 [ItemStateChangedEvent ] - Z_Strega_Power changed from 1626.4 to 62.8
2016-12-26 13:33:57.071 [ItemStateChangedEvent ] - CPU_System changed from 9.8 to 23.2
2016-12-26 13:33:57.093 [ItemStateChangedEvent ] - Z_Bath_W_Batt changed from NULL to 100
2016-12-26 13:33:57.216 [ItemStateChangedEvent ] - Z_Bath_Window changed from OFF to ON
Previously I just had a constant alarm, Battery: - and Bath_Window always OFF
That’s a step forward.
However, Bath_Window now constantly is ON and Alarm as well (independent of the magnet’s position) and Alarm is OFF as soon as the magnet is close to the strip.
Anyway: I still see DYNAMIC_VALUES in Habmin and still no "Last Wakeup timestamp"
So it’s not done yet…
I couldn’t wait any longer. I manually did about 5 or more wake ups using the magnet.
Now everything is ok.
My config now:
To me, everything looks perfect. Now when I hold the magnet on the led-side of the strip, the item BINARY SENSOR turns to OFF and when I take the magnet away it turns to ON.
BATTERY LEVEL is 100.
But I don’t know the function of the Item GENERAL ALARM. What is this used for? (Maybe a stupid question, but I’m not used to z-wave.)
@jaydee73 @chris : Thank you very much for providing the right settings.
@NCO I hope this worked for you too.
Glad it’s working.
ZWave battery devices aren’t the easiest, but this device does seem to be especially problematic for some reason. I was wondering if someone wanted to write anything in the database that might be an aid to others? I’m not sure if there’s any good suggestions coming from this or not, or if it’s just ‘perseverance’ that’s required, but if anyone thinks of something useful, then it would be appreciated.
If you can provide some input, it would be great, and I’m sure appreciated by others. To edit the database, you need to register on the database site and email me to give you edit rights. You can then edit the information in the image above - you could add information into the “Device Overview” section, or “Inclusion Information” section (or any others if you think it’s appropriate).
Thanks.
Thanks, @anfaenger.
I am getting nervous about getting the same result, because I did not get any “wake up timestamp” yet.
Do you remember, if you had one even before the strip was fully initialized?
I also set the wake up cycle on a lower level (1 Hour).
Hope it helps to get it done tonight.