[FeatureRequest] Make moods a registered state/variable that can be requested when a mood is active

Ideas & Suggestions
, ,
1

Currently a mood can’t be setup in advanced flows. But also I can’t see which mood is currently active.
I would want to be able to know which mood is active in a room. One example of where this would help is the following.

My kitchen is in my living room. When I set a mood in my living room I want to also include the lights in my kitchen. But when I want to cook in the kitchen I want to set the lights in the kitchen to another mood. When I’m done with cooking I want to disable the mood “cooking” in the kitchen and automatically set the lights in the kitchen to the mood that is currently active in the living room.

1 Like
2

I haven’t tried the Moods, but I don’t think there is an active state. It’s more like a scene you can activate - like changing many lights with a flow, but set up as one Mood to set up more easily.

1 Like
3

Save it in a text variable, my guess.

2 Likes
4

Hmmm to me it sounds like the “Zone Memory” app is a more suitable way to control pre-defined scenes for you.
To me, Moods sounds as something (still) quite basic.

5

There isn’t an “active”-state for moods. That’s what makes it not possible to request which mood is active right now.

6

Sure but that would mean that for every mood I would need to add an extra card because the moods don’t have tags that share their value in a flow.

7

Zone memory is an app that I’ve already tried. Moods offer a better user experience to define “moods” in a room. Also zone memory does not save the on/off state of a lamp. Tried it many times with my Philips hue bulbs. Also created a ticket about this bug in the past. Same issue still exists.

The reason for this feature request is because I have dozens of flows with many cards and trie to reduce cards and flow sizes so that everything will keep running smoothly now and in the future.

8

As said, a Mood is just called and the “scene” is set to all assigned lights. That’s all. A Mood can’t be “active”. After a Mood is activated, you can change all lights individually.
If you want to activate Moods on special conditions, you can use variables to “remember” your state.

1 Like
9

I know that it is just a scene. For that reason I’ve titled this topic a feature request. Or should I have put this feature request somewhere else?

10

No Problem with that…

Beside contacting support, the is no other option: see Ideas / Feature Requests

No it is a Mood, the mood is a collection of (preset) settings for one or more Light’s

The problem is you never know when the mood is active except the second you activate it (there is a trigger for, mood is activated)
If someone or something ( another flow?) fe switches a Light ON that was set in the Mood to OFF or dims another light in the mood relative with 1% , is the mood then still active?

So therefore the mood is not a state that you can check is conditions,

And I don’t expect Athom will change that.

Guess you have to work around it with Flows and variables.

11

A few months ago, Homey introduced the Moods feature, which allows us to easily set multiple lights to a specific brightness and colour/temperature, a great way to create just the right atmosphere at home. While I find this feature useful, I think there’s some room for improvement, particularly when it comes to Flow integration.

Currently, Moods only offer:

  1. A Flow trigger card that activates when a Mood is set.
  2. An action card to set a Mood.

However, I’ve noticed a gap: there is no way to check if a Mood is currently active. There’s no condition card that allows us to verify if a Mood is in effect, making it difficult to create more complex and mood-aware automations.

If I understand correctly, Homey doesn’t actively track if all the lights that were part of a Mood are still in their defined state. I understand Moods to be stateless. But here’s my suggestion: it would be amazing if a condition card for a Mood could work by checking if all the relevant light properties (like brightness and color/temperature) are still set according to the Mood definition. This would give us a much more powerful tool for building dynamic automations.

I’ve tried to work around this limitation by using a boolean variable to keep track of when a Mood is active, but I ran into another limitation, there’s no trigger card for when a Mood is unset. Without knowing when a Mood has ended, it’s difficult to manage these states efficiently.

The only workaround I’ve found is to manually compare all the individual light capabilities, but this approach doesn’t scale well. It becomes cumbersome with multiple Moods, especially if I make changes to the settings over time.

I’d love to hear if others are facing similar challenges or if the team could consider enhancing Mood Flow cards to include more conditions, like “Is Mood active?”, or even a trigger for when a Mood is unset. This would be a huge help for those of us who want to take full advantage of Homey’s automation capabilities.

Thanks for reading, I’m curious about everyone’s thoughts!

tl;dr I’d like Mood condition flow cards and/or an Mood unset trigger card

3 Likes
12

There was already a topic so therefore merged.

1 Like
13

I have defined a virtual lamp that is included in the Mood. Simply tested if this virtual lamp is on/off gives that the Mood is set/unset.

Kind regards,
Paul

14

But how would you detect that nothing has changed, which would cause the mood to no longer be “set”? For example, if I change the brightness of a bulb that was previously set with a mood, that mood would no longer be “set” because not all of the mood’s properties are fulfilled.

It doesn’t automatically turn off the virtual lamp unless you control your lights exclusively by setting moods. In that case, you can ensure that other moods turn off that specific virtual lamp again.

15

Indeed, in most cases I control my lights using moods. That is sufficient for me. The chances that individual lights are changed manually are rare. And if so, It generally doesn’t matter for my use cases.
Kind regards,
Paul