Oh wow,
Thanks so much, both of you @mischmi and @Wolfgang_S!
This has really made my day, as I was stuck on this topic for about two months now.
For those who may have a similair problem as I did: I needed this kind of rule, to peridocally disable and reenable a Homematic CCU2 thing. I know it’s a sloppy workaround but that’s what I had been doing manually for weeks, at least now its automated. The problem itself is (partly) described here:
Since the update to OH 3.1, some things discovered by the CCU showed the described config errors, as if the CCU was offline, although it wasn’t. Also some things stopped updating their states reliably and at random times. E.g. A Thermostat would randomly stop reporting the actual temperature and a door/window contact wouldn’t update its state. That’s quite annoying as it “breaks” persistence based rules and proper graphing, of course.
To be fair, in the above thread there is also a solution posted by he developer of the binding, involving manual installation of an not yet official version of the homematic binding, I think. Being relatively inexperienced, I opted for this workaround with the rules, and maybe waiting for an official update of the binding. I realize that updating the binding is the cleaner way but I’m a little afraid to use inofficial versions yet.
I hope it’s ok to post this workaround in this thread too, as I had a pretty hard time getting here (with an awful lot of googling). Maybe someone will find the same solution useful.
Cheers!