DDF for iluminize Multi 5 (4A) #7977

bluemoehre · 2024-10-16T22:17:17Z

Controller by iluminize, which can emulate multiple controllers (Dimmer, CCT, RGBW, RGBCCT).

Will solve #7985

All Screenshots

Dimmer

CCT

RGBW

RGBWCCT

github-actions · 2024-10-16T22:18:33Z

Hey @bluemoehre, thanks for your pull request!

Tip

Modified bundles can be downloaded here.

DDB changes

Modified

iluminize/led_controller_multi_5.dim.json : LED Controller Multi 5 (DIM mode) ✔️
iluminize/led_controller_multi_5.rgbw.json : LED Controller Multi 5 (RGBW mode) ✔️
iluminize/led_controller_multi_5.cct.json : LED Controller Multi 5 (CCT mode) ✔️
iluminize/led_controller_multi_5.rgbcct.json : LED Controller Multi 5 (RGBCCT mode) ✔️

Validation

Tip

Everything is fine !

_{🕣 Updated for commit 1adcf5d}

bluemoehre · 2024-10-16T22:24:20Z

The device is missing some items because a device with "state/x" or "state/y" need the corresponding cap/color/xy/{red,green,blue}/{x,y} items

That cluster/attribute 0x0300 / 0x003a is not present. How to deal with this conflict?

ebaauw · 2024-10-16T22:35:32Z

Just define the capabilities with static values.

ebaauw

You didn’t post screenshots of the Basic cluster, so I don’t know what ZCL version the device supports, but I would expect it to support attribute reporting.

Did you re-read the endpoints and Simple Descriptor each time after changing the mode? It might not make sense to expose an RGBW light as Extended Color Light. The colour temperatures will be ugly, mixing RGB and W.

devices/iluminize/led_controller_multi_5.cct.json

ebaauw · 2024-10-17T05:06:07Z

devices/iluminize/led_controller_multi_5.cct.json

+  "status": "Gold",
+  "subdevices": [
+    {
+      "type": "$TYPE_COLOR_TEMPERATURE_LIGHT",


That type should only expose ct; not xy nor hue/sat nor effect (for colorloop).

I checked this again, but the controller does provide these as shown in the screenshot.

In terms of colorspaces it is absolutely possible to convert CCT into HUE and XY. So maybe it is just the first we see doing it?

For the effects I wonder anyhow why there shouldn't be some on dimmable & CCT controllers. Candle / fire flicker would be possible =)

If you expose xy, the type should be Extended Color Light, not Color Temperature Light. However, API clients will expect the light to display colours when you're exposing xy. I don't see any additional value in exposing xy on a CCT light, as it wouldn't enable anything that isn't already enabled through ct. I do see issues with sending the wrong message that the light would expose colours.

Yes, in theory it's possible to express ct value as xy (but, obviously not the other way around). In practice setting ct will drive the WW/CW channels, whereas setting xy will drive the RGB channels, resulting in a different experience.

The only standard effect is colorloop, which is only available on lights supporting colors through hs (as it loops hue values). Hue-specific effects like candle are exposed over the manufacturer-specific 0xFC03 cluster, which this controller doesn't implement.

devices/iluminize/led_controller_multi_5.cct.json

ebaauw · 2024-10-17T05:15:35Z

devices/iluminize/led_controller_multi_5.cct.json

+          "static": 0
+        },
+        {
+          "name": "config/bri/couple_ct",


Does the controller support this? I’d default it to false. Also, I would expect it to support execute_if_off as well.

If you could tell me the cluster + attribute address I will re-check.

BTW: I find it very hard with the DDF editor to match against the controller. My workflow is always drop everything in, then compare endpoints if active. It takes too long and easily causes to miss something. Is there a better way to match the written path vs available clusters/addresses?

It’s a bit in the Options attribute, as is execute_if_off. In the Level Control cluster, hence config/bri. The Color Control cluster has the same attribute, but only with the execute_if_off bit. These are documented (briefly) in the item’s JSON file.

I double checked, but it is as displayed in the screenshots:

Level Control Options bitmap is: 0x01
Color Control Options bitmap is: 0x01

do I need to adjust something?

Does the light actually change brightness when off when the Execute If Off bit in the Level Control cluster is set, and colour (temperature) when the but in Color Control is set?

Does the light actually change colour temperature when changing brightness while the Couple Color Temp to Level bit is set?

ebaauw · 2024-10-17T05:16:28Z

devices/iluminize/led_controller_multi_5.cct.json

+          "default": true
+        },
+        {
+          "name": "config/color/xy/startup_x",


These are only supported on Hue lights.

(… same as below)

ebaauw · 2024-10-17T05:16:57Z

devices/iluminize/led_controller_multi_5.cct.json

+          "default": "0xffff"
+        },
+        {
+          "name": "config/color/xy/startup_y",


These are only supported on Hue lights.

I already talked to the manufacturer and they told me, they have been adding that on purpose to fulfill some Apple requirements. Else it wont be compatible with Home Kit. Anyhow, if it won't cause problems, I can remove it.

Added what? HomeKit doesn’t have poweron settings, and certainly not for colour. I’ve seen some vendors that (illegally) expose the Hue Manufacturer Code 0x100B in the Node Descriptor (also missing from the screenshots), so the Hue bridge exposes them to HomeKit. In that case, they might expose the Hue-specific attributes for poweron xy as well. However, they are not in the screenshots? Do you see them in the GUI? And do they work?

Yep, that's why I talked to them … They said they could provide a “real” firmware without hacks, but the conversation fizzled out - didn't get a reply anymore.

So they (illegally) pretend to be a Hue light, so the Hue bridge exposes it to HomeKit. Do they implement the manufacturer-specific versions of 0x0003 and 0x0004 (Hue Startup Current X and Hue Startup Current Y)? If you set these, and power cycle the light, does it come up with the specified colour?

devices/iluminize/led_controller_multi_5.dim.json

devices/iluminize/led_controller_multi_5.rgbw.json

bluemoehre · 2024-10-17T13:37:32Z

@ebaauw Seems like my idea to copy from another DDF was not the best. Since we have the bot checking DDF files. Are you able to add these hints/rules to it? Then we can run it vs all existing files and do a clean up? This way the next person won't trap into the same problems.

bluemoehre · 2024-10-17T13:51:15Z

You didn’t post screenshots of the Basic cluster, so I don’t know what ZCL version the device supports, but I would expect it to support attribute reporting.

I already mounted it behind a wall ... but I gonna try to upload these as well.

Did you re-read the endpoints and Simple Descriptor each time after changing the mode? It might not make sense to expose an RGBW light as Extended Color Light. The colour temperatures will be ugly, mixing RGB and W.

Since re-reading didn't work all time, causing deCONZ to show old stuff, I deleted the node from the network and then hard reset the controller each time.

bluemoehre · 2024-10-17T14:06:25Z

added Basic cluster for Dimmer Mode (2nd image in PR description)

ebaauw · 2024-10-17T14:07:07Z

@Zehir maintains the DDF validator; I haven’t looked into its internals. It does check for mandatory items, but I don’t think it currently checks for superfluous or deprecated items. Of course, the validator cannot check against the actual device features.

I often copy an existing DDF as a start to create new DDF, but I do check the validity and appropriateness of each item in the GUI. There’s also some hidden (from API clients) capabilities that change the API behaviour, like using Move to Level (with On/Off) or Off with Effect. You need to check in the GUI if the device supports these. There’s a brief description in each item’s JSON file (under devices/generic/items/*_item.json) but there’s definitely room to improve the documentation. The use of the red, green, and blue points, to specify what colors the light can display, is best explained in the Hue API documentation.

ebaauw · 2024-10-17T14:14:51Z

added Basic cluster for Dimmer Mode (2nd image in PR description

ZCL Version 3 is Zigbee 3 and should support attribute reporting.

bluemoehre · 2024-10-17T14:45:15Z

ZCL Version 3 is Zigbee 3 and should support attribute reporting.

So we need to additionally add some reporting config everywhere?

SwoopX

Hi and thank you for your contribution 👍

We would like to ask you to create a new device support request (new issue -> device support) in this repository and to link it against your pull request. Please also make sure one device support PR only covers one device. This fosters consistency, allowing everybody to find device related information at the very same place and helps expediting searches if required. Furthermore, it enables the devs to check and verify if a DDF is created correctly or if any changes/optimizations are necessary.

Thank you very much for your support!

bluemoehre · 2024-10-19T18:38:48Z

We would like to ask you to create a new device support request (new issue -> device support) in this repository and to link it against your pull request.

done

SwoopX · 2024-10-20T17:26:01Z

Thanks a lot 👍

manup · 2024-11-04T14:08:53Z

@ebaauw is the PR ready for merging?

ebaauw · 2024-11-04T15:55:02Z

I suppose so. I don't have the device so I cannot validate the DDF.

bluemoehre · 2024-11-04T16:57:28Z

@ebaauw it would help (me) to understand the status of an issue, if you could resolve all started conversations, where you think it now looks good. This prevents to miss something we had been discussing without having a solution. (Additionally I am not sure if someone could merge with unsolved discussions.)

I will also check myself everything here and in other tickets …

ebaauw · 2024-11-04T21:19:00Z

Since the DDF (by design) won't affect any other devices, merging an incomplete or even wrong DDF would cause no harm, other than the device not working as expected.

The idea of a DDF, particularly of the capabilities items, is to indicate what actually works for this device, not just what attributes it advertises. Checking this requires trying out the features in the GUI, and visually checking the light's reaction. Support for attribute reporting can be checked by the GUI showing the changed values automatically (without having to re-read the attributes), through the deCONZ log, or using a Zigbee sniffer.

So for example, if the DDF advertises the device supports Execute If Off, the deCONZ REST API assumes it does, and will happily send a Move to Level while the device is off, and update state/bri accordingly (rather than raising an API error that the light is off). If the light subsequently is turned on, but doesn't reflect the changed brightness it doesn't live up to the promise the DDF makes to API clients.

github-actions · 2024-11-08T10:18:11Z

This pull request is now merged. The new DDB files have been uploaded to the store.

DDB Files

Modified

iluminize/led_controller_multi_5.dim.json : LED Controller Multi 5 (DIM mode) : with hash (e808f2d67a)
iluminize/led_controller_multi_5.cct.json : LED Controller Multi 5 (CCT mode) : with hash (ce87fb2f2a)
iluminize/led_controller_multi_5.rgbcct.json : LED Controller Multi 5 (RGBCCT mode) : with hash (5d806336f5)
iluminize/led_controller_multi_5.rgbw.json : LED Controller Multi 5 (RGBW mode) : with hash (0603a8231d)

_{🕣 Updated for commit 5bf4142}

bluemoehre added 4 commits October 16, 2024 23:48

add DDF for iluminize multi 5 in dim mode

bfed063

add DDF for iluminize multi 5 in CCT mode

ba0e37b

add DDF for iluminize multi 5 in RGBW mode

a2e0864

add DDF for iluminize multi 5 in RGBCCT mode

f80ead0

add static XY values to fix tests

3151cef

ebaauw reviewed Oct 17, 2024

View reviewed changes

bluemoehre added 4 commits October 17, 2024 17:22

remove unsupported effect attribute

bb6f1d7

fix static XY color values

8ac6239

remove redundant & deprecated attributes

f7014c4

remove redundant & deprecated attributes

1adcf5d

SwoopX requested changes Oct 19, 2024

View reviewed changes

SwoopX approved these changes Oct 20, 2024

View reviewed changes

SwoopX added the Device Request label Oct 20, 2024

SwoopX linked an issue Oct 20, 2024 that may be closed by this pull request

iluminize Multi 5 (4A) #7985

Closed

1 task

manup added this to the v2.29.1-beta milestone Nov 4, 2024

manup merged commit 5bf4142 into dresden-elektronik:master Nov 8, 2024
1 check passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DDF for iluminize Multi 5 (4A) #7977

DDF for iluminize Multi 5 (4A) #7977

bluemoehre commented Oct 16, 2024 •

edited

Loading

github-actions bot commented Oct 16, 2024 •

edited

Loading

bluemoehre commented Oct 16, 2024 •

edited

Loading

ebaauw commented Oct 16, 2024

ebaauw left a comment

ebaauw Oct 17, 2024

bluemoehre Oct 17, 2024

ebaauw Nov 4, 2024

ebaauw Oct 17, 2024

bluemoehre Oct 17, 2024

ebaauw Oct 17, 2024

bluemoehre Oct 17, 2024

ebaauw Nov 4, 2024 •

edited

Loading

ebaauw Oct 17, 2024

bluemoehre Oct 17, 2024

ebaauw Oct 17, 2024

bluemoehre Oct 17, 2024

ebaauw Oct 17, 2024

bluemoehre Oct 17, 2024

ebaauw Nov 4, 2024

bluemoehre commented Oct 17, 2024

bluemoehre commented Oct 17, 2024 •

edited

Loading

bluemoehre commented Oct 17, 2024 •

edited

Loading

ebaauw commented Oct 17, 2024

ebaauw commented Oct 17, 2024

bluemoehre commented Oct 17, 2024

SwoopX left a comment •

edited

Loading

bluemoehre commented Oct 19, 2024

SwoopX commented Oct 20, 2024

manup commented Nov 4, 2024

ebaauw commented Nov 4, 2024

bluemoehre commented Nov 4, 2024

ebaauw commented Nov 4, 2024

github-actions bot commented Nov 8, 2024

DDF for iluminize Multi 5 (4A) #7977

DDF for iluminize Multi 5 (4A) #7977

Conversation

bluemoehre commented Oct 16, 2024 • edited Loading

All Screenshots

github-actions bot commented Oct 16, 2024 • edited Loading

DDB changes

Modified

Validation

bluemoehre commented Oct 16, 2024 • edited Loading

ebaauw commented Oct 16, 2024

ebaauw left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ebaauw Nov 4, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bluemoehre commented Oct 17, 2024

bluemoehre commented Oct 17, 2024 • edited Loading

bluemoehre commented Oct 17, 2024 • edited Loading

ebaauw commented Oct 17, 2024

ebaauw commented Oct 17, 2024

bluemoehre commented Oct 17, 2024

SwoopX left a comment • edited Loading

Choose a reason for hiding this comment

bluemoehre commented Oct 19, 2024

SwoopX commented Oct 20, 2024

manup commented Nov 4, 2024

ebaauw commented Nov 4, 2024

bluemoehre commented Nov 4, 2024

ebaauw commented Nov 4, 2024

github-actions bot commented Nov 8, 2024

DDB Files

Modified

bluemoehre commented Oct 16, 2024 •

edited

Loading

github-actions bot commented Oct 16, 2024 •

edited

Loading

bluemoehre commented Oct 16, 2024 •

edited

Loading

ebaauw Nov 4, 2024 •

edited

Loading

bluemoehre commented Oct 17, 2024 •

edited

Loading

bluemoehre commented Oct 17, 2024 •

edited

Loading

SwoopX left a comment •

edited

Loading