I’m trying to setup the aforementioned water sensor in OpenHAB 2.0 beta 4. The device is shown as “Unknown Device” in Paper UI. I have the log in discovering this device here http://pastebin.com/sYMCgrwg. It’s checking zwave:aeon_dsb45_00_000 but in the end, it could not resolve it as a thingType. What can I do to diagnose or solve this problem?
Have you woken the device up so that the binding can detect what it is? Currently it hasn’t downloaded the data required to decide the thing type (at least based on the log that’s the case).
I press the wake up button on the device when:
- after I add the “unknown device” any way.
or 2. before I search for new device.
Is there any time I need to wake up the device?
I also tried to press wake up button while I search for new devices in the inbox. But it still shows “Unknown Device”.
Maybe it’s not included properly. What does the log show - do you receive ANY data from the device at all? If not, it might be worth excluding it and re-including it again.
There’s a trick.
I don’t follow the instruction of the sensor to include the sensor into the network. In case anybody interest, the instruction is to unplug the z-wave controller stick, press the button to have it in inclusion mode, then press the button in the sensor.
What I did to make it recognized is to plug the stick, search for things in OpenHAB’s Paper UI. Then press the button on the sensor. At first it still doesn’t recognize the device, but after I add the device anyway, it recognized the device successfully.
Now, it still doesn’t show the correct values of the channels yet.
@chris Can you help again? Right now the device is recognized as “DSB45 Water Sensor”. But the problem is, there seems to be problem in getting information from the device. I tried to change the configuration such as wake up, reports that will be sent, etc. The configuration isn’t changed. The log shows
21:14:35.613 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update received
21:14:35.623 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update config_1_1 to 0
21:14:35.623 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Error getting configurationCommandClass
21:14:35.624 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update config_2_1 to 0
21:14:35.624 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Error getting configurationCommandClass
21:14:35.624 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update config_121_4_000000FF to 17
21:14:35.625 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Error getting configurationCommandClass
21:14:35.626 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update config_121_4_0000FF00 to 1
21:14:35.627 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Error getting configurationCommandClass
21:14:35.628 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update config_3_1 to 0
21:14:35.628 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Error getting configurationCommandClass
21:14:35.629 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration update group_1 to null
Do you have any suggestion about what to do to check and how to make it report whether there’s water? Thanks.
I suspect that the device hasn’t completed initialisation - is there an XML file being produced in the userdata/zwave folder for this node?
If you have a debug log of the full initialisation, then please provide it and I’ll take a look.
Hi @chris,
Here is the log when I add the device: http://pastebin.com/mj4D3266 (Please note that the node number is 14 for this device.)
By “XML file”, do you mean a file in userdata/zwave with the name similar to node[number].xml? There is no node14.xml. (or any previous node numbers when I added this device).
From the log, there is an error
14:39:38.768 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:APP_VERSION)
14:39:38.768 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class VERSION
14:39:38.768 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 14: Received COMMAND_CLASS_VERSION command V0
14:39:38.768 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 14: Process Version Report
14:39:38.768 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 14: Library Type = 3 (Slave Enhanced)
14:39:38.769 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 14: Protocol Version = 3.67
14:39:38.769 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 14: Application Version = 1.5
14:39:38.769 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 07 86 12 03 03 43 01 05 >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 07 86 12 03 03 43 01 05 (10)
14:39:43.729 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 14: Timeout while sending message. Requeueing - 2 attempts left!
14:39:43.729 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Is sleeping
14:39:43.730 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:39:44.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
14:39:44.895 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
When I search for new devices, it only shows me an Unknown Device. But it resolved to the right device name after I added it. Interestingly, there’s no error when I change the configuration such as reports that will be sent. It still doesn’t work, even if I wake up the device and change the configuration.
Below is the log when I changed the configuration. There’s no error.
14:52:02.958 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update received
14:52:02.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update config_1_1 to 0
14:52:02.998 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 14: Creating new message for application command CONFIGURATIONCMD_SET
14:52:02.998 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
14:52:02.999 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:52:02.999 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 14: Creating new message for application command CONFIGURATIONCMD_GET
14:52:02.999 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
14:52:02.999 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:52:03.007 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update config_2_1 to 0
14:52:03.007 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 14: Creating new message for application command CONFIGURATIONCMD_SET
14:52:03.008 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
14:52:03.008 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:52:03.008 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 14: Creating new message for application command CONFIGURATIONCMD_GET
14:52:03.008 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
14:52:03.009 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:52:03.009 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update config_121_4_000000FF to 0
14:52:03.013 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Set sub-parameter 121 from 0 / 000000FF
14:52:03.014 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Parameter 121 set value 00000000 mask 000000FF
14:52:03.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update config_121_4_0000FF00 to 1
14:52:03.016 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Set sub-parameter 121 from 1 / 0000FF00
14:52:03.016 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Parameter 121 set value 00000001 mask 0000FF00
14:52:03.016 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update config_3_1 to 0
14:52:03.017 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 14: Creating new message for application command CONFIGURATIONCMD_SET
14:52:03.017 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
14:52:03.017 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:52:03.018 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 14: Creating new message for application command CONFIGURATIONCMD_GET
14:52:03.018 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
14:52:03.018 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
14:52:03.018 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update group_1 to null
At the same time, I don’t get update from the device. I created an item for the channel Alarm and show it in the sitemap, the log shows this
15:00:35.986 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Command received zwave:device:73b4fcaf:node14:alarm_general → REFRESH
15:00:35.987 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Polling intialised at 1800 seconds - start in 50 milliseconds.
15:00:36.037 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Polling…
15:00:36.037 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Polling deferred until initialisation complete
It seem like the initialization isn’t complete. What else I need to to to fix this problem?
I’ll take a look at the exception tomorrow - this might explain at least part of the problem as it’s reading the firmware version and this might be preventing it discovering properly.
Hi am getting this error while added water sensor with my openhab2,
Please help me
device discovery could not resolve to thing type 7FFFFFFF:7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
This means that the device has not been discovered - probably because the device has not been woken up so that the controller can complete the interrogation. Try waking up the device and see if it completes.
i have done all upper things but nothing working
Now got error : I/O Exception Input/Output error in writeArray during sending. existing the thread
Please provide a debug log so we can see what is happening.
Hi Chris debug logs are
2017-10-30 14:04:05.813 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing ‘zwave:device:ee8a3289:node10’ takes m$
2017-10-30 14:04:28.184 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7$
2017-10-30 14:04:28.189 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:ee8a3289:node6’ to inbox.
2017-10-30 14:04:28.215 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7$
2017-10-30 14:04:28.238 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:ee8a3289:node9’ to inbox.
2017-10-30 14:04:28.257 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 0260:8003$
2017-10-30 14:04:50.045 [ERROR] [systeminfo.handler.SysteminfoHandler] - No information for channel battery#remainingCapacity with device inte$
2017-10-30 13:59:23.783 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. ex$
2017-10-30 13:59:25.787 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. ex$
2017-10-30 14:10:16.841 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7$
2017-10-30 14:10:16.845 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:ee8a3289:node6’ to inbox.
2017-10-30 14:10:16.869 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7$
2017-10-30 14:10:16.881 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:ee8a3289:node9’ to inbox.
2017-10-30 14:10:16.915 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 0260:8003$
As above, please provide a debug log so we can see what is causing the issue…