Maybe the case but the same thing happens when the status changes from OFF to ON. I fixed the problem in the meantime by manually rewriting the rule directly in the Nano editor. Having done that, I do not get any parsing warnings anymore with exactly the same rule code. However, the rule now get triggered. Strange…