zwave-js / zwave-js-ui / 27678199728

8%

push

github

fix(hass): add LZW45 to Inovelli RGBW Home Assistant discovery template (#4669)

## Summary

Add the Inovelli LZW45 Light Strip (`798-1-10`) to the existing
`rgbw_bulb` Home Assistant MQTT discovery definition used by the
Inovelli LZW42 Multi-Color Bulb (`798-1-5`).

## Problem

The LZW45 currently falls back to the generic `light_rgb_dimmer`
discovery template. The generated MQTT discovery payload contains RGB,
brightness, and color temperature support, but Home Assistant does not
correctly expose or handle all color controls when discovered through
this template.

Example of the generated discovery payload:

```json
"supported_color_modes": ["rgb", "brightness", "white"]
```

and

```jinja
{{ '%03d%03d' | format((value_json.value.warmWhite || 0), (value_json.value.coldWhite || 0)) }}
```

In testing, Home Assistant would create an entity that supported basic
on/off and brightness control but did not reliably expose or operate RGB
and color temperature controls.

## Investigation

The LZW42 already has a device-specific Home Assistant discovery
override defined in `devices.ts` and is mapped to the `rgbw_bulb`
template.

The LZW45 exposes the same relevant Command Class values used by the
LZW42:

* `38-0-currentValue`
* `38-0-targetValue`
* `51-0-currentColor`
* `51-0-targetColor`

The Color Switch payload also contains the same RGB + Warm White + Cold
White structure expected by the existing `rgbw_bulb` discovery template.

Manual testing was performed by replacing the generated
`light_rgb_dimmer` discovery configuration with the LZW42
`light_rgbw_bulb` configuration. After rediscovery, Home Assistant
correctly exposed:

* On/Off
* Brightness
* RGB Color Control
* Color Temperature Control

This behavior was reproduced on multiple LZW45 devices.

## Solution

Create a shared `INOVELLI_RGBW_DEVICE` definition and map both the LZW42
and LZW45 to it:

```ts
'798-1-5': [INOVELLI_RGBW_DEVICE],  // Inovelli LZW42 Multi-Color Bulb
'798-1-10': [INOVELLI_RGBW... (continued)

410 of 537 branches covered (76.35%)

Branch coverage included in aggregate %.

40 of 40 new or added lines in 1 file covered. (100.0%)

4420 of 24880 relevant lines covered (17.77%)

1.12 hits per line