Scenes capabilities for the new Ezlo Platform

Hi,

How would you like to interact with this functionality? Please expand as much as possible, and give us use-cases for this functionality.

@Ioana

It should be obvious. Cases, being able to communicte with on line api’s some will only accept post request in json. so the ability to choose how to submit http request would be useful.This use would be useful for beginners who can not code. Communicate with http devices ie tasmote and espeasy,etc

interact
drop down list to select protocol and an input field that accepts json format or form url

It may also be useful to have the ability to select if you want scenes to wait for a response from api and device requests before moving on.

1 Like

Hello @vezinpi
Thank you for your input. It is not a negative feedback what you just said :slight_smile: We are already focused as you also proposed both on PLEG and Reactor. If you want to add more you can always repost here or PM me (which ever is easier for you.)

Thanks
Mehmet

1 Like

Integration with Honeywell thermostats is also beautiful. Now a plug-in is used, but this is not stable

1 Like

Mostly for notifications, but one example is to have a virtual switch turn to ON for visualisation on a control panel that something has happened/is not resolved?

1 Like

Look at Microsoft Power Automate for inspiration.

1 Like

I would really like to see a secure RESTFUL api with a secure token. Where I can interact with the state of devices from another device that may use GET and POST messages. I would like to be able to read the state of devices managed by the hub and even be able to change the state of the device.

Having a secure api token that the device generated would keep this interaction secure. This would really open the door for cross interaction with devices like raspberry pi, arduino and esp8266 based projects.

Paul.

Also please don’t remove the ability to do some custom programming with lua or something similar. Plugins and components never fully cover what a programming language can.

Also if you can improve the work flow for programming and debugging, that would be great, currently development is really clunky and slow.

1 Like

Just please ignore the UI/UX implementation of PLEG, it can make a seasoned IT professional run screaming for his cuddly penguin!

Reactor and Node-Red are much better examples of implementing scene logic in a user-friendly way.

2 Likes

Yes I agree other controllers like Zipato and Fibaro have a blocky UI for creating logic. Similar to Reactor for Vera I believe although I’ve not used Reactor.

PLEG is powerful but has a learning curve.

1 Like

Reactor is powerful AND user friendly.

4 Likes

I’m sure it is. I’ve used PLEG for years and felt no need to change all my logic to Reactor.

Hopefully Vera’s new native logic engine will mean we don’t need either 3rd party plugin.

This is the real goal. When I first offered Reactor, it was because of Vera’s enduring lack of better triggering for scenes. There were other reasons, but this is not the place for an app comparison. But I was plain at that time with my feeling that it would be a good day when these products were not necessary.

I will add that I am quite pleased to find the beginnings of such functionality in Vera’s new scene model–the bones are there. I have questions about the complexity of it, but that’s not my problem directly, or yours; the onus is on them to make it work and be efficient and sufficient. But there’s a good chance that Reactor, PLEG or Rules Engine will never make it to the new firmware, simply because eZLO has finally addressed the need itself.

Edit: For clarity, I am prepared for any necessary response to the outcome.

5 Likes

I’m not sure if this is a bug or limitation of the the Edge Linux scenes engine. Anyway, I can’t add a second action to a scene, when I hit the plus it just edits the existing action.

1 Like

Hello, in the current implementation for Ezlo VOI™ you need to add Alexa/Google device as one action and the other device(s) as a separate action with a delay.

For example you can have:
Immediately Send voice command: turn off lounge room Blinds
Wait for 5s and then Lamp module 50% on

1 Like

I second Ravenshill

“please don’t remove the ability to do some custom programming with lua or something similar. Plugins and components never fully cover what a programming language can.”

1 Like

Makes sense, thanks.

1 Like

Some of my scenes:

  • On motion detection STOP (no more motion detected), start 30 second timer. If motion detected again before timer expires, cancel timer. If timer expires, turn off light.

  • If bath light turned on or motion detected in living room, run actions - BUT ONLY: between the hours of 5 and 6 am weekdays, or 6 and 7:30 am weekends, and ONLY RUN ONCE (if motion is detected again later, do not run the scene again)

  • When garage door opens, turn on garage lights. If “is night”, ALSO turn on outside lights.

I also have a bunch of scheduling type scenes (on at dusk, off at dawn type), as well as more basic action/reaction (when I arm the security system, lock the doors and turn off the lights).

Note that most of my sensors (motion and door) are on my security system (DSC with EnvisaLink EVL3 interface), so support for that in some fashion (plugin is fine) is VITAL to my being able to move to the new platform.

Thank you guys for all your hard work - eagerly looking forward to the full release of the new platform!

2 Likes

Any chance of seeing a layout of the new rules/scene before i get the ezlo units?

I hope it will follow the path layed out with reactor, it’s come to a point where i can’t really se what you can’t do with it! All functionality of the old slowmoving scenes to a full state machine.

The fact that they act as “security sensors” is very handy as well, but if they are separated (like scenes in the old UI7) this can be done by virtual devices.

2 Likes