Eve Dimmer and MinLevel

[young leaf]

My Eve Dimmer only dims the light from 100% at CurrentLevel = 0xFE to something like 60% at CurrentLevel = 1. Eve's support says that I need to set Dimming Thresholds > Minimum in the app. However, the app requires a Google Home hub, so it is not an option for me.

Reading the Matter spec, I see that the Level Control cluster provides the MinLevel attribute, which looks like it should be responsible for setting the minimum brightness. I don't see this attribute in the device properties. I wonder if this is because the dimmer does not implement it or because HA does not expose it.

[quaint rampart]

Hello @young leaf . Could you open an issue here: https://github.com/home-assistant-libs/python-matter-server and attach the diag file?

[young leaf]

Thanks. Created.

[quaint rampart]

It's probably related to these attributes:

• MinLevel / AttributeId: 2 (0x002) - Value type: Optional[uint] = 1
• MaxLevel / AttributeId: 3 (0x003) - Value type: Optional[uint] = 254

[young leaf]

My understanding is that MinLevel and MaxLevel determine the range of values that CurrentLevel is allowed to take. I am able to set CurrentLevel to the full range of values. However, CurrentLevel = 1 does not correspond to zero current. According to Eve's support, the dimming thresholds setting controls that.

Though, it is possible that the support misunderstood my question or is simply mistaken. I could only get one response from them, and even that took nearly two weeks.

[young leaf]

By the way, how do you get that information out of the diagnostics report?

[quaint rampart]

You can enable it in the addon:

[quaint rampart]

It seems that min and max are read only attributes

This may require update an Eve manufacturer attribute.
Not having this product, I don't know.

[wary igloo]

(1) is diagnostics after changing the light mininmum from 20 to 50

(2) is after changing the status led to off

i don't see any changes here, do i need to reinterview nodes or something after making a change in the app?

[quaint rampart]

If nothing changes, I assume the attribute is hidden.

[wary igloo]

It does not show up in Apple home either fwiw, usually there'll be a few more options for devices there.

(If it matters, which I doubt it does, this is on a ha yellow otbr and then shared off to apple home)

[wary igloo]

this is the contents of EveCluster https://gist.github.com/zifnab06/78917726673f6521d96ff4c1bde67721

[quaint rampart]

They probably use ByteArray setConfig 319422465 command

[wary igloo]

i unfortunately don't know enough about matter to say, on the app side, its definitely calling getConfig/setConfig with custom byte arrays mapping to various commands

i'll probably keep messing with this, i am amused.

its definitely doing something with those two attributes, need to go do other things so probably as far as i'm going to get today.

[quaint rampart]

It's already a good clue.

[quaint rampart]

I found a guide on how to create custom cluster on both the Matter Accessory Device (MAD) and the Matter Controller.
https://github.com/SiliconLabsSoftware/matter_applications/tree/master/matter_thread_custom_cluster
It must be the same principle of operation with this Custom EveCluster.
We need to know the identifier for each command from zero to n.

[wary igloo]

for dimmer: min is 50, max is 51, they both take an integer percent

I don't see anything here for status light

[quaint rampart]

This parameter should be added to the Matter specifications to avoid using a specific attribute.

[young leaf]

The Matter spec already has MinLevel and MaxLevel parameters. It looks to me like Eve could have made CurrentLevel span the whole range that the device is capable of and use the additional attributes to limit it, instead of "dimming thresholds". They would just need to make those attributes read-write.

[quaint rampart]

These attributes are read-only in Matter specs and cannot be configured.

[young leaf]

Is it not allowed to make an attribute read-write if it is read-only in the spec?

[quaint rampart]

no

[young leaf]

I see. Then it looks like a significant omission in the spec.

[wary igloo]

my read of all this (and sorry, matter is brand new to me) is they should have exposed these as attributes directly instead of some weird on device command

(and those attributes can be custom?)