question, or maybe a suggestion
Is it possible in the rules to set some trigger for a rig A, but the action (like a start/stop miner command) is for another rig B? Or maybe multiple rigs B, C, D, .....?
If this is not possible right now, it would be awesome if you could do that.
Can you give an example of when this might be useful? This would be of help for me to understand what's missing today. Thanks!
Hey Patrik,
here are two examples for my own benefit.
I have a few watercooled rigs with 2 seperated rigs in 1 water-loop. If for whatever reason the main-rig turns off, there is no waterflow anymore and I have to shutdown the second rig too. Right now that shutdown is managed by a smart socket, but if AM could handle that with just a rule and much faster, it would be awesome.
I also have multiple containers, running each 4 rigs inside, but with just 1 power line per container. If the main-rig including the power for the containers airflow turns off, I have to shut down the other 3 rigs to protect them of overheating. AM could handle that even faster than any smart socket.
I think this option can be useful for other miners too, to protect rigs in a better way without using external stuff like smart sockets or so. How could this be done? One idea would be in the rules -> actions -> "miner command" for example another line which is already set to "this miner/group", but I also can choose other miners or groups. But maybe you will find a better way like always