Local executions new indicator (BETA Firmware)

[CarlosJ (Carlos Juarez)]

@Mariano_Colmenarejo

As STHM runs in the cloud, the real problem is that if the internet fails, you don’t have STHM, it is as if were already disarmed.

To somewhat compensate for this problem, in addition to STHM, automations can be made with the smart lighting app, which is local, to activate the siren, which is also local, with some sensors in the house when the location mode is away.

Thats a great tip… I will do that to do not depend of internet connection to keep alarm prepared to trigger the siren…

[Nezmo]

@Brad_ST

I cannot make any promises about them getting addressed but does this look like a consolidated list of features available in Smart Lighting that users would like to see in the automation rule builder?

1. Turn off device X amount of time after device event happens
   example: Turn off backyard light 5 minutes after motion stops on backyard motion sensor.

2. Greater than 60 minute offset for sunrise/sunset events
   example: Turn on backyard light 120 minutes after sunset.

3. Mirror behavior
   example: Pool light mirrors the behavior of backyard light.

4. Additional preconditions
   example: Turn on pool light at 8 pm only if backyard light is on.

5. Ability to mix sunrise/sunset and specific time as period of time filter
   example: Turn on backyard light if motion is detected on backyard motion sensor and it is between sunset and midnight.

I don’t believe any of these have seen the light of day yet have they (not sure about #4)?

I finally started converting my SmartLighting to Routines. It’s very disappointing that after all this time there’s still a bunch that I can’t convert (or I have to replace with multiple routines).

[Automated_House (Jimmy)]

If I understand them right, #1 and #4 are solved. You can now set “no motion for X minutes” or “door stays open X minutes” conditions. And just about any condition can be set as a precondition now.

[Nezmo]

@Automated_House

If I understand them right, #1 and #4 are solved. You can now set “no motion for X minutes” or “door stays open X minutes” conditions. And just about any condition can be set as a precondition now.

Thanks. Yeah, I realized the preconditions are there.

For #1 I think I misunderstood and yes, looks like Routines covers that now.

#2 and #5 are a real pain.

[TheHundredthIdiot]

For me No’s. 1&3 would take first place(s), I see potential if groups were available to routines (rather than scenes) but mirror is something I use a lot in conjunction with conditionals such as lux & movement…

The ability to perform an action across many things (lights/sockets off for ex.) outside of scenes and multiple target routines is invaluable, again something actionable groups would help address but all useless if routines/scenes remain limited to 200 - which I hit a while ago and use Smart Lighting to help mitigate…

[Nezmo]

@Automated_House

If I understand them right, #1 and #4 are solved. You can now set “no motion for X minutes” or “door stays open X minutes” conditions. And just about any condition can be set as a precondition now.

Actually, I did not misunderstand. Your comment here:

Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.42.07

This is working as designed for routines. If you add an auto-off to the On action then its a pure timer. Doesn’t take into account the conditions on the IF side. In routines what you’d probably want is another routine with IF no motion for X minutes THEN turn off light.

This is what I thought it was doing which is not what I want. I want to be able to specify n minutes after motion has stopped. However, I’ve been testing this and I’m not convinced what you describe is actually happening. More to come.

UPDATE: Okay, so it looks like new activations of a motion sensor does basically trigger the automation again effectively restarting the auto-off timer. But I do think the timer is from the start of the trigger, not when motion stops for eg. That’s where I was getting mixed up.

[Automated_House (Jimmy)]

Yeah there’s two types of “delays”.

The IF condition is a remains statement that resets every time the condition is broken before the time is up

The THEN action is a wait statement that starts as soon as the IF side valuates true and AFAIK it is not canceled if the IF side changes from true to false.

[jsulliweb (Sully)]

My only complaint with this is that it still can do a delay for two things (two motion sensors, no motion, for 5 minutes), and if you do a delay, it’s no longer a local routine. Both were possible in SmartLighting. I’ve migrated, but I’ve had to do virtual switches as a workaround…

[Automated_House (Jimmy)]

@jsulliweb

still can do a delay for two things (two motion sensors, no motion, for 5 minutes)

Not sure what you mean by this? I can do multiple remains statements together

[jsulliweb (Sully)]

Hmmm….

Edit: I think my issue is that if both sensors aren’t triggered with motion, the light doesn’t turn off because the second remain statement is never triggered. That’s why it hasn’t worked for me.