This is a long standing bug, I reported it back in April 2019 on v5.2.22…
The only way to get around it is to create separate Print Jobs for each terminal then trigger then separately in rules. You can simplify the amount of actions you need to create by just passing the terminal name as a parameter, but this is still the only way I could get it to work per terminal in a reliable way.
That’s interesting, its definitely not something I have tried. However the problem still exists as this is still just a workaround, * should work for terminals the same way it does for anything else but doesn’t.