What are best practices for scenes vs modes? should you encode actions into scenes vs having RM rules that trigger on scene changes? Scenes don't seem to work that well, any way to fix?
I have 4 modes and 5 modes
- Away (All presence sensors leave)
- Daytime (Sunrise occurs)
- Evening (Sunset+offset occurs)
- Sleep (pico button pressed)
- Sunset (Transition lights from Daytime to Evening)
- Night Away (Fewer lights on in the house after dark when no one is home)
- Play (Dimmer lights than Sunset, focused on creating atmosphere for watching tv and getting ready for bed)
- Bed (All lights off except bedside tables)
- Lights Out (all lights off)
Some other things besides lights happen in the scenes, like closing blinds, turning on or off specific air filters or whole house fans, set thermostat temperature, open and close HVAC vents. Some of these things are in the scene others trigger from RM due to a scene being active.
- Am I doing this right?
- Why not just use modes for everything?
What are best practices for scenes vs modes?
- What is the reason for using scenes at all vs rules that are triggered
Should you encode actions into scenes vs having RM rules that trigger on scene changes?
- Right now things seem to work mostly well, although occasionally scene changes based on modes just don't fire
Scenes don't seem to work that well, any way to fix?
- Set the light
- Click capture button
- Sometimes the scene will swith to (ON) sometime it'll stay on (Not Set)
- Click Capture button again, most of the time it will switch to (ON)
- Activate a new Scene, about half the lights will switch to no scene state for new scence may switch to (on) may stay as (not set)
- tap activate button AGAIN, rest of lights will switch over, scene will switch to (ON)
If anything in the scene changes (e.g. manually adjust a light) scene will become in active (not set) which mostly makes sense but makes scene based rules hard, since one you change anything set by the scene you're now in no scene