I meant in AwesomeMiner, not on the miner itself. Under performance category in the miners tab. Unless that's directly linked to the miner firmware? It appears as though it's different from what is displayed on the miner itself. Would be useful if this was a 24/hr rolling average instead of since powerup as well.
Also please add support for pause/resume mining for brains OS.
Maybe a future improvement would be to let you show this 24h average in the miner list as well.
This doesn't necessarily seem to be completely true, it doesn't match Braiins 24 hour hashrate for instance (it does eventually with enough time). It seems like Brains discards the warmup period and tuning periods after a certain amount of time where AM does not.
The pause functionality for Brains seems to be broken as well. This needs to be done with the BOSminer stop/start command.
2) The pause/resume feature for BraiinsOS has not yet been integrated with Awesome Miner. I can add it for the next release.
1. Yes, both for Braiins as well as Asicto 24 hour hashrates are off in terms of what average shows on AM vs the dashboard on the miner itself. It will gravitate close to the 24 hour hashrate on the miner within about a decimal, however this takes a decent chunk of time - sometimes a couple days. Hashrate averages over 6 and 12 hours are pretty far off. The instaneous reading also is off, however it might just be when AM is polling the data vs the dashboard.
2. Appreciate adding support!
3. Couple more things here, due to the nature of Braiins and how pause functionality works, it actually consumes much more power then it should. When you stop BOSminer it puts fans at 100% and doesn't completely power down the miner. This leads to around 80w of power usage. I've talked with the developers, but fixing this seems to be a very low priority for them.
However, if you remove the pools or the pools are dead, it drops into a very low power mode and the dev fee doesn't work. It will use around 13w of power and of course is much quieter. I can do this myself through some custom rules finagling, but if you could add a bandaid checkbox where AM will 'pause' mining by removing all the pools, then readd them again when you 'unpause' it will save power. Then add a rule to pause/unpause through this functionality.
4. I looked through the rules section and can't find a way to pull in variables from outside of AM. I assume this can be done through a custom script, but looking at a text document for a variable after formatting. IE look for syntax and then variable after syntax in a file. Such as start/stop time. This could be as simple as 1 or 0 in the file.