I’m not super happy with the node20.xml and it could be related to your issue. Do you have the reinitialize device option on the node20 UI page? If yes try that and repost the new node20 XML. A more detailed option would be to reinitialize with the debug on.
Edit: Also is this node included securely?
New node20 config after reinit from UI with debug mode.
network_cc14718f__node_20.xml (15.5 KB)
After node reinits, I have updated the timer with value of 30 [sec], and it is working now.
Can you tell me what does it mean?
Also is this node included securely?
I use scan from UI, and add using button on device, as described here, in inclusion section.
IMO, yes. I have all devices.
Thanks
@majherek Everything looks fine now. Enjoy.
Hi there,
I just wanted to add a new device to my network, which didn’t work (others did), and than I found this thread.
I have a Shelly Wave 1PM Mini here, which gets added as Unknown Device, but Thing Properties show:
which seems weird, because Shelly should have a manufacturer ID of 0460 (as my other Shellys have). There is also an corresponding entry in OpenSmartHouse Z-Wave Device Database.
What’s wrong here? Is my device sending a wrong manufacturer ID or is OH doing a wrong mapping? Anything I can do?
I’m running openHAB 4.3.1 Release Build.
This is the same - 1120 is just decimal notation for hexadecimal 460.
It looks like this entry is not yet complete and therefore it’s not available in the binding.
Ah, didn’t think of that, so okay.
Is this really the case, if someone uploads some attachment, it’s gonna be complete and thus available? Seems a bit strange, but… shall I register and upload the manual which is available on the Shelly website?
Well, it will need to be “approved” first, but yes, that seems to be all that is required.
I can upload it if you provide me the link.
I appreciate you find this a bit strange, but not all manuals are easy to find - or can be found at all (sometimes we’ve had to scan and upload data). The idea was to try and provide a reasonably complete reference to users so they didn’t have to go searching the web to find information on obscure devices.
By forcing people to provide a core set of information on all devices BEFORE they are approved, we’ve found the information gets added. “I’ll do it later” was previously accepted, and information was often never available leading to problems further down the line…
Minor note. Your TYPE is 0x0002 and the device missing the manual is 0x0009. If that device looks good other than the manual missing, your type:ID pair will need to be added.
Short manual:
Complete manual (didn’t find a pdf):
What do you mean, can I test it and should I test somehow before?
Take a look at this post for an answers. 4a) is what I mean and 4biii) links to a test procedure. Guidance for “unknown” Zwave Device - Tutorials & Examples / Solutions - openHAB Community
From your first post?
143 = 0x008F
OK, it took a while, but in the meantime I registered for OpenSmartHouse, downloaded the XML, integrated it into my ZWave-Binding and added the device - which is working fine.
Hmm, only thing: in the OH UI - bindings: I see 2 Z-Wave Bindings, although I uninstalled it before installing the modified version. Within karaf console, I see only 1 such add-on?
Haven’t seen that. Probably okay if only one bundle in karaf. Not exactly sure of what you did, but..
IIRC the tutorial suggests using bundle:update not uninstalling the existing binding. The other option would be uninstall ZW from the UI, then add the modified binding in the addons folder. You might need feature:install openhab-transport-serial in karaf as that dependency is normally installed when adding ZW from the UI.
I’m running 4.3.5, a few point releases later and a few months later.
I am still seeing “unknown device” for this same Shelly device (Wave 1PM Mini)
Is this still to be expected? I would have thought it’d be in 4.3.5 release.
I’m not sure about the breakdown in the mechanics/communication between the ZW developer and OH central committee, but the ZW DB updates have not been backported to OH4.3.x. The device is only in OH5 snapshots (Java21 and 64-bit OS required).
Also you need to verify that your TYPE:ID is in the current ZW DB for the device.
I upgraded to OH5 snapshots and this now works for me.
Thank you for your help.
