Moods, I think, could use a little improvement.
They were originally designed to set lighting scenes that can be recalled. And for that purpose, they work great. Click a button and your lights dim to ‘movie mode’. But then we encounter a problem.
In order to transition between moods effectively, every mood must contain every light. Otherwise, you could recall a mood and non-included lights won’t toggle, forcing you to manually make adjustments- completely defeating the point of recalling a lighting scene. And if you add a light, you must edit every mood you have individually and set settings.
This issue is compounded if you have lighting scenes per time of day or activity- a pre sunrise, a daytime, an evening, an all brights for cleaning, a movie mode, a dim, an ultra dim, or more.
My proposal:
A big lookup table, with all zone moods on one axis, and all lights (and available parameters) on the other axis. Table values are just numbers, with possibility for a null value.
What it accomplishes:
Add a light or a mood, and you can quickly set all the parameters for all your lights in one place in a fraction of the time otherwise necessary. Plus easier editing in the future. The null value is important because sometimes you don’t need every parameter set.
Additionally:
An ‘And’ card for moods. Checks if a mood is currently active. Right now the solution for this is to make a flow to set a variable when a flow is activated. But it’s extremely tedious making a parallel flow to turn ‘off’ that mood if any manual adjustments were made. Implementation of the ‘And’ card would be to check the current parameters of the mood’s lights against the lookup table.
Anyone have thoughts? Or other ideas?