Min Max DIM values

[senadjukic]

I would like to understand why is there a limitation to set the max dim value below 50% in the app (and with it probably also in the api)?

https://freeimage.host/i/3gHHKdP

In certain rooms I never want to go full capacity.

Also I realized the physical switch is not respecting this limit. If you press the dim button (+) for a bit longer, it goes to 100%.

[woodworm]

Min is between 10%–40% and max between 50%–100%. These values are defined by the dimmer-device itself.
But no matter whether you set min to 20% and max to 60%, or min to 10% and max to 75%, when operating the load, the value is always shown as being between 0% and 100%.

[senadjukic]

I get the point that you are allowing the app slider to go always between 0-100% given the user-specified ranges.

Yet, if I never want to go on dimmer device max 50%, but just 30%, I don't have an option. Why can't I set a dimmer device max of 30%?

My endgoal is that this is a variable which I could define, even based on daytime (in a script). That would allow to say it's 10pm, if you press physically the button, dimmer max should be 30%. If I go in app slider to 100%, that would result to 30% on the dimmer device.

With that every light-sensitive person will not be shocked :D

That will play nicely with the button led variable, as you can set this after sunset to a minimum, to find the phsyical button.

The workaround would be that I listen via websocket to the websocket event and then "correct" it via external controller, but that will always be delayed. The planned button API would likely have latency too.

[woodworm]

Very interesting use cases! If I understand correctly, you would ideally like to completely take over the functionality of the '+' and '-' buttons on the dimmer, and depending on the situation, control the load on the dimmer yourself in response to button events?

At the moment, I don’t have a ready-made solution for overriding the '+'/'-' buttons on a dimmer that currently operate in a decentralized way. However, I will bring this up internally for discussion.

In addition to the "max_level" and "min_level", the dimmer configuration also includes a "turn_on_level". The "turn_on_level" (used for the jump on button click) can be set lower than the "max_level" (used during button press).
This might possibly be a solution for your case.

[senadjukic]

Very interesting use cases! If I understand correctly, you would ideally like to completely take over the functionality of the '+' and '-' buttons on the dimmer, and depending on the situation, control the load on the dimmer yourself in response to button events?
Yes, exactly. That will allow the app and the dimmer device to respect the same ranges. The only caveat that I see that a dimmer device always needs connectivity with the gateway before executing a physical button event (like button up). I am ok if there is a fallback if gateway is not reachable, but primarily it could react based on gateway calls (or store locally the settings pushed by gateway).

I could imagine even more flexibility with controlling the dimmer physical device (+/-).
That would even allow flexibility, such as dimming on steps.
Let's assume I want to have a "low" (1000), "medium" (5000), "high" (10000) brightness step through button clicks.

Bri: 0
+ Dimmer Device Button Up
Bri: 1000 
+ Dimmer Device Button Up
Bri: 5000
+ Dimmer Device Button Up
Bri: 10000

That would solve a huge problem, as I can not fumble around to get towards Bri: 1000 with the button dimming. Often, I press too long down (-) so that the lights get shut off. I hope the illustration is clear :-)

And yes I know there are workarounds such as having the button now as a smartbutton and have a custom event, listening on the websocket, reacting in that way..

In addition to the "max_level" and "min_level", the dimmer configuration also includes a "turn_on_level". The "turn_on_level" (used for the jump on button click) can be set lower than the "max_level" (used during button press).

This is an interesting fact, I could then have the turn_on_level = 1000 at least. That would just overwrite that I could have "last_value" as an option.