I have 3-state workflow, cycling round to run my boiler config every minute, and then check it has run. I have noticed several strange things about it - initially that I had some log entries that the timer was being ignored, not a major concern in itself but nothing else can change the state.
luup_log:128: ALTUI: warning: Wkflow - Timer - Timer ignored, active state is different from the timer state <0x756eb520>
I then noticed that the timers are cycling round twice as fast as they should so that my boiler update is called two times every minute, and in the “history” some get labelled with just “name”, some as “timer:name”. I have replaced the timer transitions with identical 20s timers (clones), but get the same problem.
Anyone else seen this effect?
(The workflow cycles round the 3 states, checking for an error, waits for 20s and sets a virtual switch as a heartbeat monitor, waits 20s, runs the boiler update… clearing the switch, then waits another 20s and repeats the process. [If the switch has not been cleared then an error is flagged, but that looks ok] However, some of the timers are firing immediately rather than waiting 20s, doubling the overall rate)