Hey patrike could you add a way to manually reset performance statistics, like average?
Thanks for your request. Please let me know which ASIC and firmware you have in mind here, as I think there are only a few of them where this feature exists?
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.
The average hashrate in the Performance column is actually a value reported by the ASIC miners. To see the average hashrate as recorded by Awesome Miner, please open the Mining History for the miner. This way you can see the average hashrate for the period of time you want - for example the 24h average hashrate.
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.
1) After mining for 24 hours - is the Braiins 24h avg hashrate different from the hashrate you see in the Mining History in Awesome Miner, when selecting 1 day?
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.
Hi and thanks for all feedback.
1) For the current hashrate it's like you point out - Awesome Miner will request the current hashrate at some point and the ASIC web interface will request the current hashrate at some point. These two requests will never be made at the exact same time so it's expected to be different.
This is also the reason why any average values must be calculated over a longer period of time. The ASIC miners providing an average hashrate concept is keeping their own statistics and calculations for this and Awesome Miner will never be able to access it. Awesome Miner is instead sampling the hashrate, temperature and more to create its own statistics database. Over time this should be very close to what the ASIC miner reports. I will however review this to see if there are any issues or possible improvements to make here
3) Thanks for the update. I don't think we will be able to do this workaround in a good way in Awesome Miner as it's a bit risky to remove the pools. Awesome Miner could try to keep track of the removed pools for this miner and add them back later on, but what happens if a user is manually adding back some other pools? Or if the IP address of the miner changes? This workaround is too risky to implement from what I can see.
4) The Awesome Miner HTTP API can be used for this.
To get a variable, see this example:
https://www.awesomeminer.com/api#tag/Miners/paths/~1api~1miners~1%7Bid%7D~1variables~1%7Bname%7D/getTo update a variable, see this example:
https://www.awesomeminer.com/api#tag/Miners/paths/~1api~1miners~1%7Bid%7D~1variables~1%7Bname%7D/postAny external application can make a HTTP GET or POST to Awesome Miner to get and update the variables for a miner. To call these API methods from the command line you can use the tool "curl" to perform the requests.
