Hi,
Want to share some ideas based on my experience with ewelink
eWelink CAST - Suggestions
possibility of slide between different casts without the need of go back to choose one cast
Sunset and sunrise widget, similar to weather
NSPanel and TX2/3 possibility to show independent channels in ewelink cast
Possibility of change background images
tail of last 20 Scenes logs, for example
SONOFF devices
NSPANEL
decimal are needed to temperature and RH
on/off button needed for the automatic thermostat
possibility to show independent channels in ewelink app
more background images, like kitchen and attic
possibility to setup on widgets of the NSPanel channels of another NSPanel
DOOR/WINDOWS SENSOR
Possibility to setup a scene to alert if a door or window is open more then X time
EWELINK APP
possibility to use filter to search on the scene logs, one idea is to give an unique Id to scenes
On scenes should be permitted to set, for example, to turn ON on sunset and turn OFF on a specific hour, for example 23:00
OTHER SUGGESTIONS
zigbee rain sensor
zigbee lux sensor
For example I have a VELUX with a zigbee window sensor, and I would like to be notified if it start rain (zigbee rain sensor) and I also want to turn the light if not enough clarity, same that happens on cars (zigbee lux sensor).
Thanks Guys, keep the good work, and I’m expecting that some of my suggestions will be applied
If you are in a hurry with this functionality, you can achieve it using https://sequematic.com
This could be achieved, for example, by creating a scene on the ewelink side. Every time the sensor is activated, it sends a webhook call.
On the SM side, count the number of times using a variable and react accordingly.
This requires adaptation to a specific solution. When to count, how much to count, how to reset a variable value and when.
In this model, we can count how many times the sensor is activated. When the desired value is reached, the preferred action will be performed and at the same time the variable value will be changed to 0 to be ready for the next counting to 3.
You shouldn’t have /DOOR/R1/ Unless that’s your version of censorship.
R1 is the name of the variable where the values go. Of course, you can choose any name you want. I take it you created a variable?
You’re trying to do the same thing twice.
Stopping here makes little sense imho… What is the purpose of this minute?
My humble opinion would be that it is always good to start with simple logic and more sequences to make the diagram more understandable. And as we gain practice, we can move towards more complex and uniform sequences.
The original example I showed does exactly what you wanted. Counts the number of times the door has been opened.
The opening time counting can theoretically be included in another sequence.
I would do it a little differently. Two main sequences and two variables. One counts quantity and the other counts time.
I don’t fully understand your model… Should the number of door openings be a separate alarm and the opening time a separate one, or should both values be met?
Let’s separate the two issues. First, let’s check the number of times the door is opened.
For this purpose, ewelink must send a webhook with +1 information every time the door is opened, but do not use -1 because we do not subtract anything here.
Then, on the SM side, the “Number_of_Door_Openings” variable is increased from 0 to 10, in this way the openings are counted, when it reaches 10 it will perform an action (email) and reset the state from 10 to 0 and will wait for another +1.
Very simple counting of the number of door openings and reacting to them when the assumed number is reached.
The second issue is the door opening time.
For this purpose we use the “Door_Position” variable. On the ewelink side, we send the appropriate webhook depending on the sensor status. Open and Closed… the Open value initiates a one-minute countdown and if the sequence is not stopped by changing the value in “Door_Position” it will execute the action (email).
Make an exact copy of my example and continue from here…
