Shelly Wave 1 Mini - z-wave device not recognized

Add-ons Bindings
,
1

Hi

I am running OH 4.2.3 and have tried to include Shelly Wave 1 Mini devices to my setup with little success. I got them added, but they are not recognized in openhab.

After some research I realize that I can’t find this device in the opensmarthouse database.

Things type shows me “Uknown Device”.

I would love to try to add this device into the database like this one: OpenSmartHouse Z-Wave Device Database

I found also this:
https://manual.zwave.eu/backend/make.php?lang=en&sku=ALREZWE_W_1_MIN&cert=ZC14-24020400

But when I try to register on Open Smart House using this link: https://www.opensmarthouse.org/user/register.php I get an error:

image

Any advise, how can I try to create zwave XML device file locally?

2
3

Out of curiosity, do you have a XML for the mini in your userdata/zwave folder? Others have had a problem. 4.2M4 Shelly Wave 1pm mini and i4 not recognized - Add-ons / Bindings - openHAB Community. and Problems with Shelly Wave 1 Mini - Add-ons / Bindings - openHAB Community

4

No, I don’t have the XML, but want to create XML base on alrezwew1pm_0_0.xml (from org.openhab.binding.zwave-4.2.3.jar) and specification from: https://manual.zwave.eu/backend/make.php?lang=en&sku=ALREZWE_W_1_MIN&cert=ZC14-24020400

5

The problem there is that the binding XMLs are not the same as the XML’s that need to be loaded into the DB. However, if you have an OH generated node XML with a recognized Shelly 1PM that could be modified and uploaded.

6

Ok. I order wave 1PM mini. Let’s wait.

I see your’s conversation here: Problems with Shelly Wave 1 Mini - #17 by pacive

Can I try to add binding XML to jar file, and use this modified jar from addons folder? Is the problem somewhere else (I haven’t read into the aforementioned thread yet) and this module won’t be recognized anyway?

7

You could modify a binding XML like @juno did here. Also note that @Juno has a stub in the ZWDB.

It’s your money, but I don’t know I would buy a device just to get the XML. This should be resolvable.