#Auto-adjusting parameters on multiple dimmers daily.

1 messages · Page 1 of 1 (latest)

halcyon beacon
#

Hello everyone! I'm just far enough down the HA rabbit-hole that I can't see daylight anymore....

I have six Inovelli White Series dimmers that I'm playing with before I commit to a full build-out of 70+ devices. I've been playing with HA adjusting the default on level for the dimmer so that the dimmer comes on (regardless of what triggers the on event) at varying brightness levels throughout the day/night. This is currently an automation modifying that particular entity on the device at different points throughout the day.

I've also setup automations so that a double-click of the up paddle always gives immediate 100% brightness (overriding the default level) and double-clicking the down paddle shuts off all lights in the room.

For six devices, and three unique triggers, working with individual automations for each button is manageable, but with a planned build-out of 70+ similar devices, and the possibility of programming for 1x, 2x, 3x, 4x, and 5x taps for each of the three buttons plus managing the default dimmer-on level, I feel like there has to be a more efficient way of managing these parameters. Any guidance on how I should proceed? Even a Blueprint that builds the standard automations would be helpful (especially for the up/down and scene button taps) but really I'd like to avoid needing to modify 70+ automations should I (for example) desire to adjust the default dimmer-on levels for all devices.

I'm thinking of defining the different dimmer levels (daytime, nighttime, and a very dim setting I like to use while the "Sleep" schedule on my thermostats is active) as constants (helpers?) and triggering a script that would run through each device and modify the default dimmer-on levels without needing one automation conditionally modifying 70+ devices or 70+ automations modifying the dimmer-on level for each device.

Again, just looking for the correct words that would get me self-navigatiing the correct rabbit hole. 😅

stone mountain
#

You could create your own integration for this 😄

mellow sapphire
#

You're fairly far down the rabbit hole CasitaHappy

Yeah you could create your own integration, but you don't necessarily need to go to that extent if you don't want.

I think you're on the right track with defining different dimmer levels, as long as those levels can be extrapolated to each room's lights the same way.

In my setup I have different 'brightness profiles' for different times of the day via templating and variables that get applied on a per-light basis throughout the home so I have a 'modifier' variable for each room that acts as a multiplier on each light's defined brightness values in the room. The switches, Inovelli blues in my case, dim by adjusting their room's modifier variable. Whenever the modifier variable changes, the lights (via automations that trigger on any state change in that modifier) receive new brightness updates. I have fallback logic in place for lights to dim directly but in a more basic way using bindings if the server were to go offline. There's much more simple ways to go about this, but this is imo the more maintainable way to do it when your lighting system is already very heavily automated.

halcyon beacon
#

At my day job, I dabble in automation (I maintain some rather complex PLC systems), so I'm not entirely on unfamiliar territory, I just don't speak the local langauge. I was also unsure I wanted to get this deep with tech at home but, here we are, lol.

#

I think I'm going to try setting up the helpers for dimmer levels. The next challenge would be the button tap settings. I'll have a think on that one I guess!

fringe fox
#

one thing you could look into is writing an automation blueprint for handling the dimmers. then you only have to write it once, and you can use it multiple times, providing different devices and helpers as parameters.

mellow sapphire