Hi Patrike,
I have a couple questions / suggestions.
1. It would be awesome if you could add the ability for Rules to trigger other Rules. For example, if the temperature of (X set of Antminer S9's Miners) exceeds X, then trigger other Rule/s. The other Rule could lower the OC value of the Antminer L3's sitting next to the S9's, lowering the temp of the affected area. There are so many other valuable options that could be created if Rules could trigger other Rules.
2. Is there a way, or can you add a way to natively enable extranonce subscribe (#xnsub) to AM's multipools? I've tried several variations on the "Online Services" panel, and they end up with the URL of the pool breaking. Instead of the Algo's Port # being added to the end of the pool, it adds a -1. See below for pictures.

Thank you!
1) Thanks for your suggestions on this. It's an interesting concept. I assume the main reason is that you want this to not have to define the same actions in many rules. Where you also thinking that if the other rule to execute is selected to run only on specific miners, it will be applied for those specific miners when executed? So the first rule might perform action on Miner#1 and then execute another rule that might be specified to execute only on "Miner#2 and Miner#3" - or should it be configurable that the other rule also should execute on the original Miner#1?
2) Antminers only allows the #xnsub to be specified as part of the default pools (toolbar: Tools -> Antminer -> Default Pools). It's being ignored by the Antminer when you send it via Change/Add Pool operations.