Skip to content

Myriades-ll/ZW164_py_plugin

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Zwave SoundSwitch CommandClass - plugin for Domoticz

GitHub release (latest by date) Domoticz 2022.2 Python version Zwave JS-UI version

This plugin is intended to get you the ability to use Zwave hardwares that embed the COMMAND_CLASS_SOUND_SWITCH (0x79|121).
In shorter way, you will be able to act with doorbells, sirens, ...

Prerequisites

  • Domoticz functional
  • A MQTT Auto Discover Client Gateway with LAN interface plugin functional

functional hardwares

see functionnal hardwares

Please, send feedback for your onw hardware; not listed 😉

Install

In your domoticz plugin folder:

git clone https://github.com/Myriades-ll/ZW164_py_plugin.git
sudo systemctl restart domoticz.service

Configuration

Zwave-js-ui

Set the retain flag ON like in the picture below.

retain flag

This plugin don't use the autodiscovery. It has its own system. You may have to restart zwave-js-ui to get the retain working.

sudo zwave-js-ui.restart

Domoticz

Add the new hardware named CCSoundSwitch through Zwave-JS-UI. Fill required fields, then start the plugin.

Plugin initialization may take a few time; at most 30 seconds; it has to retrieve some data from hardware. See Domoticz logs to view what's done.

Usage

For every endpoint in your hardware, the plugin will create 2 devices:

  • the first to control the volume
  • the second to select the sound you want to play

Each device represent the actual values of your hardware.

So first, adjust the volume and then select a sound to play it instantly.

Update

in this plugin folder; usually ~/domoticz/plugins/ZW164_py_plugin

git pull

then restart the plugin.

Limits

You can't change actual volume while playing a sound. It will change for the next sound.

If you turn off the volume, the endpoint won't play anymore sound; it will be skipped.

Note

If you upgrade from version 1.0.0:

  • stop the previous plugin
  • delete it; highly recommanded
  • then follow installation and configuration steps of the new plugin; see above