1) Triggers are defined indpendelty.
But with "conditions" you could create a appeal, that the trigger does not fire or is ignored.
E.g. A LUX Sensor trigger a light scenes based on the light outside. But only between 17:00 & 20:00.
This would prevent that the scenes fires in the morning, when its cloudy and the values jumps/jitter.
2) Currently the makro "command" does execute each command regardless if the previous command is done.
(resolve() outside the commad handler callback): https://github.com/OpenHausIO/backend/blob/dbf499ec68eb4ab7d4204ab21efea51133fe824c/components/scenes/makro-types.js#L40
This can be a problem when one command dependet on the other command successful execution.
But its not needed to wait for the previous command when, diffrent lights are turned on. Why wait for a light to turn on to turn another one on?
So there should be a option where you specify if it should execute them "simultaneous" or in a synchronous way.
Add the following properties:
1) Triggers are defined indpendelty. But with "conditions" you could create a appeal, that the trigger does not fire or is ignored. E.g. A LUX Sensor trigger a light scenes based on the light outside. But only between 17:00 & 20:00. This would prevent that the scenes fires in the morning, when its cloudy and the values jumps/jitter.
2) Currently the makro "command" does execute each command regardless if the previous command is done. (
resolve()
outside the commad handler callback): https://github.com/OpenHausIO/backend/blob/dbf499ec68eb4ab7d4204ab21efea51133fe824c/components/scenes/makro-types.js#L40 This can be a problem when one command dependet on the other command successful execution. But its not needed to wait for the previous command when, diffrent lights are turned on. Why wait for a light to turn on to turn another one on? So there should be a option where you specify if it should execute them "simultaneous" or in a synchronous way.