Inovelli VZW31-SN Firmware 1.2 New Parameters

[DAVe3283]

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there.

Describe the bug

What causes the bug?

Firmware 1.2 (https://community.inovelli.com/t/red-series-2-1-firmware-changelog-vzw31-sn/14579) was recently promoted to stable (zwave-js/firmware-updates#83). It adds 2 new parameters (temperature and overheat) and an option from 1.1 (leading or trailing edge dimming). These options don't have config values in this repo.

What do you observe?

The temperature parameter shows up, but it is not being reported as a measurement, and the temperature units are missing. This causes Home Assistant to display it is a string, instead of a number and recording the history in a graph.

Switching between leading and trailing edge is also somewhat ambiguous.

On other parameters, the values would be labeled in a drop-down, e.g. [0] Leading Edge, [1] Trailing Edge.

What did you expect to happen?

The new parameters should show up with the correct units as the other parameters do. This would let the temperature show up as a history graph like other Z-Wave devices reporting a temperature have.

Steps to reproduce the behavior:

1. Update a VZW-31SN to firmware 1.2
2. Enable one of the new parameters (e.g. Internal Temperature) in Home Assistant
3. Note how the parameter has no units and doesn't get a history graph.

Device information

Manufacturer: Inovelli
Model name: Red Series 2-1 Dimmer (VZW31-SN)
Node ID in your network: 9

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

Z-Wave JS UI: 8.24.2
Z-Wave JS: 11.14.0
Home Assistant Add-On Version: 1.15.9

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

No, it never worked anywhere

If yes, where did it work?

No response

Attach Driver Logfile

Do you need a log of a re-interview to see the new parameters? Let me know what you need and I will provide it.

[zwave-js-bot]

👋 Hey @DAVe3283!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log is required to diagnose most issues.

Please consider uploading a logfile that captures your problem.

[InovelliUSA]

For P26 can we NOT have it as a selectable option in the GUI or have it read only? Changing this setting remotely can damage the device if an improper load is connected. It is ok to change it via combo button or to send it as a custom configuration parameter from the control panel:

Just want to be cautious that people don't willy nilly change it. The combo button is:

Hold down + press config 13x = trailing edge
Hold up + press config 13x = leading edge

[AlCalzone]

Absolutely!

[AlCalzone]

Parameter 26 added in #6391

[InovelliUSA]

@AlCalzone Thanks! I see the note you placed in the file.