Problema with backlog being interrupted with any other command

[Héctor Rguez.]

Hi;

I'm using Tasmota 8.1.0 with a Sonoff TH 10 to control a resistance in a Solar system to heat water and a normal Sonoff to manage a recirculation pump.

I use backlog command for security to prevent problems with the programming that could let the pump or the resistant always on, so usually, when I want to activate the recirculation pump I send a

backlog power on;delay 600;power off

And similar with the resistance. I calculate the time needed to put the water at the desired temperature and divide between the max time the delay command accept, 6 minutes. I've calculated that I need 7 minutes to elevate 1 grade the water temperature.

The problem I see is: If I send any command like a status to the Sonoff in the time the delay is running, the delay is terminated suddenly and the last command, the power off is executed.

In the instructions it is said that another backlog command can abort the first one, but not any other command.

There is any way to this not occur and the delay will end normally independent of another commands send to the Sonoff?

Thanks in advance.

[Michael Ingraham]

The problem, perhaps, may be with the Delay command. Since 'Delay' is expected to be used only with 'Backlog' commands, the code may not be written to expect any commands from being executed otherwise. To confirm this, you probably need to visit the Tasmota Discord chat to inquire of the admins whether they have experienced the Delay command being terminated by any subsequent command.

Having said that, you may want to use 'PulseTime<x>' instead. You set the PulseTime value and then turn the output on. It will then automatically turn off after the time you set. You only need to execute the 'PulseTime<x>' command once while your desired duration does not change. In other words, if you calculate a different value, then invoke the PulseTime command to update it. Otherwise, it remains set even across reboots. Once set, you only need to invoke 'Power<x> 1'.

[Héctor Rguez.]

Hi;

Good clue!

I didn't know the pulsetime option. I think I viewed time ago but think that cannot use it during too much time as I need. Now I see that above 100 the time is measure in seconds instead of 0,1 seconds, so it is perfect for my needs.

Thank you very much !