Hi, I have an issue with a new Z-Wave+ device, a keypad POPP (#700045). It is not recognized by OpenHab2.
My configuration is as follows:
Raspberry Pi with openhabian, openHAB 2.3.0-1 (Release Build).
Z-Stick Gen5 AEOTEC ZW090.
I tried multiple paths to have it work, but without success:
Uninstall and re-installing the Z-wave binding
Remove and re-add the thing
Ensure the keypad is in active configuration mode (as battery operated)
Use Paper UI or Habmin on my Android device for the addition/removal of the thing
… but unfortunately always without success
Each time I get the same unsuccessful message…
Z-Wave Node 8
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.
The original post says that it is not discovered. As you can see there was some discussion to try and work out what is wrong. As far as I can see there shouldn’t be any reason it shouldn’t work but I’ve not tested this myself. I know other keypads are working though.
Hi, unfortunately no. It was not clear to me if the keypad was not completely recognized by the Z-Stick Gen5. Or if openhab could not initiate correctly the device. I made all possible efforts to “wake up” the device, but could not get any better result than the one described in my initial post. Thus for the time being I have installed a simple wired keypad. This is not really comparable to the expectations I had with the POOP Keyboard…
@chris can you have a quick look at my debug log file?
It’s node 48 in my config. Seems that when I hit the ring button 2 times, it’s sending out the battery state. But nothing else. When I enter a code, the node says it’s correct (green light on it), but I can’t find it in the log.
So I’ve got the feeling that we’re missing something on the node (keypad).
I already removed the keypad (before node46), and added it once more. In the manual they mention network mode or standalone mode. And I was afraid I had it the first time in ‘standalone’. So now I’m sure about the network mode. And I didn’t enter a ‘master code’ yet. Easier to test.
ps Is it correct that I say that there are also a lot of timeouts? I’m about 3m away from the Gen5 stick.
Lol, battery level is already on 70%, and the devices didn’t worked once properly.
Seems that the keypad won’t initialize completely.
When I hit the ring button (twice seems to have more action then once), it should wake up.
Sometimes, the battery-level is communicatied. And every time, the thing is updated.
2019-02-06 12:40:43.982 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node52' has been updated.
2019-02-06 12:40:53.468 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node52' has been updated.
2019-02-06 12:40:57.809 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node52' has been updated.
2019-02-06 12:41:15.135 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node52' has been updated.
2019-02-06 12:41:28.603 [vent.ItemStateChangedEvent] - Keypad_Hekken_Batterij changed from 74 to 70
2019-02-06 12:41:28.683 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node52' has been updated.
Popp themselves won’t give any support it seems. Only answer I’m gettig is ‘secure Mode’. But no idea what/how/where I should put this. It’s a pitty how bad the service is from hardware producents. Only selling is in their portfolio. They’re lucky that we need hardware.
Answer Popp Support:
Please include device in secure Mode.
We do not test our devices with third party software.
@chris (or any others ), not sure if your back from holidays already. But if so, can you help me out with the analyse of the logs? Am I missing something? We’re talking about node52. I’ve already excluded/included the node for about 6 times. But every time the same endresult…
I’m back (just) and in recovery mode a little - and trying to work through some of the mails here
I guess from Popps response that this device might only work fully in secure mode, and looking at the log, I don’t think that the device is included securely.
So, you will need to exclude and reset the device, then include it using the binding (ie not using any button on the stick if you have one). In theory, this should include securely. It’s also possible that you will need to change the “Secure Inclusion Mode” setting in your controller to all devices - I say this because it looks like this device is saying it’s a notification sensor, and therefore the binding won’t include it securely by default.
If this doesn’t work, then please provide a debug log of the inclusion.