Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge πŸŒ‰, get rid of your proprietary Zigbee bridges πŸ”¨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.72k stars 1.64k forks source link

White LED of RGBW driver 5110.40 is always on #18804

Open Stefan-3 opened 1 year ago

Stefan-3 commented 1 year ago

What happened?

Main issue Controlling the RGB LEDs with LED driver 5110.40 (iluminize.js) is working fine but it's not possible to control the white LEDs of the RGBW LED stripe. The white LEDs are always on with max. brightness. Modifying iluminize.js is not enough (adding multiendpoint results in error log message "not supported by converter").

"Expanded" issue The LED driver 511.000 from sunricher can be configured with 2 mechanical dip switches to match to the connected LED stripe type (DIM, CCT, RGBW, RGB+CCT). Currently it's quite a "chaos" regarding this device:

image

So, the converter for LED driver 511.000 is implemented at 4 different locations. I suggest cleaning this up: a) all 4 configurations in file sunricher.js (and within this file one configuration after the other) b) harmonized model name in converter file (e.g. modelId). This means HK-ZD-DIM-A instead of SRP-ZG9105-CC, HK-ZD-RGB-A instead of 5110.40, ...

These are the corresponding entries in the shepard file for all 4 dip switch settings: shepard answers.txt

Note: The RGBW driver 5110.40 is currently the "one and only" recommended device at the wholesaler isolicht.com: https://www.isolicht.com/led-beleuchtung/installationsmaterial/dimmer-schalter-schutz/zigbee-3-0-dimmaktor-fur-led-12-24v-4x1-5a-36-48v-4x0-75a

What did you expect to happen?

Endpoint to control white LED.

How to reproduce it (minimal and precise)

Set dip switches of LED driver to RGBW dimmer --> endpoint to control white LED is missing

Zigbee2MQTT version

1.22.1

Adapter firmware version

20211210

Adapter

SONOFF ZIGBEE 3.0 USB-STICK

Debug log

No response

github-actions[bot] commented 11 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Stefan-3 commented 11 months ago

The problem is still present and the device is used quite often especially in Germany. So sooner or later many other users will have the same problem.

github-actions[bot] commented 10 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Stefan-3 commented 10 months ago

still waiting

github-actions[bot] commented 4 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Stefan-3 commented 4 months ago

still waiting