Yes, that was how I did it originally. I only changed to the current version when I started experiencing issues. Here is the original piston.
It seems my issues are related to hub delays. The recent change suggested by WCmore had had a positive effect. I can still see additional event sequences in the log, but now they don’t cause a problem. In other words I have a workaround, not a fix.
An update to say the last changes fixed my issues. Of all the changes the one that did the trick was to increase the auto-off timer within the module to one minute. Now when there are delays that would have caused a second ‘on’ of the action, the switch is already on so there is no effect. At the end of the timer the switch turns off and my curtain motor is triggered.
All good in the end and thanks for the help.
