I must be missing something. What I want to do is turn on the hallway light for 5 minutes if the garage door is opened, but ONLY at night. How do I detect night without setting something like a VirtualSwitch at sunset and resetting it at sunrise, and then using it as an AND condition? Unfortunately, no virtual switch available yet.
And, note also that sunset and sunrise do not work for me on the west coast - apparently a known problem in Atom v1 and EZLO Plus as well.
In recognition of the desire to distinguish/control between events that run by day vs. those that typically run at night (lighting, security, access, etc.), perhaps Ezlo could add a âNightâ trigger to the Schedule>Daily> option, much like âAt time of dayâ? Although it would be a state - between sunset and sunrise - rather than a transition like sunset, it would allow us to condition actions using the AND function to those we only want to occur at night. A similar extension of this concept would be to add a Time Window trigger in the Schedule>Daily option that would allow us to set the beginning and ending time that a trigger (state, actually) would allow us to restrict an action using the AND operator.
While on the subject of suggestions/enhancements, perhaps Ezlo could enhance the scene creation process to allow editing. I.e., having created a scene with two triggers using the AND function, adding some actions, and then saving, I decided that I didnât want one of the trigger conditions. However, I was unable to delete that condition without deleting the entire scene and rebuilding. Maybe I missed some button (iOS), but it would seem that some way to delete/edit a particular trigger and/or action without complete rebuild would be helpful.
The thing you are missing is the âGrouping of Activations eg Triggersâ
in your case you have two triggers
1-Door opening (A device State)
2-Night time (A Time State)
So you need to âGroup these two triggersâ so that it only triggers when both conditions are met:
Click on âAdd activation eventâ
then
Click on âA group of activation eventsâ as per below
then create two activation events and group them together using âANDâ
I did an example in the below screenshot where I took a device as a triggerâŠthen I took a time as a trigger and combined them with an âANDâ statement.
Now you can turn on your light after sunset if the garage door is openâŠ
For turning it off (pls look at my previous post âŠwhere you can use the âlightâ as the device triggerâŠif the Light is onâŠturn it off after a delay of 5 min).
Also for Time zone: pls go to âSettingsâ then âUnit Settingsâ and choose your locality.
Hope this help!
finally received the plus in the US. first impressions echo the above sentiments. Fast inclusion, fast on performing actions.
The VOI stuff is really powerful for integrating other systems that are not in the Ezlo/Vera. Iâm thinking through a lot of possibilities with that.
Like the new scene creation and being able to do AND/OR operations. Itâs OK that it walks you through very wizard-like for creating a scene, but i find that too limiting. i really like the way reactor allows you to create your entire set of conditions (activation events in the vera UI) on one page, so i can reference what else iâve already done in the logic.
I also wish that it was not a one to one condition to action, i would love to have one scene that controls a common set of elements. Again, drawing comparison to reactor, each group of conditions (activation events) can have an action. and these actions can be fired when the condition is met or when it goes false, so i donât have to create a second scene for a âoffâ condition. In Reactor, there is a concept of a NULL group that allows me to have separate logic in one single container. so in one location i can look at all the actions that are related to AC.
Only had it for about an hour, so i will play some more with it when i get some time.
Does anyone else find it strange that when initiating a scene that turns on a light, for example, the notification that gets sent is âScene finishedâ? Would think it might say something like âScene activatedâ or âScene initiatedâ, anything other than âfinishedâ.
From the Appâs perspectiveâŠit sent the commandâŠand the command is received by the controllerâŠso the app did its jobâŠdepending on the sceneâŠit might take X timeâŠ
happy to discuss wordings and new suggestionsâŠ
Btw: were you able to set the scene as per your requirement? if not, what were you not able to ?
I was using âSunsetâ to turn on a light. It worked â except that it occurred more than 3 hours before actual sunset on the West coast â due to the apparently known bug. But, I guess I think of scenes doing things that might continue for a while, not being âfinishedâ just when they are initiated or become active.
I understandâŠits a perspective issueâŠIf you look at it from âAppâs perspectiveâ it merely sends the instruction to Controller and then doneâŠIf you look at it from âControllerâs perspectiveâ a scene is in constant executionâŠwe are always open to find a happy medium for wording.
The user doesnât differentiate between the appâs perspective and the controllerâsâthey are one and the same to the user. The app is the UI of the controller, so âScene Finishedâ sends an odd message if the userâs scene will last some period of time. It seems that the app wants to indicate when it starts sending the commands to the controller, and provide an indication when it has finished. Perhaps instead of scene started and scene finished, simply report âCommands Sentâ when the app has transmitted all the controllerâs commands.
Indeed, the commands have been sent to the controller, but âCommands Sentâ is not very explanatory when it shows up as an email. To the user that gets the email, he is left to wonder just what action was effected with the commands. Much clearer, to me, to advise in email that âXYZ scene was initiatedâ or something like that. The user interacts with the UI through devices and scenes, not commands, so referencing the state/status of the scene seems clearer to me.