You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.I have a Hue bulb and a Hue on/off /dimmer switch. In the Rules screen I have 2 rules so that the on and off buttons control the bulb state. But when I try to set up rules for the “increase/decrease brightness” buttons (event 2 and event 3) the bulb thing only allows me to set the brightness to a certain fixed level. What I need is to be able to set it to its current level + a percentage.
The text was updated successfully, but these errors were encountered:
Try using the "Followers" add-on. Then you can specify a range from one thing to be applied to a range on another thing. The ranges don't even need to match.
This would be also very helpful for me! Are there already plans to implement this?
We're trying to keep the rules engine UI as simple as possible. I'd say that a reasonable goal for the rules engine UI is that 80% of rules can be set with the simple drag and drop UI, and the other 20% require a custom add-on to do something special. My gut feeling is this use case of increasing/decreasing the value of a property by a fixed increment falls into that 20%. But if anyone has ideas for how to incorporate this into the UI without adding too much complexity then I'd be happy to review designs.
benfrancis
changed the title
Rules Engine - need more possibilities for setting property of dependent Thing
Rules Engine - increase/decrease numeric property by a fixed increment
Feb 1, 2021
1.I have a Hue bulb and a Hue on/off /dimmer switch. In the Rules screen I have 2 rules so that the on and off buttons control the bulb state. But when I try to set up rules for the “increase/decrease brightness” buttons (event 2 and event 3) the bulb thing only allows me to set the brightness to a certain fixed level. What I need is to be able to set it to its current level + a percentage.
The text was updated successfully, but these errors were encountered: