espressodaily wrote:1. Lighting scene - e.g. Mood in kitchen. Turn a bunch of lights off, some on and to a certain dim level.
It depends on how you trigger it. But in any event you can define it as an Action Group then call that action group from any triggers/schedules.
espressodaily wrote:2. Leak detection - when water detected turn on pump for a few minutes or until no water
That's definitely a trigger with an action to turn on the pump with either an auto off after some time or another trigger that turns it off when the leak sensor goes off.
espressodaily wrote:3. Thermostat scheduling - at a particular time, set to cool or heat and temperature.
The simplest way is with schedules that run at your particular times which just have an action to set the thermostat. There are other ways of making a much more sophisticated thermostat schedule but you may not need it.
espressodaily wrote:4. Turn every light off
Same as #1. I think everyone here has an action group that turns everything off. You could make a Virtual Device, but if the only real use is to turn them all off then an Action Group is fine.
espressodaily wrote:5. Motion - when motion occurs turn on light. Turn off in 15 min if no motion
Trigger on the motion sensor going on, turn on the light. If your motion sensor has a setting to set a timeout, then just set the timeout to 15 and add a trigger on the motion sensor going off, turn off the light. If you can't adjust that in the motion sensor itself, then create a trigger with an action to turn it off delayed by 15 minutes.
The lesson here is that the generic concept of "scenes", IMO, is too ill defined (and means different things to different people and different products). What you have to do is think about these things in terms of "scenarios" (or use-cases if you're a developer). Clearly define the scenario, and then the solution is much easier to discover.