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.
Here’s what I see in the openhab.log file:
2017-08-27 16:10:56.484 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-08-27 16:10:56.490 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:15da5b25003:node5' to inbox.
and here’s from the events.log file
2017-08-27 16:10:56.492 [InboxAddedEvent ] - Discovery Result with UID 'zwave:device:15da5b25003:node5' has been added.
2017-08-27 16:10:56.509 [BindingEvent ] - org.openhab.binding.zwave.event.BindingEvent@15dea2e
2017-08-27 16:11:16.585 [InboxRemovedEvent ] - Discovery Result with UID 'zwave:device:15da5b25003:node5' has been removed.
2017-08-27 16:11:16.596 [ThingAddedEvent ] - Thing 'zwave:device:15da5b25003:node5' has been added.
2017-08-27 16:11:16.647 [hingStatusInfoChangedEvent] - 'zwave:device:15da5b25003:node5' changed from UNINITIALIZED to INITIALIZING
2017-08-27 16:11:16.650 [hingStatusInfoChangedEvent] - 'zwave:device:15da5b25003:node5' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-08-27 16:11:16.654 [hingStatusInfoChangedEvent] - 'zwave:device:15da5b25003:node5' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-08-27 16:11:26.438 [BindingEvent ] - org.openhab.binding.zwave.event.BindingEvent@790112
Based on the above, the device is not really discovered - or hasn’t completed the interrogation phase at least. Either it’s not communicating with the controller, or maybe there was a problem with the inclusion process.
I would suggest to reset the device - exclude it, and then reinclude it to see if that helps for starters. Otherwise a debug log is really needed.
I don’t think so - in the other issue the device is discovered - here I don’t think it’s communicating at all and certainly not enough to get the manufacturer ID (just going on the information you’ve provided of course - maybe you have more information to conclude it’s the same?).
@chris Thanks. I’m going to figure out how to enable debug and will show the log shortly. I’ve tried to reset the device(three taps up and three taps down) and then restarted openhab service and tried to re-add the device, but still the same result.
The log doesn’t contain any communications with the device so there’s not much I can comment on about why it’s not discovered -:
I would suggest to get a longer log and looking at the log viewer yourself to see if there’s communication with node 5. If there is I’m happy to check it out…
(when pasting in a log, please format with the </> button as it’s much easier to read).
@chris Can you suggest some ways to elicit some communication with the device? I have the log open and the switch is able to control the fan, but I’m not seeing anything in the log.
Is it reasonably close to the controller? Let’s say 20 to 30 feet max? If so, I suspect that it needs to be excluded and then included again - I know you’ve done that, but I’d suggest to do it again, and get the full debug log so we can see what’s going on (if anything).
If there’s still nothing happening, then I’m not sure - if it excludes and reincludes again then it should be able to communicate…
@chris Yes, less than 15ft from the controller. I’ve tried to exclude and re-include and get the same results. Now, I am getting two nodes found. Both have the same ID:
I think you may be right. I think they are not being excluded properly. They immediately show up when I try to search for devices. I have an Aeotek Z Stick Gen 5. I’m going to try a full reset of the stick this evening and try again.
For that stick, it’s a long press of the button and wait for the Yellow light to flash. Then actuate the switch. Here are the instructions from the Aeon site.
Removing devices via its button (Example).
Remove the Z-Stick from your PC USB port (disconnect)
Press and hold the Z-Stick Gen5 button until its LED should blinks yellow rapidly, then release its button.
Now go to your Switch or Z-Wave device, and tap its button quickly (most devices use a single tap, but some Z-Wave devices may have special operations to unpair, please refer to your Z-Wave devices manual to unpair it from the Z-Stick).
If successful, you’ll notice that the Z-Stick Gen5s LED will become solid blue for 2 seconds to indicate a successful unpair, then it will return to blinking yellow rapidly to allow you to continue removing other devices.
You can continue to remove devices while it is blinking yellow rapidly (follow steps 3-4 with each device you want to remove then continue to step 6 when you are done)
Once you are done, tap the Z-Sticks button once and the LED should stop blinking.
Then I tried to add the device again via paperUI and still the old “unknown” devices keep showing up the in the list. So, I switched back to Zensys and manually included the fan control there. I was able to turn the fan on and off via Zensys.
Anyway, I reboot the pi, and got everything all cleared up.
Now, I started paperUI and tried to discover the switch by searching and pressing a button on the switch. Here’s my log @chris :
You need to update to the latest snapshot version of the binding. If you’re running snapshot runtime, then just go to PaperUI and uninstall the binding, wait 30 seconds and reinstall it again.
getting a little side-tracked:
I’ve attempted to upgrade from 2.1 stable to 2.2 snapshot. It looks like the I have the 2.2 zwave snapshot binding installed after the upgrade. No errors during the upgrade. I have some UI errors and also can’t seem to get to device discovery in paperUI:
HABmin:
I tried in HABmin and the items list is empty. I receive an error when I click/switch from the things menu to the bindings menu. Switching to any other menu, I don’t get the error message. Also, the binding menu never populates with bindings :