2. I'm running into a issue where IPs are changing on ASICs and the AM client doesn't update the current listing to reflect this. They can easily be found by scanning the network, but obviously not good. This is generally being caused by my router resetting then occasionally the miners resetting.
Could you add a Rule Action that runs a network scan and readds the miners replacing their original entry? They are uniquely identifiable at least by their MAC address.
a) A partial solution is to configure the DHCP lease time on your router to be much longer than the default. Set it to something like 10 years and it will not change IP address of a miner simply because it's down for a short while.
b) A more complete solution is to make use of a Remote Proxy that is responsible for an entire IP address range. Using the Automatic Discovery feature it will automatically find new miners and add them. You can also enable MAC address identification and it will keep track of MAC addresses to handle the case when an ASIC miner changes IP address. Awesome Miner will simply update the IP address of the existing External Miner entry to point to the new IP address.
See the article below and also the final section about MAC address identification.
https://support.awesomeminer.com/support/solutions/articles/35000085994-environment-setup-remote-proxy-for-distributing-load