[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[puwaha]

I setup something neat last night using AM and thought I'd share it with you all here.

I bought an ASIC that crashes every 30 minutes or so.  I'm still working with the seller to get it replaced, and he is very adamant about getting it working, sending me new components, and has even offered to send me a refund for the days it hasn't been mining.  Great guy, I'll post about the experience later when it's all settled.

Anyway... so the ASIC runs for 30 minutes at a pop and requires a reboot to get going again.  I had a Wemo Insight smart plug that has some basic "turn on" and "turn off" applets at IFTTT.  There is also an applet where you email IFTTT's email address with some hash tag in the subject line, it will trigger the applet.  Light bulbs went off, and I realized I can use AM to track the ASIC and send an email to IFTTT to trigger the turn off and turn on Wemo applet.

So, in IFTTT, I setup two applets with one where the "if this" trigger is the mail applet with a hash tag of "#off" in the subject line... to perform the "then this" action to turn off the Wemo smart plug.  I then setup the second applet to do nearly the same thing but look for a hash tag of "#on" in the subject line to perform the "then this" action to turn on the Wemo smart plug.

Then I go into AM's rules and setup a user rule.  I setup the trigger to ping the IP address of the ASIC and if hasn't responded in 9 seconds to do the action.  The action section is a small set functions in AM that run in sequence.  The first action is to send an email to the IFTTT email address with a "#off" in the subject line.  Then I put a Wait action for 10 seconds.  Then put another email action to send an email to the IFTTT email address with a "#on" in the subject line.  Finally, I put 6 individual wait actions for 60 seconds each.  It basically runs like this:

If no response from IP address for 9 seconds then
    Send and email with #off
    wait 10 seconds
    send another email with #on
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds

I needed to put the waits in there at the end of the script because it takes a minute or two or three for the ASIC to fully power on and start responding to pings.  Otherwise, every 9 seconds without a ping response would cause AM to trigger again, turning off the smart plug and back on again.

This opens up a whole new realm of possibilities with using Awesome Miner and smart devices using IFTTT.  I have had a few problematic GPU rigs in the past that would hard-lock up and the only way to get them going again was to power cycle them.  I have a Raspberry Pi with some relays setup on the power switch pins to do just that.  There is some code that I modified to trigger the relays with a momentarily close the relay to "hold down power for 6 seconds" action and then wait 5 seconds, then momentarily close the relay for a half second to power on.  It works mostly the same way as the AM/IFTTT/Wemo setup works above.  If it doesn't receive a response from the rig by pinging every 30 minutes, then it assumes it's down and does the power cycle sequence.  It doesn't always work correctly, because sometimes the rig will hard-lock, but still respond to pings!

The AM/IFTTT/Wemo setup is a million times easier to setup, and incredibly more flexible.  It would be simple for anyone to use something similar to monitor their rigs for hard lockups.  You don't have to just limit it to ping replies in AM, you could have dead device, offline, submitted shares, or hashrate thresholds as a trigger.  AM makes this easy.

Suffice it to say, I'll be getting a few more Wemo smart plugs so that AM can monitor all my rigs and take appropriate action.  There's not a worse feeling when you are out of town, look at your AM web page and see a rig that is down... and you won't be back to take any action for a few days.  This also opens up easy automation opportunities for mining rigs you may have at another site.

[cashen]

I setup something neat last night using AM and thought I'd share it with you all here.

I bought an ASIC that crashes every 30 minutes or so.  I'm still working with the seller to get it replaced, and he is very adamant about getting it working, sending me new components, and has even offered to send me a refund for the days it hasn't been mining.  Great guy, I'll post about the experience later when it's all settled.

Anyway... so the ASIC runs for 30 minutes at a pop and requires a reboot to get going again.  I had a Wemo Insight smart plug that has some basic "turn on" and "turn off" applets at IFTTT.  There is also an applet where you email IFTTT's email address with some hash tag in the subject line, it will trigger the applet.  Light bulbs went off, and I realized I can use AM to track the ASIC and send an email to IFTTT to trigger the turn off and turn on Wemo applet.

So, in IFTTT, I setup two applets with one where the "if this" trigger is the mail applet with a hash tag of "#off" in the subject line... to perform the "then this" action to turn off the Wemo smart plug.  I then setup the second applet to do nearly the same thing but look for a hash tag of "#on" in the subject line to perform the "then this" action to turn on the Wemo smart plug.

Then I go into AM's rules and setup a user rule.  I setup the trigger to ping the IP address of the ASIC and if hasn't responded in 9 seconds to do the action.  The action section is a small set functions in AM that run in sequence.  The first action is to send an email to the IFTTT email address with a "#off" in the subject line.  Then I put a Wait action for 10 seconds.  Then put another email action to send an email to the IFTTT email address with a "#on" in the subject line.  Finally, I put 6 individual wait actions for 60 seconds each.  It basically runs like this:

If no response from IP address for 9 seconds then
    Send and email with #off
    wait 10 seconds
    send another email with #on
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds

I needed to put the waits in there at the end of the script because it takes a minute or two or three for the ASIC to fully power on and start responding to pings.  Otherwise, every 9 seconds without a ping response would cause AM to trigger again, turning off the smart plug and back on again.

This opens up a whole new realm of possibilities with using Awesome Miner and smart devices using IFTTT.  I have had a few problematic GPU rigs in the past that would hard-lock up and the only way to get them going again was to power cycle them.  I have a Raspberry Pi with some relays setup on the power switch pins to do just that.  There is some code that I modified to trigger the relays with a momentarily close the relay to "hold down power for 6 seconds" action and then wait 5 seconds, then momentarily close the relay for a half second to power on.  It works mostly the same way as the AM/IFTTT/Wemo setup works above.  If it doesn't receive a response from the rig by pinging every 30 minutes, then it assumes it's down and does the power cycle sequence.  It doesn't always work correctly, because sometimes the rig will hard-lock, but still respond to pings!

The AM/IFTTT/Wemo setup is a million times easier to setup, and incredibly more flexible.  It would be simple for anyone to use something similar to monitor their rigs for hard lockups.  You don't have to just limit it to ping replies in AM, you could have dead device, offline, submitted shares, or hashrate thresholds as a trigger.  AM makes this easy.

Suffice it to say, I'll be getting a few more Wemo smart plugs so that AM can monitor all my rigs and take appropriate action.  There's not a worse feeling when you are out of town, look at your AM web page and see a rig that is down... and you won't be back to take any action for a few days.  This also opens up easy automation opportunities for mining rigs you may have at another site.

This is awesome.

I just bought APC switched PDUs. I bet I could setup something very similar.

[yhbae]

I setup something neat last night using AM and thought I'd share it with you all here.

I bought an ASIC that crashes every 30 minutes or so.  I'm still working with the seller to get it replaced, and he is very adamant about getting it working, sending me new components, and has even offered to send me a refund for the days it hasn't been mining.  Great guy, I'll post about the experience later when it's all settled.

Anyway... so the ASIC runs for 30 minutes at a pop and requires a reboot to get going again.  I had a Wemo Insight smart plug that has some basic "turn on" and "turn off" applets at IFTTT.  There is also an applet where you email IFTTT's email address with some hash tag in the subject line, it will trigger the applet.  Light bulbs went off, and I realized I can use AM to track the ASIC and send an email to IFTTT to trigger the turn off and turn on Wemo applet.

So, in IFTTT, I setup two applets with one where the "if this" trigger is the mail applet with a hash tag of "#off" in the subject line... to perform the "then this" action to turn off the Wemo smart plug.  I then setup the second applet to do nearly the same thing but look for a hash tag of "#on" in the subject line to perform the "then this" action to turn on the Wemo smart plug.

Then I go into AM's rules and setup a user rule.  I setup the trigger to ping the IP address of the ASIC and if hasn't responded in 9 seconds to do the action.  The action section is a small set functions in AM that run in sequence.  The first action is to send an email to the IFTTT email address with a "#off" in the subject line.  Then I put a Wait action for 10 seconds.  Then put another email action to send an email to the IFTTT email address with a "#on" in the subject line.  Finally, I put 6 individual wait actions for 60 seconds each.  It basically runs like this:

If no response from IP address for 9 seconds then
    Send and email with #off
    wait 10 seconds
    send another email with #on
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds
    wait for 60 seconds

I needed to put the waits in there at the end of the script because it takes a minute or two or three for the ASIC to fully power on and start responding to pings.  Otherwise, every 9 seconds without a ping response would cause AM to trigger again, turning off the smart plug and back on again.

This opens up a whole new realm of possibilities with using Awesome Miner and smart devices using IFTTT.  I have had a few problematic GPU rigs in the past that would hard-lock up and the only way to get them going again was to power cycle them.  I have a Raspberry Pi with some relays setup on the power switch pins to do just that.  There is some code that I modified to trigger the relays with a momentarily close the relay to "hold down power for 6 seconds" action and then wait 5 seconds, then momentarily close the relay for a half second to power on.  It works mostly the same way as the AM/IFTTT/Wemo setup works above.  If it doesn't receive a response from the rig by pinging every 30 minutes, then it assumes it's down and does the power cycle sequence.  It doesn't always work correctly, because sometimes the rig will hard-lock, but still respond to pings!

The AM/IFTTT/Wemo setup is a million times easier to setup, and incredibly more flexible.  It would be simple for anyone to use something similar to monitor their rigs for hard lockups.  You don't have to just limit it to ping replies in AM, you could have dead device, offline, submitted shares, or hashrate thresholds as a trigger.  AM makes this easy.

Suffice it to say, I'll be getting a few more Wemo smart plugs so that AM can monitor all my rigs and take appropriate action.  There's not a worse feeling when you are out of town, look at your AM web page and see a rig that is down... and you won't be back to take any action for a few days.  This also opens up easy automation opportunities for mining rigs you may have at another site.

Interesting... I made an order for one of these plug as well to try out the concept you outlined above. The only issue I read with this approach is that another source tells me that IFTTT takes an hour to propagate the signal to the plug, which is kinda slow (although better than nothing I suppose).

So was this not the case for you? How long does it take for the plug to "react"?

I currently use TP-Link's smart plugs (HS110) for my rigs and it too can measure the power consumption and it is very reliable, but  I couldn't find any ways to use IFTTT to reboot the rig when the overall power consumption dips below certain level. It simply doesn't exist.

[yhbae]

For NiceHash, it appears to be fairly accurate - within 95% range.

But for AHashPool and HashRefinary, they are still wildly off. Of course, not the fault of AM but still, that's what you get. I haven't even tried the ZPool yet due to it having somewhat worse reputation than the others supported by AM but I'm going to try that out within few days.

I'm trying to figure out the right % for each pool so that I can more realistically do profit switching across different pools. For now, I'm sticking to one pool at a time and figuring out what this % should be.

Without the right %, pool switching is pretty much useless - 90% of the time it will be AHashPool, 8% HashRefinery then 2% for the rest.

In my tests, these are the numbers I found:


Nicehash: 98%
MiningPoolHub: around 98%, probably a bit more
Ahashpool: about 68%
Hashrefinery: about 75%
Zpool: less than 60% of what they actually publish

So far, my numbers are not far off from yours.

For MPH, is that number based on BTC auto-exchange or are you mining a specific coin and receive only that coin?

Thanks.

[ydem]

In my experience LUX gives farrrr less than the estimates of any mining calc.

You are totally WRONG!

Open aHashPool website an you will see 3000 miners on phi right now.

On my statistics last night phi was the most profitable for 80% of the time.

Every AM user that did not had phi algo mining just lost more than 20% because of your ignorance and lack of research.

I advise you to add the missing coins and algos.

I do think that it is not fair to make users of AM loose thousands  of dollars every hour because of your ignorance of not having all algorithms added in managed profit miner. I added myself and earning a lot more than everybody else that do not have all coins by default.

Who thinks like me that it is better to have all coins added by default in the next release and some new pools besides the few ones that are overloaded and not responding that we have now ?

Totally agree with your statement, please add the missing algo PHI, for now i call this app 'Almost Awesome Miner', keep it awesome

[wtfonly16]

doesnt let u add miners with diff ports wtf....

192.168.1.129:1337 is ip and doesnt work... i change api to 3333 and it works... completly ignores port

the fuck is this shit?

[puwaha]

Interesting... I made an order for one of these plug as well to try out the concept you outlined above. The only issue I read with this approach is that another source tells me that IFTTT takes an hour to propagate the signal to the plug, which is kinda slow (although better than nothing I suppose).

So was this not the case for you? How long does it take for the plug to "react"?

Within seconds for me.  When I set it up in the first pass... I used the Wemo off/on applet with no waits in AM and I would watch the Wemo smart plug go off and on over and over because the rig is not going to respond to pings immediately.

I currently use TP-Link's smart plugs (HS110) for my rigs and it too can measure the power consumption and it is very reliable, but  I couldn't find any ways to use IFTTT to reboot the rig when the overall power consumption dips below certain level. It simply doesn't exist.

You could potentially write your own applet, but that may be more effort than required.  I think if you use AM's triggers on dead device, offline, or no accepted in X minutes it would do essentially the same thing.  If you wanted to get really fancy, there is an applet in IFTTT for the Wemo insight to track switch usage in a Google spreadsheet.  Then setup applets to monitor that spreadsheet and take action.

[puwaha]

doesnt let u add miners with diff ports wtf....

192.168.1.129:1337 is ip and doesnt work... i change api to 3333 and it works... completly ignores port

the fuck is this shit?

I'm assuming you are trying to setup mining software that doesn't come out of the box with AM?  What software is it?  Did you set it up as Managed Software in AM so that AM knows how to interface with it? 

[wtfonly16]

doesnt let u add miners with diff ports wtf....

192.168.1.129:1337 is ip and doesnt work... i change api to 3333 and it works... completly ignores port

the fuck is this shit?

I'm assuming you are trying to setup mining software that doesn't come out of the box with AM?  What software is it?  Did you set it up as Managed Software in AM so that AM knows how to interface with it? 

its claymore eth miner..... because im using diff remote management port thats not the default 3333, awesome miner doesnt detect it.
i can pull api from it using ethman just fine....

[puwaha]

doesnt let u add miners with diff ports wtf....

192.168.1.129:1337 is ip and doesnt work... i change api to 3333 and it works... completly ignores port

the fuck is this shit?

I'm assuming you are trying to setup mining software that doesn't come out of the box with AM?  What software is it?  Did you set it up as Managed Software in AM so that AM knows how to interface with it? 

its claymore eth miner..... because im using diff remote management port thats not the default 3333, awesome miner doesnt detect it.
i can pull api from it using ethman just fine....

Is it a different version than the one that came out of the box with AM?  If it's the same one, then you don't need to specify an API port, AM already knows how to do it.  It will be added automatically to the command line when it's issued to your rig.

If it's a different version, then you should tell AM about it as a new Managed Software entry.  Then in the entry, you tell AM that it's Claymore dual miner compatible, and it knows then what command line entry to add it's own API statement.

[trolling]

Hello,
Running v4.3.3.  Menu tab indicates a new version available to download, but the update crashes.  Log file suggests failure to download required files from website.  Any ideas?


/20/2018 7:43:19 PM.208 [001] Updating wallet statistics
1/20/2018 7:43:19 PM.401 [022] Checking for updates: Release URL: http://www.awesomeminer.com/download/setup/ReleaseInfo.xml, Dev URL: http://www.awesomeminer.com/download/setupdev/ReleaseInfo.xml
1/20/2018 7:43:19 PM.765 [022] Current Version: 4.3.3
1/20/2018 7:43:19 PM.765 [022] New Version: 4.3.2.0
1/20/2018 7:43:19 PM.765 [022] Requires Version: 0.1.4.0
1/20/2018 7:43:19 PM.930 [022] Current Version: 4.3.3
1/20/2018 7:43:19 PM.930 [022] New Version: 4.3.4.0
1/20/2018 7:43:19 PM.930 [022] Requires Version: 0.1.4.0
1/20/2018 7:43:19 PM.930 [022] Development version update available: 4.3.4.0
1/20/2018 7:43:19 PM.930 [022] Check for updates, dev: True
1/20/2018 7:43:28 PM.178 [027] [E]Failed to download string from: https://cloud.awesomeminer.com/command/pull?userid=dGltLnJvbGxpbmdAZ21haWwuY29t&code=MDMzMTExMTkyMDg3MjM3MDg5MjA1MjMzMjA2MTk1MjA5MTE3MTEwMTUxMjAwMTI5MjIzMDY0MTYxMjM1MjE3MDg1MDEyMTYwMDgxMjM1MTgzMTUxMDMyMTAyMTQ0MjM1&systemid=1
 System.Net.WebException: The remote server returned an error: (400) Bad Request.
1/20/2018 7:43:38 PM.583 [010] [E]Failed to download string from: https://cloud.awesomeminer.com/command/pull?userid=dGltLnJvbGxpbmdAZ21haWwuY29t&code=MDMzMTExMTkyMDg3MjM3MDg5MjA1MjMzMjA2MTk1MjA5MTE3MTEwMTUxMjAwMTI5MjIzMDY0MTYxMjM1MjE3MDg1MDEyMTYwMDgxMjM1MTgzMTUxMDMyMTAyMTQ0MjM1&systemid=1
 System.Net.WebException: The remote server returned an error: (400) Bad Request.
1/20/2018 7:43:44 PM.801 [001] Log of miner status[ManagedMiner#2 - pb2.gtx1080TI_1]
  Type: Managed, EngineType: DstmMiner, EngineSubType: Disabled, UseWorkerSuffix: False, WorkerSuffix: , ManagedProfitMiner: True
  Algorithm: Equihash, LastStatusUpdate: 1/20/2018 7:43:44 PM, Enabled: True, InterfaceDisconnectedTimeUtc: 12/31/9999 11:59:59 PM
  State: Executing, ApiState: Connected, PendingCommand: False, MarkedForRemoval: False
  IsProfitMiner: True, IsManualStop: False, Autostart: True, Engine Type: DstmMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:

1/20/2018 7:45:33 PM.344 [024] [E]Failed to download string from: https://cloud.awesomeminer.com/command/pull?userid=dGltLnJvbGxpbmdAZ21haWwuY29t&code=MDMzMTExMTkyMDg3MjM3MDg5MjA1MjMzMjA2MTk1MjA5MTE3MTEwMTUxMjAwMTI5MjIzMDY0MTYxMjM1MjE3MDg1MDEyMTYwMDgxMjM1MTgzMTUxMDMyMTAyMTQ0MjM1&systemid=1
 System.Net.WebException: The remote server returned an error: (400) Bad Request.
1/20/2018 7:46:35 PM.820 [025] [E]Failed to download string from: https://cloud.awesomeminer.com/command/pull?userid=dGltLnJvbGxpbmdAZ21haWwuY29t&code=MDMzMTExMTkyMDg3MjM3MDg5MjA1MjMzMjA2MTk1MjA5MTE3MTEwMTUxMjAwMTI5MjIzMDY0MTYxMjM1MjE3MDg1MDEyMTYwMDgxMjM1MTgzMTUxMDMyMTAyMTQ0MjM1&systemid=1
 System.Net.WebException: The remote server returned an error: (400) Bad Request.
1/20/2018 7:47:27 PM.931 [028] [E]Failed to download string from: https://cloud.awesomeminer.com/command/pull?userid=dGltLnJvbGxpbmdAZ21haWwuY29t&code=MDMzMTExMTkyMDg3MjM3MDg5MjA1MjMzMjA2MTk1MjA5MTE3MTEwMTUxMjAwMTI5MjIzMDY0MTYxMjM1MjE3MDg1MDEyMTYwMDgxMjM1MTgzMTUxMDMyMTAyMTQ0MjM1&systemid=1
 System.Net.WebException: The remote server returned an error: (400) Bad Request.

[moppidoo]

Hello,
Running v4.3.3.  Menu tab indicates a new version available to download, but the update crashes.  Log file suggests failure to download required files from website.  Any ideas?

https://bitcointalk.org/index.php?topic=676942.msg28211753#msg28211753

[yhbae]

Interesting... I made an order for one of these plug as well to try out the concept you outlined above. The only issue I read with this approach is that another source tells me that IFTTT takes an hour to propagate the signal to the plug, which is kinda slow (although better than nothing I suppose).

So was this not the case for you? How long does it take for the plug to "react"?

Within seconds for me.  When I set it up in the first pass... I used the Wemo off/on applet with no waits in AM and I would watch the Wemo smart plug go off and on over and over because the rig is not going to respond to pings immediately.

Cool...

I currently use TP-Link's smart plugs (HS110) for my rigs and it too can measure the power consumption and it is very reliable, but  I couldn't find any ways to use IFTTT to reboot the rig when the overall power consumption dips below certain level. It simply doesn't exist.

You could potentially write your own applet, but that may be more effort than required.  I think if you use AM's triggers on dead device, offline, or no accepted in X minutes it would do essentially the same thing.  If you wanted to get really fancy, there is an applet in IFTTT for the Wemo insight to track switch usage in a Google spreadsheet.  Then setup applets to monitor that spreadsheet and take action.

Hmmm, so it sounds like it is possible to write some plug-in for AM to trigger IFTTT to control these smart plugs. Perhaps I should try this on my current TP-Link plugs. I have 9 of them - hopefully this approach works!

[wtfonly16]

doesnt let u add miners with diff ports wtf....

192.168.1.129:1337 is ip and doesnt work... i change api to 3333 and it works... completly ignores port

the fuck is this shit?

I'm assuming you are trying to setup mining software that doesn't come out of the box with AM?  What software is it?  Did you set it up as Managed Software in AM so that AM knows how to interface with it? 

its claymore eth miner..... because im using diff remote management port thats not the default 3333, awesome miner doesnt detect it.
i can pull api from it using ethman just fine....

Is it a different version than the one that came out of the box with AM?  If it's the same one, then you don't need to specify an API port, AM already knows how to do it.  It will be added automatically to the command line when it's issued to your rig.

If it's a different version, then you should tell AM about it as a new Managed Software entry.  Then in the entry, you tell AM that it's Claymore dual miner compatible, and it knows then what command line entry to add it's own API statement.

it wants me to add pools and shtt.. wtf? i just want to monitor.................

[cashen]

doesnt let u add miners with diff ports wtf....

192.168.1.129:1337 is ip and doesnt work... i change api to 3333 and it works... completly ignores port

the fuck is this shit?

I'm assuming you are trying to setup mining software that doesn't come out of the box with AM?  What software is it?  Did you set it up as Managed Software in AM so that AM knows how to interface with it?  

its claymore eth miner..... because im using diff remote management port thats not the default 3333, awesome miner doesnt detect it.
i can pull api from it using ethman just fine....

Is it a different version than the one that came out of the box with AM?  If it's the same one, then you don't need to specify an API port, AM already knows how to do it.  It will be added automatically to the command line when it's issued to your rig.

If it's a different version, then you should tell AM about it as a new Managed Software entry.  Then in the entry, you tell AM that it's Claymore dual miner compatible, and it knows then what command line entry to add it's own API statement.

it wants me to add pools and shtt.. wtf? i just want to monitor.................

Are you setting up an "external" miner? Sounds like you are setting up a managed miner.

[eminer001]

Is there any way to set an overclock profile per gpu and per algo?

so for example MINER01 -> GPU0 -> will have different overclock settings based on the different algos THEN MINER01 -> GPU1 -> will have different overclock settings based on the different algos  and so on

is it possible?

I also agree that one algo needs memory OC and another algo needs base clock oc. Without this functionality we are not maximizing the profits, and mining is all about maximizing profits by having all coins and algos and best settings for each.

[eminer001]

Please add Intense (ITNS) and Masari (MSR).  Small, but profitable, CryptoNight coins.

Yes, we have a very small number of coins in AM , a lot of profitable ones are missing.

[eminer001]

I know you're working on a lot of these. Keep up the great work!!

1 Suggestion.

1. Move the "Current" vs "24 hour average" to profit page
2. Have it be current or Custom, where custom is average in X mins. This will allow the user to choose 5 minutes, 1440 for 1 day etc.

https://i.imgur.com/qOajjBE.png

https://i.imgur.com/1Fw3RQ0.png

Anyone like or dislike this suggestion please provide constructive feedback.

I also believe that custom minutes is the best to have. 24 hours is too much, but something like 10 minutes or 1 hour would be a lot more helpful.

[ruplikminer]

Is there any way to set an overclock profile per gpu and per algo?

so for example MINER01 -> GPU0 -> will have different overclock settings based on the different algos THEN MINER01 -> GPU1 -> will have different overclock settings based on the different algos  and so on

is it possible?

I also agree that one algo needs memory OC and another algo needs base clock oc. Without this functionality we are not maximizing the profits, and mining is all about maximizing profits by having all coins and algos and best settings for each.

Exactly. That's what I really need. Some algos runs better on base clock some others on memory. This would be a very useful feature! Patrick already told me that it will be added shortly!

[thucar]

Well, my things are going from bad to worse.

This is what my AM dashboard is showing right now. Both miners are spending more time idling than working.

https://i.snag.gy/M4wiKn.jpg

EDIT: Just upgraded to the latest Dev version - both, the monitoring PC as well as both remote clients on the miners. No change, still restarting both miners at the exact same time every 15-20 minutes.