I think the scenario is the following:
- On Linux, Awesome Miner can only read memory temperature for AMD. For Windows both nVidia and AMD are supported.
- Recent mining software versions for Gminer, Lolminer and T-Rex have found some unofficiall way of reading the nVidia memory temperature on Linux.
- NbMiner and most other mining software cannot report memory temperature for nVidia on Linux
- When you use "Change device order", Awesome Miner will not use the mining software reported temperatures by default. Instead Awesome Miner will use what is available from Awesome Miner itself and also provide a way to set a custom device order.

Please note that "Change device order" is only needed in case you manually need to re-arrange the GPUs - in case Awesome Miner doesn't display the correct hashrate and monitoring details for some reason. In most cases you don't need to enable "Change device order".

When not enabled, you will get the memory temperature for all mining software where it's supported (Gminer, Lolminer, T-Rex).

I will also look into if there is a way to find out how they do read the memory temperature on Linux - as this isn't really public information.

Awesome Miner version 9.3.5

 Features
  - Define colors for miner groups, displayed on the Groups page
  - Properties of both Virtual Groups and Standard Groups can be configured via the Groups page
 Changes
  - Remove Legacy operations from ASIC Tools
 Mining software
  - TeamBlackMiner 1.62
 Correctoins
  - Correction to the use of variables in combination with the Remote Proxy

Thanks for your report. Awesome Miner should be able to figure out and show the details correctly in most cases, without the need of specifying the devices manually. I will look into this case and see how to improve.

Is this with combination of a specific mining software or a general problem?

Thanks for the suggestion. The mining history doesn't keep track of the number of shares per pool for each time interval at the moment. Right now it's only the primary pool that is being recorded and only how much time is being spent on the pools. It isn't possible to integrate this with the current design of the mining history.

You can at any point in time look at the pools and their number of accepted shares and difficulty to confirm where the hashrate is spend. As you can do this at any point in time you should be able to confirm and trust that the firmware takes the stated fee and nothing more. In case you need to verify this over time one possibility would be to do it via the API of the Antminer - where you can get the raw data, do the calculations and confirm the result.

Thanks for your question. Are you looking for a way to confirm how much of the hash power that is being used for the dev fee pool?

You should be able to see the difficulty and number of accepted share for all pools, including the dev fee pools. Please note that the dev fee pools have a very low difficulty so the number of shares may be quite high while the actual work spend on these pools are low compared to the work spend on your defined mining pools.

Awesome Miner version 9.3.4

 Features
  - Use of variables when setting Custom Configuration Properties on an ASIC miner
 Changes
  - Consider Whatsminer ASIC miners in sleep mode to be Disconnected
  - Trigger condition for finding miners not hashing has been improved to detect more scenarios
 Mining software
  - Cpu-Miner-Opt 3.19.7
  - Gminer 2.91
  - Lolminer 1.48
  - Nanominer 3.6.0
  - SrbMiner-Multi 0.9.4
  - XmRig 6.17.0
 Corrections
  - Correction to API processing of Gminer dual mining
  - Correction to dual mining coin detection in combination with use with the profit switcher
  - Correction to allow fan adjustments when global fan control has been disabled for a specific host

Awesome Miner is automatically downloading the mining software - but what can happen is that you have some security software or anti-virus software that removes it. For this reason, Awesome Miner will fail to start the mining software as the main executable is simply missing.

Please consider adding an exclusion for the folder in your security software.
C:\Users\rickk\AppData\Local\AwesomeMiner\

Unfortunately we don't provide any full mining OS ourselves.

Awesome Miner version 9.3.3

 Features
  - Rule action to clear all or acknowledge all notifications
  - Include ASIC error details in miner CSV export
 Changes
  - Updated AMD GPU clocking ranges for Linux
 Mining software
  - Gminer 2.90
  - Lolminer 1.47
 Corrections
  - Corrections to visible tabs for a selected miner
  - Correction to Gminer dual mining worker name
  - Correction to Ethermine pool balance

The concept of Privileged API Access isn't needed for more recent Antminers like S19 and L7. Awesome Miner can reboot, change pool and more on them anyway.

The visible tabs is a UI bug and will be corrected in the next release.

For Windows we detect what the drivers report for the clocking range. For some GPUs on Linux we had hard coded max values - and I will increase these for you.

Awesome Miner version 9.3.2

 Features
  - Binance pool balance
 Mining software
  - TeamBlackMiner 1.61
  - PhoenixMiner 6.0c
 Correction
  - Correction to update failures of pool balance
  - Correction to UI for history data selection when using 1 day as data resolution

Yes - it will be included now. There will be a new release with a few corrections in a moment.

Awesome Miner version 9.3.1

 ASIC mining
  - Added support for Goldshell LT6
  - Display of frequency and voltage for Goldshell ASIC miners. All Goldshell devices details are displayed on the ASIC tab.
 Configuration
  - Additional configuration options for history data resolution
  - Increase the upper limit for number of days to keep history data
  - Configure update interval for Managed Miners
 Mining software
  - Gminer 2.89
  - SrbMiner-Multi 0.9.3
  - TeamBlackMiner 1.60
  - WildRig miner 0.31.3
  - TeamRedMiner 0.9.4.1
  - T-Rex miner 0.25.9
 Corrections
  - Correction to Gminer dual mining setup for full URL pool paths

It's good that you tried with the .NET installation first, as the most common issue is a broken or corrupt .NET installation. Another common issue is that security software is preventing the installation from running successfully.

Also, for the issue related to Awesome Miner not starting correctly, could you please send me the Awesome Miner log file (even if uninstalled, you will still find it):
%localappdata%\AwesomeMiner\AwesomeMiner.log

Thanks!

There are a few dual mining design changes planned, to better be able to roll out these frequent new combinations of dual mining algorithms. You will find support for this in the near future.

Awesome Miner version 9.3

 ASIC mining
  - External Miner configuration is based on a ASIC hardware selection for ASIC miners (no software selection needed). Network scan is also updated to reflect this.
  - Added support for Innosilicon A6+
 GPU mining
  - Add a concept of secondary pool to simplify dual mining without having to use pool groups
  - Improved support for AMD Radeon Pro W6600 and BC-250 on Linux
  - User defined mining software improvements for dual mining
 Features
  - Rule trigger for CPU load
  - Configurable if message dialogs should be suppressed
  - Create API keys per user account making it possible to define limited and read-only API keys
  - Antpool balance
 User interface
  - Display last known worker name for disconnected External Miners
  - Updated description for a number of permissions for user groups
  - Hide buttons in the user interface not relevant for certain ASIC miner types
 Mining software
  - Gminer 2.83
  - Lolminer 1.46a
  - SrbMiner-Multi 0.9.2
  - TeamBlackMiner 1.56
  - TeamRedMiner 0.9.4, incl. update to Awesome Miner integration related to the eth_worker parameter and watchdog
  - T-Rex miner 0.25.8
 Corrections
  - Correction to coin trigger to also support user defined cons
  - Correction to Firmware mining profile trigger
  - Correction to network discovery not processing all IP address ranges in case of a single range with invalid IP address syntax

To make sure I understand the scenario correctly:
1) The External Miner is configured with "Add to worker name" and a value like "5" for example to identify this specific miner
2) You have at lease one pool defined in Awesome Miner (Options dialog, Pools section). Fill in the Pool URL, Worker name and Coin fields. The worker name is either a wallet or a pool username (for example "scmining")
3) You select the miner and go to the toolbar Tools -> ASIC Tools -> Default Pools
4) Select your pool and apply the changes.

Is the operation in step #4 successful?
Did the worker name for this miner become "scmining.5" or similar?

Thanks for the feedback - this is a good point.

Thanks for your question.

If you update the property "Add to worker name" in the properties of an External Miner - nothing will happen right away. Next time you use Awesome Miner to update the pools (toolbar: Tools -> ASIC Tools -> Default Pools) this setting will be used to give each Antminer a unique worker name.

SSH itself can be enabled but it isn't really intended to be used for anything so it might be removed in the future. Was it some specific feature you were looking for via SSH? For pool operations like Add Pool we will soon implement support for it without having to use the classic concepts like Privileged API access.