I know that this topic is quite often on this forum but I think I’ve tried many solutions and I have still the same problem - I cannot initialize my z-wave devices in proper way (I have got “unknown device”). Maybe you have had the same problem and resolved it.
OpenHAB, I have checked for 2.2.0, 2.3.0 (both stable versions) and 2.4.0 (build 1293)
I know that there is some problem with battery devices so I have plugged Multisensor into the computer via USB but it’s nothing changed. I have tried resetting devices and razberry board, including and excluding devices - of course I have still unknown device.
When I checked a log from the OpenHAB I noticed that I’ve got:
NODE 8: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0 (for ZW-100). I could attach the log file but I think there is too big.Then I have started thinking that the problem is firmware on razberry board, I have checked version of this firmware and it’s 5.04.
This is not a good idea. This will not make the device work better since ZWave devices are defined when they are included into the network. At that point, the controller is told if the device is a “listening” device or not - it won’t change by plugging it in to the USB port (unless you reset it, and re-include it, but please don’t do that unless you will ALWAYS run with USB).
You need to wake up the device. The manual should tell you how to wake a device up - normally there’s a button that you press - sometimes you may need to press it 3 times or hold it down for a few seconds… If you don’t do this, battery devices (ie devices that are not listening devices) will not communicate with the controller. Note that even if the device sends data to the controller (such as a door sensor) this is not the same as the device waking up and sending a wakeup notification.
Ok, I understand, From now I won’t do this. But in my case it didn’t matter because I tried a few times to include my devices normally, it means by waking up (without USB connection), and got “unknown device”.
Earlier, I was pretty sure that I woke up device in proper way. Now, I do not know but I see WAKE_UP_NOTIFICATION message in my debug log. Before, I did manual factory reset of device and z-wave board.
Easiest is to put it somewhere like dropbox, pastebin etc, and post the link here… Alternatively, you could open a ticket on my website (www.cd-jackson.com) - you need to register first if you go down that route.
Here the binding sends a message to the device. The controller says that it has sent it, but then says it has not received a response from the device.
Since the binding is receiving data from the device when you press the button to wake it up, the binding is able to receive the data from the device. However, given that there are no responses (that I have seen) to any messages we send, then I would conclude that the messages being sent by the controller are not working (ie the controller is not transmitting).
I could of course be wrong with this, but I’m not sure what else it could be at the moment.
So, do you have any idea? Maybe there is too early firmware version on z-wave board. It’s strange because I’ve received some messages from device, so transmittion module on z-wave board should be ok. But you mentioned that there are no responses to messages we send. I think that I have to check another controller, maybe z-stick plusgen 5.
If you refer to sensor information, alarms, and wakeup/NIF messages, then this doesn’t require that the transmission from the controller works.
I didn’t see ANY responses to any messages FROM the controller. I might have missed them, but even if there are some, the very vast majority are failing.
I doubt it’s firmware related.
Personally, I think the controller has a hardware problem, but of course I’m not 100% sure.
I am using similar set up of raspberry pi 3+ RaZberry2+OH+Aeotec Multisensor 6, getting similar issue for z-wave sensor:
Sensor
Unknown Device
This device has not been fully discovered by the binding. There are a few possible reasons for this -:
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like “Z-Wave node 1 (0082:6015:020D::2.0)”). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.
**Below are the inclusion logs:**
2020-01-16 07:19:47.206 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:dc5a4f58:node25' has been added.
==> /var/log/openhab2/openhab.log <==
2020-01-16 07:19:47.207 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:dc5a4f58:node25' to inbox.
==> /var/log/openhab2/events.log <==
2020-01-16 07:19:47.248 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_ack changed from 171 to 172
2020-01-16 07:19:47.251 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 324 to 325
2020-01-16 07:19:47.306 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_ack changed from 172 to 173
2020-01-16 07:19:50.041 [vent.ItemStateChangedEvent] - ImageURL changed from https://www.placecage.com/c/480/360 to https://www.placecage.com/640/480
2020-01-16 07:19:52.341 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_ack changed from 173 to 174
2020-01-16 07:19:52.354 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 325 to 326
2020-01-16 07:19:52.537 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:dc5a4f58:node25' has been removed.
2020-01-16 07:19:52.570 [hingStatusInfoChangedEvent] - 'zwave:device:dc5a4f58:node25' changed from UNINITIALIZED to INITIALIZING
2020-01-16 07:19:52.593 [hingStatusInfoChangedEvent] - 'zwave:device:dc5a4f58:node25' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-01-16 07:19:52.611 [hingStatusInfoChangedEvent] - 'zwave:device:dc5a4f58:node25' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-01-16 07:19:52.617 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:dc5a4f58:node25' has been updated.
2020-01-16 07:19:52.624 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:dc5a4f58:node25' has been updated.
2020-01-16 07:19:52.631 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:dc5a4f58:node25' has been updated.
**Below are the wake up notification logs:**
2020-01-16 07:24:00.047 [vent.ItemStateChangedEvent] - ImageURL changed from https://www.fillmurray.com/g/320/240 to https://www.placecage.com/480/360
2020-01-16 07:24:01.442 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 396 to 397
2020-01-16 07:24:01.471 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_ack changed from 208 to 209
2020-01-16 07:24:01.478 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 397 to 398
2020-01-16 07:24:01.783 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 398 to 399
2020-01-16 07:24:01.805 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 399 to 400
2020-01-16 07:24:01.834 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 400 to 401
2020-01-16 07:24:01.891 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_can changed from 4 to 5
2020-01-16 07:24:01.900 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:dc5a4f58:node25' has been updated.
2020-01-16 07:24:02.161 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_ack changed from 209 to 210
2020-01-16 07:24:02.177 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 401 to 402
2020-01-16 07:24:04.069 [vent.ItemStateChangedEvent] - CurrentDate changed from 2020-01-16T07:23:04.033+0000 to 2020-01-16T07:24:04.037+0000
2020-01-16 07:24:05.464 [vent.ItemStateChangedEvent] - Sun_Azimuth changed from 127.4331630415714 ° to 127.63270218438535 °
2020-01-16 07:24:05.467 [vent.ItemStateChangedEvent] - Sun_Elevation changed from 0.7203404503127578 ° to 0.8410537833817723 °
2020-01-16 07:24:05.639 [vent.ItemStateChangedEvent] - Moon_Azimuth changed from 235.81617844490046 ° to 236.04320863901867 °
2020-01-16 07:24:05.647 [vent.ItemStateChangedEvent] - Moon_Elevation changed from 23.63715481382528 ° to 23.511343875724336 °
2020-01-16 07:24:06.274 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 402 to 403
2020-01-16 07:24:06.314 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_ack changed from 210 to 211
2020-01-16 07:24:06.327 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 403 to 404
2020-01-16 07:24:10.046 [vent.ItemStateChangedEvent] - ImageURL changed from https://www.placecage.com/480/360 to https://www.placecage.com/g/640/480
2020-01-16 07:24:10.415 [vent.ItemStateChangedEvent] - zwave_serial_zstick_dc5a4f58_serial_sof changed from 404 to 405
In the properties I don’t see the manufacturer data (type and id). This probably means that the binding has not completed the interview where it gets this information from the device. Given that this is a battery device, it probably needs to be woken up to allow this to complete.
I’m not familiar with the device, but normally there will be a button you need to press.
Below I have included a Leviton Binary switch DZR15-1RZ
Z-Wave Node 027
Unknown Device
This device has not been fully discovered by the binding. There are a few possible reasons for this -:
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like “Z-Wave node 1 (0082:6015:020D::2.0)”). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.
2020-01-16 11:32:07.459 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:2c6e6f93:node27' to inbox.
==> /var/log/openhab2/events.log <==
2020-01-16 11:32:07.460 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:2c6e6f93:node27' has been added.
2020-01-16 11:32:07.620 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_ack changed from 125 to 126
2020-01-16 11:32:07.623 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 231 to 232
2020-01-16 11:32:07.682 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_ack changed from 126 to 127
2020-01-16 11:32:10.012 [vent.ItemStateChangedEvent] - ImageURL changed from https://www.placecage.com/c/320/240 to https://www.placecage.com/480/360
2020-01-16 11:32:12.711 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_ack changed from 127 to 128
2020-01-16 11:32:12.721 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 232 to 233
2020-01-16 11:32:12.785 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:2c6e6f93:node27' has been removed.
2020-01-16 11:32:12.818 [hingStatusInfoChangedEvent] - 'zwave:device:2c6e6f93:node27' changed from UNINITIALIZED to INITIALIZING
2020-01-16 11:32:12.858 [hingStatusInfoChangedEvent] - 'zwave:device:2c6e6f93:node27' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-01-16 11:32:12.863 [hingStatusInfoChangedEvent] - 'zwave:device:2c6e6f93:node27' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-01-16 11:32:12.872 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:2c6e6f93:node27' has been updated.
2020-01-16 11:32:12.875 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:2c6e6f93:node27' has been updated.
2020-01-16 11:32:16.872 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 233 to 234
2020-01-16 11:32:16.908 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_ack changed from 128 to 129
2020-01-16 11:32:16.917 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 234 to 235
2020-01-16 11:32:21.029 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 235 to 236
2020-01-16 11:32:21.070 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_ack changed from 129 to 130
2020-01-16 11:32:21.077 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 236 to 237
2020-01-16 11:32:25.160 [vent.ItemStateChangedEvent] - zwave_serial_zstick_2c6e6f93_serial_sof changed from 237 to 238
2020-01-16 11:32:25.181 [hingStatusInfoChangedEvent] - 'zwave:device:2c6e6f93:node27' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
It’s pretty much impossible to know what’s happening without a detailed log. All we can see is that the device doesn’t communicate, but really there’s limited information here.
Please also use code fences to format your logs.I’ll try to edit your post.
Below I have included a Leviton Binary switch DZ15S:
Z-Wave Node 028
Unknown Device
This device has not been fully discovered by the binding. There are a few possible reasons for this -:
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like “Z-Wave node 1 (0082:6015:020D::2.0)”). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.
Status: OFFLINE - COMMUNICATION_ERROR Node is not communicating with controller
hide properties
