Page 1 of 1

Max Value for Command GPIO: Pulse,<GPIO>,<value>

Posted: 09 Aug 2019, 14:31
by alwashe
what ist the max value for Pulse?

When I use 3999ms as value it works and I get a log entry.
But when I use 4000ms as value it works but I don't get a log entry.
Why?

[edit]
ok I think I found the answer: https://espeasy.readthedocs.io/en/lates ... e#commands

before I just knew this site: https://www.letscontrolit.com/wiki/index.php/GPIO

Re: Max Value for Command GPIO: Pulse,<GPIO>,<value>

Posted: 09 Aug 2019, 20:56
by ThomasB
Sounds like you found the solution. An important thing to note here is that the Pulse rule command is a blocking event. The P001 plugin uses the delay() function for this action, so nothing else can occur while the pulse is active. That is why you must avoid it on long time periods because important scheduled system events will be adversely delayed and/or lost.

The LongPulse and LongPulse_ms commands don't block (they use the PluginTaskTimer instead of a hard delay). So use these commands instead in your long duration pulse rules.

- Thomas

Re: Max Value for Command GPIO: Pulse,<GPIO>,<value>

Posted: 10 Aug 2019, 12:31
by alwashe
Thank you very much for that info.