Hmm, a redirect. What will be a bit different from “native” OH2 rule to OH3 rule running under a DSL interpreter of the new rule engine … is the context.
Pipes and so on are often problematic with executeCommandLine, because it does not run in a shell context.
I believe the exec code does some uhh kludges to try and work with simulating pipes by itself, maybe this is where the “array” comes in.
This is not the same, but feels similar. I have no knowledge to look deeper or experiment, but would at least try without the redirect.