I did try waking it up but it does not seem to make a difference . My battery sensor is exactly this item here:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/400
How do I get a debug logfile?
I cannot seem to upload the openhab.log and events.log files to this forum. Must I convert them to something else?
You need to find somewhere to load them to - eg Dropbox, or something similar.
https://drive.google.com/file/d/1StZniafbn3NRcqgZ1Qi4_JDxODWvpXM9/view?usp=sharing
https://drive.google.com/file/d/1e7PEyfRNTEOKTN0MnJKfrp1AVgf1wF-y/view?usp=sharing
thanks Chris
Unfortunately that is not a debug log.
Did you see the link to the docs from my post above?
Go to karaf console and type
log:set DEBUG org.openhab.binding.zwave
You should also log zwave to a separate file to make it better readable:
https://docs.openhab.org/administration/logging.html#logging-into-separate-file
You have a lot of errors in your logs:
Your Zigbee is not connected to the correct port. Are you using two USB devices at the same time? That can cause trouble when rebooting because the ports can change, you may need to use symlinks:
Also your network bindings needs arping installed:
https://docs.openhab.org/addons/bindings/network/readme.html#arping
I would highly recommend to first troubleshoot all your errors and then advance to zwave device inclusion.
Thanks!
How do I get the log file out after the
log:set DEBUG org.openhab.binding.zwave
Same procedure you did already:
post your openhab.log.
But after a debug command it will be several megabytes 
But the file does not seem to have changed. Its definately less than 1 MB
Did you create a separate zwave log as I recommended above?
Then you need to use that file …
Here you can see an example for a zwave debug log file:
Note the debug in
07-Nov-2017 16:35:02.207 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 10: TID 13471: Timeout at state ABORTED. 3 retries remaining.
Yes I did.
Here it is:
https://drive.google.com/file/d/1D4kOJoFvJILaQwoaJYw2wFlQnIKI-VEw/view?usp=sharing
oops … just saw your msg. Wrong log file then
No, that is a valid debug log. All good.
Feeding that through the log viewer it does not look too bad for the controller and node 3:
But nothing at all for node 2.
So you need to catch a log when you either include the node in question (or reinitialize it, or wake it up)
I am not sure which is node 2 or node 3. I only have 2 z wave devices now connected, the Aeotec Z stick and the Neo door sensor.
In this log, did you actually wake up the device so that it can initialise? If so, there is no sign of this. Currently the binding is waiting for the device to send a wakeup notification, and there is no communication with the device yet.
Should i “wake” the battery sensor, or the Aeotec Z wave stick? Or both?
Is the Z wave stick supose to be switching between blue, orange , red all the time while its in the usb port of the ubuntu VM?
From what I read just pressing the button on the sensor wakes it, when I see a little red light
You can only wake battery devices. Other devices do not sleep.
Yes - I think that’s normal.
ok. tried waking up the sensor. This is my latest log
https://drive.google.com/file/d/1z-eOAxK_5N56QhVmuUE7sK4-ImBkgA46/view?usp=sharing
Only your controller and node 3 are showing data, still nothing from your not working node.
If that is the case, everything is fine 
I have only one Neo device (flood sensor), despite the manual saying click the button once to wake it up, I need to triple click the button to wake it up …