Thanks for the suggestion - I will improve that.

Thanks for the update on this. I will try to reproduce the scenario.

I would actually recommend you to check the setting for the connection timeout. Although it might sound attractive to increase the timeout to wait longer, in this case I think we should try to make it fail faster with a short timeout instead. Can you make sure that the setting "Increase connection timeout for Remote Agent" is unchecked, which is actually the default value?

Can you see if the files config.txt and awesome-restart.bat also are generated correctly in the same folder as pools.txt? In case Awesome Miner is unable to update/write to these files, it fail to start the mining software.

Is the log file for Remote Agent indicating that there are any issues creating these files? If you want, you could send me this log file.

Awesome Miner version 5.4.3 (Development preview of 5.5)

- Significant performance improvements to support a very large number of miners
- The Remote Proxy can do automatic discovery of new ASIC miners on the network and automatically add and remove new miners in Awesome Miner
- Introducing multiple columns when displaying External Miners, Managed Miners and Pools in the options dialog
- The dialog to save hashrate can also save the current power usage for the selected GPU (if reported by the mining software)
- Display of AMD and nVidia GPU driver version on the Summary tab for each Managed Miner and Managed Profit Miner
- Profit switching interval can be specified in both minutes and seconds and allows an interval as low as 30 seconds
- Profit switching setting for the minimum time a miner will stay on the same pool before i can change to another pool
- Filtering for Managed Template section of Options dialog
- Updated integration with the block explorer for Ethereum to continue the support for Ethereum wallet balance
- Selected lines on the Balance tab can be copied to the clipboard using Ctrl+C
- Updated coin images and cleanup of old coins
- Added API to get a list of coins and information from the Coins tab (/api/coins/stats)
- Added API to get a list of multi coin pools and information from the Online Services tab (/api/onlineservices/stats)
- Added API to get a list of all Profit profiles (/api/profitprofiles)
- CastXMR 1.4 with Cryptonight-Fest algorithm support
- SrbMiner 1.6.7
- Correction to scenario where pools are added from the web interface and used for performing actions on ASIC miners
- Correction to trigger for Revenue / Profit to not trigger too often
- Correction to user defined Managed Software to prevent new algorithms, that are disabled for the specific software, to show up in the Benchmarking window
- Correction to uptime display for Excavator miner version 1.5
- Minor corrections

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

Direct download links
http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
http://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

Thanks for the update. I will include the updated miner versions in the next release of Awesome Miner.

Would it be even better if I simply removed the small coin icon and the large generic pool icon, and replaced it with only a large coin icon? So instead of two icons you would only have one, and that would be a larger icon for the specific coin?

I think that would make most sense as the generic pool icon doesn't give so much information. If anyone else also have feedback on this as well, please let me know. Thanks!

Last time the profit switcher was a bit CPU heavy when using a large number of Profit profiles.

Version 5.4.3 will be released soon and includes even more optimizations to the performance and CPU load. Can you please upgrade to the latest version once available, and send me a new log file if you still run into this problem? You could also try to increase the profit switching interval to find out if the profit switcher is causing these issues. Thanks!

If the miner is stopped and you want to start it based on a profit value, you need to use the property "Profit Profile" instead of "Miner Profit", as the miner doesn't have any profit when stopped.

I just had another report on the issue with multiple triggering, when using the Revenue / Profit trigger. A correction will be included in the next release.

In the View Details dialog you can see the Profit hashrate for the pool/algorithm. Is this hashrate a non-zero value? If you go to the Coins tab and compare XDNA with the same hashrate, do you get a non-zero value?

Please get back to me with the log file and configuration file and I will investigate this in more detail. Thanks!

Some fields are updated on the miner when it's in profit switching mode, so when changing back to a Managed Miner all settings may not be kept. You can use the concept of Managed Templates to restore the Managed Miner properties to a saved state.

The closest Awesome Miner has to offer here is the Profit factor you can set on a individual pool (Pool Properties, Advanced section). Specifying a value like 0,88 here would make all profit reporting for this pool lower, but this will apply to both the estimates for the day and for the month. Having this specified for only the month is a very specific scenario that isn't supported.

If needed, you can use the rule action "Set property" to schedule power cost changes depending on day and time.

Good point. I will add support for this in the next release.

Thanks for the suggestion. From what I can see this software doesn't provide any monitoring API. The command line is however more or less compatible with ccminer.

If you run into this issue, please send me your log file and configuration file and I will be able to investigate in more detail. Thanks!

I've never seen any indication that it would be slower. For ASIC and GPU mining the CPU load is typically low anyway, so consuming a few more CPU cycles on a separate thread should be fine.

Awesome Miner request the status from the miner API every 5 seconds by default. You can also right click on an External Miner and select Properties to change this interval.

No matter if you have an ASIC miner or GPU miner, the mining calculations are made on the actual ASIC chip or GPU while the API requests are processed on the CPU. For this reason, there shouldn't be any performance impact.

I think you should use the concept of Profile Groups in this case. Your profit profile represents the hashrate and power usage for a single GPU - and that's perfectly fine. In addition, you can add a Profile group where you specify that you have two GPU's based on your profit profile. See the section "Profile groups":
https://support.awesomeminer.com/support/solutions/articles/35000086086-profit-switching-for-gpu-and-cpu-mining#profile

You would then specify that your Managed Profit Miner should be based on your Profile group (two GPU's) instead of your Profit profile (one GPU). That should make the power cost be correct as well.

There is a feature where you can customize the Progress column and use expressions to get additional information about the miner to be displayed. See:
https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-field

There is also an example on the page above for displaying Windows update. Current GPU clocking profile is however not yet supported.

Thanks for your feedback. There have been a few similar requests about display in both USD and BTC. It will probably be supported in the future - the main difficulty is to fit all the information in the user interface in a readable way as there can be values for both revenue and profit as well.