Skip to content

Fix hashrate sensor unit: H/s → GH/s - #8

Merged
fgrfn merged 2 commits into
mainfrom
copilot/fix-sensor-current-hashrate-unit
Mar 25, 2026
Merged

fgrfn merged 2 commits into
mainfrom
copilot/fix-sensor-current-hashrate-unit

Conversation

Copilot AI commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

The AxeOS API reports hashrate values in GH/s, but all hashrate sensors were labeled with H/s, causing incorrect unit display in Home Assistant.

Changes

  • sensor.py: Updated unit from "H/s" to "GH/s" for all six hashrate sensor definitions:
    • hashRate, hashRate_1m, hashRate_10m, hashRate_1h, hashRate_1d, expectedHashrate
# Before
"hashRate": ("Current Hashrate", "H/s", ["hashRate"], ...),

# After
"hashRate": ("Current Hashrate", "GH/s", ["hashRate"], ...),
  • README.md: Updated unit references in the sensor list and the automation example message template.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Fix incorrect unit displayed for current hashrate sensor Fix hashrate sensor unit: H/s → GH/s Mar 25, 2026
Copilot AI requested a review from fgrfn March 25, 2026 22:02
@fgrfn
fgrfn marked this pull request as ready for review March 25, 2026 22:03
@fgrfn
fgrfn merged commit dbede40 into main Mar 25, 2026
5 of 6 checks passed
@fgrfn
fgrfn deleted the copilot/fix-sensor-current-hashrate-unit branch March 25, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants