Timer AND event?

Community Playground General Discussions
1

By defining a scene I have the choice to use a timer or an event - or both.

I defined a scene to switch my outdoor lightning off in the morning. I told Vera to switch off the lightning at sunrise and at 7:00. For me I thought that the light goes down either on sunrise OR at 7:00 depending on what is first true.

The result is a permanent garden lightning. :frowning:

How does Vera handle a scene with both a timer an an event? Is it OR or AND?

Any ideas?

huwu

2

(bump)

Did you ever come to a satisfactory resolution on this question?

By the way, Iā€™d have betted anything on ā€œORā€ being the operative word here, since I assume Vera will perform a scene whether the timer wound down or the requisite event occurred.

3

No there was no answer from MCV. But Iā€™m sure itā€™s OR since I have a bit more experience with Vera now.

4

Either a timer or an event can trigger a scene. In the new Luup version sunset/sunrise is now a ā€˜timerā€™ and you can provide an offset (ie 2 hours before sunrise or 1 hour after sunset).

5

As Iā€™ve read in the post no. 6 in thread ā€œGo back to prior settingsā€ ([url=http://forum.micasaverde.com/index.php?topic=742.msg3541#msg3541]http://forum.micasaverde.com/index.php?topic=742.msg3541#msg3541[/url]) the mutliple events functionality is already implemented in the backend and you guys are now thinking about an easy way to let even nontechnical customers benefit from it.
I donā€™t know if you are still thinking about it, but if you do, I have a suggestion for this you might like to pick up.
Well, here it goes:

The scenery itself consists of two parts. WHEN to activate it (timer or event) and WHAT to activate.

Because what to donā€™t has to be changed, I proceed with when Vera should do things for you and me.

The condition(s) when a scene should be activated could easily configured, if the following would be possible:

  1. Timers and events, which lead to activation of a scene, are grouped by logical ANDs (instead of OR)
  2. There has to be the possibilty to create more of those groups. These groups will be concatenated by a logical OR.
  3. For Timers it should be possible to set a range (e.g. 06.00 am till 09.00 am or from sunrise till 10.00 am)
  4. For Events it should be possible to use state conditions, were we have two types
    4.1 binary devices like switches, outlets, ā€¦ : when the device is on (or off) condition gets true
    4.1 multivalue devices like dimmers, thermostats, ā€¦ : when the device state is between a value range (dimmer: 20% to 80%, temperature: 75 degrees to 80 degrees)

With this kind of definition, I think, even the nontechnical user is able to define any situation when a specific scene should be activated whitout having too much redundancy in configuration. For better understanding I will outline a ā€œEvent-Timer-Scenarioā€:

WHEN
Group 1:

[ul][li]Timer (range 06:00 am - 09:00 am) AND[/li]
[li]Event (bathroom light turned on)[/li][/ul]

             OR

Group 2:

[ul][li]Timer (range 03:00 pm - 4:30 pm) AND[/li]
[li]Event (dining room light turned on)[/li][/ul]

WHAT
Action1:

[ul][li]turn coffeemachine on[/li][/ul]

In techical terms: the boolean condition expression would look like this:

(Timer >= 06:00 am AND Timer < 09:00 am AND bathroom light = ON) OR (Timer >= 03:00 pm AND Timer < 04:30 pm AND dining room light = ON)

I consider this functionality as breaktrough in the whole automation process, because now I am able to define any situation in my home when I want Vera to do things for me and my family (like brewing some tasty coffee :-*)

Comments, suggestions and discussion are highly appreciated.
Thank you for reading the whole bunch :wink: