Yeah I have a similar work-around in place. Was just curious to whether the actual problem had been addressed somehow.seattleneil wrote: ↑23 May 2024 18:33A potential work-around is to the "Virtual Device (JavaScript)" app (aka CodeDevice module) to create a multilevel switch, where the
command is something like: zway.devices[ZWAVE_DEVICE_ID].instances[CHANNEL_ID].commandClasses[0x79].Set(8,%%). Please understand that you'll need to determine the correct command to control the tone for a channel which you can do using the Expert UI. The virtual device will appear as a dimmer switch on the smarthome/normal UI where the dimmer level will be the tone. You can then change the icon from a light bulb to something more meaningful.
COMMAND_CLASS_SOUND_SWITCH support
Re: COMMAND_CLASS_SOUND_SWITCH support
-
- Posts: 193
- Joined: 02 Mar 2020 22:41
Re: COMMAND_CLASS_SOUND_SWITCH support
Based on Z-Wave.me adding products with Zigbee and Matter support, it feels like the Z-Way developers are less focused on Z-Wave technology. I understand they have a business to run, but it makes me a little sad. If I wasn't so lazy, I would experiment with Z-Wave JS UI and Home Assistant.
Re: COMMAND_CLASS_SOUND_SWITCH support
Missed this thread. Don't you have a button in the UI created for each tone? It should be rendered automatically. This works since 2019.
Re: COMMAND_CLASS_SOUND_SWITCH support
To set the default tone of a channel,
Code: Select all
zway.devices[nodeID].instances[X].commandClasses[121].ConfigurationSet(Y,255)
and Y is the tone (1-30).
To trigger the default tone of a channel,
Code: Select all
zway.devices[nodeID].instances[X].commandClasses[121].TonePlaySet(255,255)
Both of these are only available through expert commands or ZWaveAPI and are the two of the most useful commands imo.