Are Shelly Qubino Wave Shutter modules supported by Domoticz?

[mantoz]

Hi guys,
I've just installed 4 Shelly Qubino Wave Shutter modules to control my blinds.
While I've been able to use them to open and close my blinds (fully open or fully close only for now), it seems they're not fully supported, there's no configuration.

qubino_mods.jpg (83.05 KiB) Viewed 2415 times

Did anyone know something more about this please?

Thanks,
mantoz

[mantoz]

OK, some more investigations and a reply to myself as this could be helpful to some other user.
OpenZWave is not maintained anymore, so new devices are not added to the device database anymore (and SW development has stopped, I think, what a pity!).
However, as all devices need to be compliant to ZWave specs, basic features work out-of-the-box and just a config file is needed to have some additional features.

So I added the following lines to domoticz/Config/manufacturer_specific.xml file to make OpenZWave recognize the new Shelly/Qubino Wave Shutter devices:

Code: Select all

<Manufacturer id="0460" name="Shelly Qubino">
	<Product config="shellyqubino/waveshutter.xml" id="0082" name="Wave Shutter" type="0003"/>
</Manufacturer>

Then I created an additional config file named domoticz/Config/shellyqubino/waveshutter.xml to add some additional info:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<Product xmlns='https://github.com/OpenZWave/open-zwave' Revision="2">

<!-- ShellyQubino: Wave shutter -->

	<!-- Configuration  -->
	<CommandClass id="112">
		<Value type="list" genre="config" instance="1" index="71" label="Operating modes" size="1" min="0" max="1" value="0">
			<Help>This parameter defines selection between two operating modes. NOTE: After setting a mode the module needs to be reconfigured. Please check the detailed description in the product manual.</Help>
			<Item label="Shutter mode" value="0" />
			<Item label="Venetian mode" value="1" />
		</Value>
		<Value type="list" genre="config" instance="1" index="78" label="Forced Shutter calibration" size="1" min="0" max="1" value="0">
			<Help>By modifying the parameters setting from 0 to 1 a Shutter enters the calibration mode. Once the calibration process finished the parameter reports a result value: 2: device calibrated, 3 device not calibrated, 4 calibration error</Help>
			<Item label="Default" value="0" />
			<Item label="Start calibration process" value="1" />
		</Value>
	</CommandClass>

	<!-- Association Groups -->
	<CommandClass id="133">
		<Associations num_groups="2">
			<Group index="1" max_associations="16" label="Multilevel" auto="false"/>
			<Group index="2" max_associations="1" label="Lifeline" auto="true"/>
		</Associations>
	</CommandClass>

	<!-- Remove COMMAND_CLASS_BASIC -->
	<CommandClass id="32" action="remove" />

</Product>

After restarting OpenZWave/Domoticz, the new Shelly/Qubino devices are correctly identified. If you don't have the additional info specified in waveshutter.xml, just try refreshing the node in the node list of your ZWave controller.
Just an additional note, you probably need to perform a calibration of the Shelly Qubino Wave Shutter after installing it for the first time to have it working with percentage open/close commands. You can perform it through on the specific node menu.

Ciao,
mantoz

[waltervl]

And just an advise if you want to keep using and updating Domoticz: switch to Zwave-JS-UI. https://www.domoticz.com/wiki/Zwave-JS-UI

[lost]

just a config file is needed to have some additional features.

Hello,

You may IMO make a PR to OZW github for these additions, I did some for unsupported Hank products, maybe 1 year after Fishwaldo step-down, and Nechry was able to merge them...

Provided you stick to a gen5 controller max (bough a refurbished backup at low price 1 year ago to have a spare for my 2016 SPOF device), OZW will still do the job if adding config files and their IDs/Config link in ManufacturerSpecific file. If config info in device documentation is not present, this can usually be found on zwave-alliance site: They store config data info for all certified products...

Even if the PR is not handled, files will remain present & may be found more easily by others with same needs.

[waltervl]

There is no merge action for more than 1 year on OpenZwave, the project is dead.......
https://github.com/OpenZWave/open-zwave

[lost]

And just an advise if you want to keep using and updating Domoticz: switch to Zwave-JS-UI. https://www.domoticz.com/wiki/Zwave-JS-UI

For a working setup, especially for years, changing may mean in the end sound like... breaking.

One reason for removal was compilation issues on newest distros (Ubuntu was used for build & Debian based) I remember to have read this at the time this was announced. But looks Debian maintainers were able to fix this as latest Bookworm (+next Trixie... and even Sid) still package OZW:
https://packages.debian.org/bullseye/libopenzwave1.6

[lost]

There is no merge action for more than 1 year on OpenZwave, the project is dead.......
https://github.com/OpenZWave/open-zwave

So those who had needed rights for project merge gave-up... There may be some place for an alternate config tree repo, we may name this "openzwave-notdead"!

[waltervl]

If you feel that urgent need you can also take over the maintenance of the original repository, then it is not dead anymore.....

[lost]

If you feel that urgent need you can also take over the maintenance of the original repository, then it is not dead anymore.....

I'm not sure that if a minimal project maintenance (let's say to handle build issues for Linux/minimal code change, windows may be a problem as I don't use this OS since ~15 years now but some help may show-up & merge new devices configs) was still done this would now change anything on Domoticz side. If I'm wrong, yes, I may find enough time to spend on this.

[gizmocuz]

Best to merge this into the Domoticz github repo (just done)