Hi, I bought the product “Aeotec Nano Shutter Z-wave Plus S2” with the specified part number ZW141-A. I tried to include into my z-wave network and within few days it only display as an unknown device. This device appears in the z wave database but as OH advice, there could be some set of references that may need to be update or include.
I’ve already create an account in cd-Jackson, but I’m not sure if I have to request a ticket to modify the database device, because I’m not sure if I’m wrong but It’s already register the same type and ID.
Hi there, I didn’t tried last week if this device can be recognize by OH. But yesterday I tried it by upgrading it to the latest snapshot. So actually is running 2.5.0~S1623-1 (Build #1623). And the procedures that I’ve take is to uninstall z wave binding and re installing it with the latest version. I’ve already try installing it through the paper UI and also manually with vs code but it’s still recognizing as an unknown device. Maybe I forget to take any additional step?
In the OH logviewer I’m still getting the same message since this device wasn’t update in the zwave database.
2019-06-26 10:28:31.957 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 0086:0103:008D::2.2
Actually all this time I had my bindings through addon.cfg. Previously just tried once to see if it works with Paper UI but it didn’t. So I installed again all my bindings through addon.cfg, the xstream file and the latest zwave snapshot version are in the addon folder. I will be trying and looking around if theres anything I missed or doing wrong. Thanks for your time and help!.
This is already a good start.
Make sure you have something like this in your log:
27-Jun-2019 17:44:25.107 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
27-Jun-2019 17:44:25.212 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
27-Jun-2019 17:44:25.483 [INFO ] [ab.binding.zwave.internal.protocol.ZWaveController] - Starting ZWave controller
27-Jun-2019 17:44:25.483 [INFO ] [ab.binding.zwave.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
If not, just restart the binding: bundle:restart 278