@ DankNetCode (bitcointalk)
Tried to PM this to you, but my account is too newb to get it through.  I guess this isn't entirely a hi-jacking since it's somewhat NM related.

Put this into the arguments line of each ps1 miner file you use in the "miners" folder in nemos:

"-b 0.0.0.0:4068" (without the quotes)

I'm not sure why the --api remote argument doesn't work.  I think it might work if you were running AM locally on your mining rig since it defaults to a loopback IP (127.0.0.1).  I'm sure there's a way to get it to work using additional arguemtns, but the above argument worked for me right out of the gate so I just stuck with it.  

Depending on what firewall and OS you're running, the first time each miner runs, you'll likely be prompted to acknowledge the firewall exceptions.  Certainly happens on my W10, Windows defender rig.

Cheers.

J.


While I've got your attention, I was wondering if you'd consider disabling the "quickedit" property for the miner CMD window (unless of course you have a reason for it to be on).  I think a lot of the issues you may be hearing about along the lines of "NM not changing algo after interval/sleep time," "benchmark won't stop," and maybe even some "pool stats frozen" are people inadvertently left clicking in the stats window, not realizing it that it's stopping the NM script from doing it's thing.

If not for anything else, consider doing it for people like me who are fumbling with their phones trying to monitor their rigs via Teamviewer and fat fingering the left click by accident.