strange behaviour, does not turn off , or even turns on instead

[Dakhaasje]

I have this system with automatic lights, based on PIR with RF and wall switches with RF .
Timers reset while PIR activity , and when time runs almost out, a warning light starts blinking. Then the lights go off.
That should be the case.
However, the timers do not always send the OFF command.
Sometimes they even send the ON command and not start the timer... so the lights stay on all night.
I am switching to wall light switches with Tasmota and RF soon because of this unreliability.
timersflowexample.json.txt

... edit: I discovered a typo in one of the PIR-RF received data-switches.

[linuxha]

Do you think it was the type that caused the error or do you still have the issue?

[Dakhaasje]

I think it was the reason of one PIR to not have a reaction. (the switch code was 5 digits instead of 6).
I replaced for the main living area all timers with eztimer modules.(left the surrounding structures mostly the same) Ok, they lack the warning. I solved that by delaying the off-command and a blink. So far no problem with eztimer...
But your timer works without issues in the bed- and bathroom. So I left those.
However the lights there work with Mqtt, not RF.
Today I received the new sonoff T2 wall switches, and flashed them.
They will be installed in the living area.

I think the reason the timer worked irregular is because of the use of RF together with coding on/off "0" / "1" instead of "on" and "off". Nodered (or I) seems to view them as number instead of string sometimes.
offtopic:
The Livolo/Sesoo RF wall switches are programmed with separate RF codes for on and off. I discovered today again that the Sonoffs do not support that... only codes for "toggle". So I cannot use a RF Pir to turn one on immediately. So the programming must be simple, to not make the reaction slow. I do not know which timer will be best then. I might try to let the wall switch itself run the timers.

[linuxha]

2.5 years no word, will close