I have quite a few Fibaro roller shutter and dimmer devices.
They have built in scene controller functions to trigger actions on double / tripple click of the right paddle on the dimmer modules or double / triple click on up/down paddles on the roller shutter modules.
I used to handle this in PLEG and I am in the process of translating that to workflows.
I setup one workflow for a roller shutter module (see attached).
I wonder what would be a best practice approach to configure that kind of workflow.
I am asking because I will have to duplicate my template quite a few times and want to be sure it is done in the most efficient way possible (in terms of required processing time).
The workflow is working fine, only the time lag is bothering me (3 to 10s from click event).
With ten or more of these workflows, will the lag I see right now even increase?
With the few workflows I have right now I see a cpu usage of 3 to 10% on a PI3.
[quote=“pls90, post:1, topic:193340”]I have quite a few Fibaro roller shutter and dimmer devices.
They have built in scene controller functions to trigger actions on double / tripple click of the right paddle on the dimmer modules or double / triple click on up/down paddles on the roller shutter modules.
I used to handle this in PLEG and I am in the process of translating that to workflows.
I setup one workflow for a roller shutter module (see attached).
I wonder what would be a best practice approach to configure that kind of workflow.
I am asking because I will have to duplicate my template quite a few times and want to be sure it is done in the most efficient way possible (in terms of required processing time).
The workflow is working fine, only the time lag is bothering me (3 to 10s from click event).
With ten or more of these workflows, will the lag I see right now even increase?
With the few workflows I have right now I see a cpu usage of 3 to 10% on a PI3.[/quote]
there is only one page in the PDF, I cannot see the workflow fully
oh, I am sorry. 2nd try.