non of this help. I clear the cache and tmp, re-discover the sensor but still not working
Which log I should post for debug?
Thanks,
Yehuda.
When things do not go as planned. In the documentation like I said earlier.
Try to put the suggested command, got the following:
log:set DEBUG org.openhab.binding.zwave
-bash: log:set: command not found
How this help me? still get the error
I think I will go on downgrade to 2.4 which was stable and work fine for me.
Could you point me the which 2.4 version I should downgrade?
downgrading to 2.4 will not help you and the developer has already said he cannot support the 2.4 z-wave binding due to all the many changes since then. Search and read the fine documentation to learn.
We are here to help you learn your system. We are not a HelpDesk handing our ready made solutions.
How to ask a good question / Help Us Help You - Tutorials & Examples - openHAB Community
Please try help me get the debug log.
I am not familiar with command line and has no clue why I got this error.
Welcome to __ _____ ____ _
____ ____ ___ ____ / / / / | / __ )(_)___ _____
/ __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __ / / __ `/ __ \
/ /_/ / /_/ / __/ / / / __ / ___ |/ /_/ / / /_/ / / / /
\____/ .___/\___/_/ /_/_/ /_/_/ |_/_____/_/\__,_/_/ /_/
/_/
openHAB 2.5.2-1 (Release Build)
Looking for a place to get started? Check out ‘sudo openhabian-config’ and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhab:8080
To interact with openHAB on the command line, execute: ‘openhab-cli --help’
[01:54:15] openhabian@openhab:~$ log:set debug org.openhab.binding.zwave
-bash: log:set: command not found
Hi Bruce,
Just want ot update that I downgrade back to 2.4 and now the new sensors are just binding well and can notify the sensor position and the battery level,
I would guess that the problem are related to 2.5 version and not to the new sensors that I added.
I will keep use 2.4 as long I not required to upgrade.
Thanks for your help
It can take a long time for updating the battery level. You can force it by pressing the button in the device. Maybe repeatedly, with some pause between (30 seconds or so).
I found that installing the sensor binding at ver 2.4 than upgrade to 2.5 work well for me
I guess the issue is with the 2.5 sensor binding
Thanks
Device is working on my side.
Make sure item sensor_door is defined as contact and not as switch.
I made that mistake by myself, if defined wrongly the status remains at Null …
best regards Harry
also work fine for me, but with binding form ver 2.4
Thanks
Yehuda
Why not update to 2.5? Staying behind will only get more painful when OH3 is released.
I’m having the same problem. I just received this sensor today so it has never worked correctly. Running OH 2.5. Ran debug (grep’d to NODE 10 which is this device.) i see that it says Manufacturer data not known and that the Node XML isn’t created, which i confirm the file isn’t there on the file system. I’ve tried to wake up the device repeatedly using the directions on the Thing description page found here. I’m sure that i’m pasting these logs wrong… sorry in advance. Any and all help is appreciated thank you!
[23:52:11] openhabian@openHABianPi:~$ less /var/log/openhab2/openhab.log | grep "NODE 10"
2020-05-05 22:06:31.400 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-05-05 23:18:39.774 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-05-05 23:36:52.209 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Handler disposed. Unregistering listener.
2020-05-05 23:36:52.243 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 10: Serialise aborted as static stages not complete
2020-05-05 23:36:52.690 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node Init transaction completed with response null
2020-05-05 23:36:52.692 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Skipping initialization thread, process stopped by controller
2020-05-05 23:38:09.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Channel zwave:device:19f9c0a5:node10:sensor_binary linked - polling started.
2020-05-05 23:38:09.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Channel zwave:device:19f9c0a5:node10:alarm_tamper linked - polling started.
2020-05-05 23:38:09.068 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Channel zwave:device:19f9c0a5:node10:sensor_door linked - polling started.
2020-05-05 23:38:09.068 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Channel zwave:device:19f9c0a5:node10:battery-level linked - polling started.
2020-05-05 23:38:17.502 [DEBUG] [age.SerialApiGetInitDataMessageClass] - NODE 10: Node found
2020-05-05 23:38:17.562 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 10: Init node thread start
2020-05-05 23:38:17.941 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 10: Serializing from file /var/lib/openhab2/zwave/network_d3dc1078__node_10.xml
2020-05-05 23:38:17.956 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 10: Error serializing from file: file does not exist.
2020-05-05 23:38:18.002 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from EMPTYNODE
2020-05-05 23:38:18.034 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 10: Init node thread finished
2020-05-05 23:38:18.037 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - advancing to IDENTIFY_NODE
2020-05-05 23:38:18.054 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: Initialisation starting
2020-05-05 23:38:18.379 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: ProtocolInfo
2020-05-05 23:38:18.381 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Listening = false
2020-05-05 23:38:18.383 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Routing = true
2020-05-05 23:38:18.386 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Beaming = true
2020-05-05 23:38:18.388 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Version = 4
2020-05-05 23:38:18.390 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: FLIRS = false
2020-05-05 23:38:18.392 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Security = false
2020-05-05 23:38:18.395 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Max Baud = 40000
2020-05-05 23:38:18.397 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Basic = BASIC_TYPE_ROUTING_SLAVE
2020-05-05 23:38:18.399 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Generic = GENERIC_TYPE_SENSOR_NOTIFICATION
2020-05-05 23:38:18.401 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Specific = SPECIFIC_TYPE_NOTIFICATION_SENSOR
2020-05-05 23:38:18.403 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Creating new instance of command class COMMAND_CLASS_NO_OPERATION
2020-05-05 23:38:18.406 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Command class COMMAND_CLASS_NO_OPERATION, endpoint 0 created
2020-05-05 23:38:18.408 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Version = 1, version set. Enabling extra functionality.
2020-05-05 23:38:18.411 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.
2020-05-05 23:38:18.413 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Creating new instance of command class COMMAND_CLASS_BASIC
2020-05-05 23:38:18.415 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Command class COMMAND_CLASS_BASIC, endpoint 0 created
2020-05-05 23:38:18.418 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.
2020-05-05 23:38:18.433 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@16c181f
2020-05-05 23:38:18.435 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node Init transaction completed with response COMPLETE
2020-05-05 23:38:18.436 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - advancing to REQUEST_NIF
2020-05-05 23:38:18.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@6e8496
2020-05-05 23:38:18.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Bump transaction 13 priority from Controller to Immediate
2020-05-05 23:38:18.447 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Adding to device queue
2020-05-05 23:38:18.448 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Added 13 to queue - size 3
2020-05-05 23:38:23.420 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Controller status changed to ONLINE.
2020-05-05 23:38:23.422 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Controller is ONLINE. Starting device initialisation.
2020-05-05 23:38:23.430 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties.
2020-05-05 23:38:23.433 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties. MAN=2147483647
2020-05-05 23:38:23.438 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Properties synchronised
2020-05-05 23:38:23.442 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising Thing Node...
2020-05-05 23:38:23.446 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:19f9c0a5:node10:sensor_binary for OnOffType
2020-05-05 23:38:23.448 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:19f9c0a5:node10:sensor_binary for OnOffType
2020-05-05 23:38:23.461 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:19f9c0a5:node10:alarm_tamper for OnOffType
2020-05-05 23:38:23.463 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:19f9c0a5:node10:alarm_tamper for OnOffType
2020-05-05 23:38:23.470 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:19f9c0a5:node10:sensor_door for OpenClosedType
2020-05-05 23:38:23.472 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:19f9c0a5:node10:sensor_door for OpenClosedType
2020-05-05 23:38:23.479 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:19f9c0a5:node10:battery-level for PercentType
2020-05-05 23:38:23.483 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:19f9c0a5:node10:battery-level for PercentType
2020-05-05 23:38:23.487 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Polling initialised at 86400 seconds - start in 33696000 milliseconds.
2020-05-05 23:38:23.489 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Device initialisation complete.try downgrade to 2.4, binding the sensor, upgrade to 2.5.
It works for me.
I am running OH 2.5.
I just downgrade to 2.4 in order to install the sensor binding, than upgrade back to 2.5
While it’s a little hard to be sure from this log, it looks like the device has not been discovered yet. There is no device information available, and until the binding receives this from the device it will not be able to do anything.
I guess this is a battery device, and you should wake it up so that the binding can discovery it fully and then configure it.
1 Like
It may also help to press the button 3x times quickly (LED will flash than instead of a one-time-blink). Actually 3x press is for in-/exclusion, but if the controller is not in in-/exclusion mode nothing will happen regarding that, but might help to initiate data transfer.
Also give it some time between experiments with trying to wake it up.
For the 1x click at least 30 seconds, for the 3x click at least a minute.
Removing the battery is also an option - give the sensor then 15 seconds (I believe) to start up.
I have 7 of these, and sometimes they included & transferred instantly, and something it was a longer process with many tries.
Also, when it was very rebellious to recognise, restarting OH can help - again, give OH then some time to fully startup - when the messaging frequency in the controller frame count reduces, try the usual one-click method to wake the sensor.
Once included and configured, the sensors are very reliable in operation, the hardware is very good, despite the low price.
Edit: Also read here: Neo Coolcam PIR motion sensor (PD03Z) - Wakeup issue
Edit: Just in case: The 1x click must not be too short. Something like a 0.1-second-click does nothing, but a 0.3-second-click works. If you don’t see the LED blink one time, it was too short pressed.
1 Like
Hi,
i have the same Problem with two new Neo Coolcam NAS-PD01Z.
Both Devices I can include in the OpenHAB Z-Wave network and Openhab will identify them correctly.
However if I Wakeup the Devices, I see nothing in the OpenHAB Z-Wave (Debug) log for a Wakeup…
Also I can’t change any settings like Assoziation Group etc., because the devices send no Wakeup Notivication to the controller? In Paper UI there is a point to Setup „Wakeup Configuration“ - „WakeupNode“. This is empty after the Inclution.
In the Userdata/zwave folder also no xml files created.
The Devices will blink red if they notivacate any motion, however send nothing to the Controller.
I already thry 3x click, without any luck.
Platform information:
- Hardware: Raspberry Pi 4 Model B Rev 1.2 - 4GB
- OS: Openhabian - Raspbian GNU/Linux 10 (buster)
- Java Runtime Environment: openjdk version “1.8.0_222”
- openHAB version: 2.5.4-1
- Z-Wave binding: 2.5.5.202005041107
Different device so different issue with similar symptoms.
Please start a new thread to avoid dealing with multiple problems in the same thread.
The volunteers here are easily confused.
2 Likes