GUI round 9 (#4): fix WhatsMiner power-limit (v3 auth/param) + asic-rs patch queue

Round-9 #4 -- "the power-limit on the WhatsMiners doesn't apply properly" --
root-caused and verified against the live fleet, then fixed in vendored asic-rs
via a new patch queue (ADR 0003).

Root cause: asic-rs routes a WhatsMiner to its v3 (WhatsMinerOS) backend when
the firmware date is >= 2024-11-01. The v3 privileged power-limit write
(command "set.miner.power_limit" on port 4433) authenticated against account
"super" but hashed the token with the WEB/admin password, and sent the watt
value as a float -- so the miner rejected every write with "invalid json or
password is wrong". asic-rs then swallowed that (Ok(data.is_ok()) -> Ok(false))
so the GUI showed "refused" with no reason. (Older miners, fw < 2024-11-01, use
the v2 "adjust_power_limit" path, which restarts the miner on a change -- see
below.)

Fix (thirdparty/asic-rs/patches/0001):
- v3 set_auth: the "super" account's token password is a SEPARATE v3 credential
  (factory default "super"), NOT the web/admin password carried by `auth`; use
  "super". The web password still drives the v2 (admin) path.
- v3 set_power_limit: send the watts as a bare integer (a float trips the
  firmware's "invalid json" parser).
- v2 + v3: propagate the RPC error with `?` instead of swallowing it to
  Ok(false), so a real failure reaches the round-9 bottom-right error indicator
  with the miner's own message.

Verified on a live M30S+ (fw 20241108, api 3.0.1) via a read-only 4028
capture/restore harness: the fixed request returns {"code":0,"msg":"ok"};
asic-rs set_power_limit now returns Ok(true) and the miner applies the limit
(it restarts to re-tune, ~10 min ramp -- expected WhatsMiner behaviour). Matches
the pyasic and HashSource whatsminer-api-3 references. All test miners were
returned to their prior configured limit.

asic-rs patch-queue mechanism (ADR 0003 updated): asic-rs is cargo-vendored, so
in-place edits are documented as a numbered patch under thirdparty/asic-rs/
plus a checksum-refresh helper and scripts/apply-asic-rs-patches.sh for
re-vendoring. The committed vendor/ tree has the patch applied and its
.cargo-checksum.json refreshed, so builds need nothing extra (CI builds fresh;
a note documents the local `cargo clean -p` cargo-caching gotcha).

Known follow-up: the v2 backend (fw < 2024-11-01) reaches the miner via
"adjust_power_limit" but a changed value restarts the miner and the in-restart
status check reports failure; whether it applies correctly needs its own
verification. The error-propagation change surfaces that honestly meanwhile.

Compile-checked (release + tests); 79 offline tests pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y8h447BPyJR4fioYZvQ9bh
This commit is contained in:
2026-09-18 14:10:05 -06:00
co-authored by Claude Opus 4.8
parent 3ac4e104a0
commit 3530d67a5c
8 changed files with 256 additions and 13 deletions
+9 -1
View File
@@ -20,7 +20,15 @@ vendor/ cargo-managed crate sources ONLY (regenerated by
`cargo vendor vendor`; it deletes unmanaged dirs - never
put hand-made trees here; learned the hard way)
thirdparty/
asic-rs lives in vendor/ (pure crates.io dep, cargo-vendored)
asic-rs the vendored crates live in vendor/ (crates.io dep,
VERSION cargo-vendored); this dir holds their patch queue:
patches/ 0001 whatsminer set_power_limit error propagation (#4)
refresh-checksums.py rewrites a vendored crate's .cargo-checksum.json
after a patch (cargo verifies each file's SHA256)
The committed vendor/ tree has the patches applied and the
affected .cargo-checksum.json refreshed, so builds need
nothing extra. On re-vendor, run
scripts/apply-asic-rs-patches.sh to re-apply + refresh.
wxwidgets/
wxWidgets-3.3.3/ pristine release tree, never edited directly
VERSION upstream version + tarball URL + sha256
+33
View File
@@ -0,0 +1,33 @@
#!/bin/bash
# Re-apply the asic-rs patch queue to the cargo-vendored tree and refresh the
# affected crates' .cargo-checksum.json. Run this after `cargo vendor vendor`
# (which regenerates a pristine vendor/ and drops our edits). A normal build
# does NOT need this -- the committed vendor/ tree already has the patches
# applied and checksums refreshed; this is the re-vendoring recipe (ADR 0003).
set -euo pipefail
REPO=$(CDPATH= cd -- "$(dirname -- "$0")/.." && pwd)
cd "$REPO"
PATCHES_DIR="thirdparty/asic-rs/patches"
shopt -s nullglob
patches=("$PATCHES_DIR"/*.patch)
if [ ${#patches[@]} -eq 0 ]; then
echo "no patches in $PATCHES_DIR"
exit 0
fi
for p in "${patches[@]}"; do
echo "== applying $p =="
if git apply --check -p1 "$p" 2>/dev/null; then
git apply -p1 "$p"
elif git apply --check -p1 --reverse "$p" 2>/dev/null; then
echo " (already applied -- skipping)"
else
echo "ERROR: $p does not apply cleanly; resolve manually." >&2
exit 1
fi
done
echo "== refreshing checksums for all vendored asic-rs crates =="
python3 thirdparty/asic-rs/refresh-checksums.py --all
echo "done."
+34
View File
@@ -0,0 +1,34 @@
upstream: asic-rs (crates.io)
version: 0.8.1 (cargo-vendored under vendor/, per ADR 0003)
state: pristine cargo-vendored tree + this patch queue.
asic-rs is materialized with `cargo vendor vendor` and consumed through
.cargo/config.toml's vendored-sources replacement (directory = "vendor").
Unlike wx-rs, asic-rs is many crates (asic-rs, asic-rs-core, and the
per-make / per-firmware crates); a change to any of them lives here as a
numbered .patch, NOT as an in-place edit of the pristine tree (ADR 0003).
The committed vendor/ tree already has the patches applied AND its affected
crates' .cargo-checksum.json refreshed, so a normal build needs nothing extra
-- the patch queue is provenance + the re-vendoring recipe.
GOTCHA (cargo caching): cargo fingerprints a registry/vendored crate by
(name, version, source), NOT by file content, so it will REUSE a cached
build of a vendored crate even after its source is edited. CI is unaffected
(fresh target/ each run compiles the patched source). But an incremental
LOCAL build that already compiled the unpatched crate must be forced:
cargo clean -p asic-rs-firmwares-whatsminer # then rebuild
Otherwise the local binary silently keeps the old behaviour.
Update / re-vendor flow:
1. bump the pin in crates/alkane-gui/Cargo.toml, `cargo vendor vendor`
(this regenerates a pristine vendor/ and DROPS our edits)
2. scripts/apply-asic-rs-patches.sh # re-applies patches/ + refreshes checksums
3. resolve any patch that no longer applies, rebuild, commit
patches/:
0001 whatsminer set_power_limit (round-9 #4): fix the v3 (WhatsMinerOS)
privileged auth -- the "super" account's token password is the separate
v3 credential (default "super"), not the web/admin password -- and send
the watts as a bare integer; also propagate the RPC error instead of
swallowing it to Ok(false). See the patch header.
@@ -0,0 +1,86 @@
Subject: [PATCH 0001] whatsminer set_power_limit: fix v3 auth/param + propagate errors
Round-9 #4 (WhatsMiner power-limit "doesn't apply properly"). Root-caused and
verified against the live fleet.
v3 backend (WhatsMinerOS, firmware >= 2024-11-01, port 4433): the privileged
power-limit write authenticated against account "super" but hashed the token
with the WEB/admin password carried by `auth`, and sent the watt value as a
float. The miner rejected every such write with "invalid json or password is
wrong". Two fixes:
- set_auth: the "super" account's token password is a SEPARATE v3 credential
(factory default "super"), NOT the web/admin password; use "super". The web
password still drives the v2 (admin) path.
- set_power_limit: send the watts as a bare integer, not a float ("3000.0"
trips the firmware's "invalid json" parser).
Confirmed on a live M30S+ VH65 (fw 20241108, api 3.0.1): the fixed request
`{"cmd":"set.miner.power_limit","param":3000,"ts":..,"account":"super","token":..}`
returns {"code":0,"msg":"ok"}; asic-rs set_power_limit now returns Ok(true) and
the miner applies the limit (matches pyasic / HashSource whatsminer-api-3).
v2 + v3 backends: both wrote `Ok(data.is_ok())`, which swallowed any RPC failure
into Ok(false) and hid the miner's own status message. Propagate the error with
`?` and return Ok(true) on success (like the Braiins/Auradine/Proto backends),
so a genuine failure reaches the caller and the round-9 error indicator.
diff --git a/vendor/asic-rs-firmwares-whatsminer/src/backends/v2/mod.rs b/vendor/asic-rs-firmwares-whatsminer/src/backends/v2/mod.rs
index c7b00e3b..11b07542 100644
--- a/vendor/asic-rs-firmwares-whatsminer/src/backends/v2/mod.rs
+++ b/vendor/asic-rs-firmwares-whatsminer/src/backends/v2/mod.rs
@@ -637,11 +637,10 @@ impl SetFaultLight for WhatsMinerV2 {
impl SetPowerLimit for WhatsMinerV2 {
async fn set_power_limit(&self, limit: Power) -> anyhow::Result<bool> {
let parameters = Some(json!({"power_limit": limit.as_watts().to_string()}));
- let data = self
- .rpc
+ self.rpc
.send_command("adjust_power_limit", true, parameters)
- .await;
- Ok(data.is_ok())
+ .await?;
+ Ok(true)
}
fn supports_set_power_limit(&self) -> bool {
true
diff --git a/vendor/asic-rs-firmwares-whatsminer/src/backends/v3/mod.rs b/vendor/asic-rs-firmwares-whatsminer/src/backends/v3/mod.rs
index 77d724d5..34b7a7f8 100644
--- a/vendor/asic-rs-firmwares-whatsminer/src/backends/v3/mod.rs
+++ b/vendor/asic-rs-firmwares-whatsminer/src/backends/v3/mod.rs
@@ -669,12 +669,14 @@ impl SetFaultLight for WhatsMinerV3 {
#[async_trait]
impl SetPowerLimit for WhatsMinerV3 {
async fn set_power_limit(&self, limit: Power) -> anyhow::Result<bool> {
- let data = self
- .rpc
- .send_command("set.miner.power_limit", true, Some(json!(limit.as_watts())))
- .await;
+ // WhatsMinerOS wants a BARE INTEGER watt value; a float ("3000.0")
+ // trips the firmware's "invalid json" parser (round-9 #4).
+ let watts = limit.as_watts().round() as u64;
+ self.rpc
+ .send_command("set.miner.power_limit", true, Some(json!(watts)))
+ .await?;
- Ok(data.is_ok())
+ Ok(true)
}
fn supports_set_power_limit(&self) -> bool {
true
@@ -806,8 +808,15 @@ impl HasDefaultAuth for WhatsMinerV3 {
impl HasAuth for WhatsMinerV3 {
fn set_auth(&mut self, auth: MinerAuth) {
- // WhatsMiner V3 username is always "super", V2 is always "admin"
- self.rpc.set_auth(MinerAuth::new("super", auth.password()));
+ // WhatsMiner V3 username is always "super", V2 is always "admin".
+ // The V3 privileged token authenticates against the "super" ACCOUNT,
+ // whose password is a separate v3 credential (factory default "super")
+ // -- NOT the web/admin password carried by `auth`. Pairing account
+ // "super" with the web password made every v3 privileged write fail with
+ // "invalid json or password is wrong" (round-9 #4, confirmed on the live
+ // fleet). Keep the super-account default password here; the web password
+ // still drives the v2 (admin) path below.
+ self.rpc.set_auth(MinerAuth::new("super", "super"));
self.v2_rpc
.set_auth(MinerAuth::new("admin", auth.password()));
}
+74
View File
@@ -0,0 +1,74 @@
#!/usr/bin/env python3
"""Refresh the .cargo-checksum.json of vendored asic-rs crates after the patch
queue (thirdparty/asic-rs/patches/) has been applied to the cargo-vendored tree.
cargo verifies each vendored file against the per-file SHA256 in that crate's
.cargo-checksum.json; a patched file whose checksum is stale fails the build. For
every crate named on the command line (or, with --all, every asic-rs* crate under
vendor/), this recomputes the SHA256 of each file already listed in the manifest
and rewrites it, preserving the top-level "package"/"$comment" keys. Files not
listed are left alone (cargo only checks listed files).
Usage:
refresh-checksums.py <crate-dir> [<crate-dir> ...]
refresh-checksums.py --all # every vendor/asic-rs* crate
"""
import hashlib
import json
import sys
from pathlib import Path
REPO = Path(__file__).resolve().parents[2]
VENDOR = REPO / "vendor"
def sha256(path: Path) -> str:
h = hashlib.sha256()
with open(path, "rb") as f:
for chunk in iter(lambda: f.read(1 << 16), b""):
h.update(chunk)
return h.hexdigest()
def refresh(crate_dir: Path) -> int:
manifest = crate_dir / ".cargo-checksum.json"
if not manifest.exists():
print(f"skip {crate_dir.name}: no .cargo-checksum.json")
return 0
data = json.loads(manifest.read_text())
files = data.get("files", {})
changed = 0
for rel in list(files):
fp = crate_dir / rel
if not fp.exists():
print(f" WARN {crate_dir.name}: listed file missing: {rel}")
continue
new = sha256(fp)
if new != files[rel]:
files[rel] = new
changed += 1
if changed:
manifest.write_text(json.dumps(data, separators=(",", ":")))
print(f"{crate_dir.name}: refreshed {changed} checksum(s)")
else:
print(f"{crate_dir.name}: no changes")
return changed
def main() -> None:
args = sys.argv[1:]
if not args:
print(__doc__)
sys.exit(2)
if args == ["--all"]:
crates = sorted(p for p in VENDOR.glob("asic-rs*") if p.is_dir())
else:
crates = [Path(a) if Path(a).is_absolute() else (VENDOR / a) for a in args]
total = 0
for c in crates:
total += refresh(c)
print(f"done: {total} checksum(s) refreshed across {len(crates)} crate(s)")
if __name__ == "__main__":
main()
+1 -1
View File
@@ -1 +1 @@
{"$comment":"This file only protects against accidental modifications. It is not a security mechanism and does not protect against malicious changes.","files":{".cargo_vcs_info.json":"30f09ad063df45fdf223aff235fe2da15cb1a7e79e86d7012074153b91662fc4","Cargo.lock":"9d0886791db53421d3218ab72d964145b86cfbe9738eaf09aac5d3c89a1c0190","Cargo.toml":"8c2e9938436850f2e250e8268ed7b385fce903e2077923b207a0560ca3e3242c","Cargo.toml.orig":"891fcfa45e79d6bc4d838c4f3075618f791bd013c99231da48e752b987f409d5","src/backends/mod.rs":"0f5a0ae31d5443d0d0f41a2540def806196238c92d22761b3ad9843cb2e77f45","src/backends/v1/mod.rs":"80f3915f1e87c6f7483e9bd0e5b1fb5552f8d017634c82eea6150fe5134b171f","src/backends/v1/rpc.rs":"4cee9caeb9bc291c4efec04f4b7fc2b8eaead904a1f2d0f30e13236476d9aac5","src/backends/v2/mod.rs":"a1a054eda0b1466b8ae1693f47d6f2d79cc0ac067eb82320c4d659c9e1eaef0f","src/backends/v2/rpc.rs":"b7afc5357d24de42350d4ec15a6b5a37698e4fd77b2c2cc8071f303ee62e957c","src/backends/v3/mod.rs":"fd232f2df64b148f0998726fc41c089d08080ba25b3ca37bcb1c7f43b08b1c17","src/backends/v3/rpc.rs":"7a5f80aec4af1bcaa0d36e67345aa9acbbd8ead73c0be474f06305358b38e81b","src/error_codes.rs":"de85845f52b1d4e1a0bff73462cef00962b60fad8a3ed71c7bb083c02df3a413","src/firmware.rs":"6d002e481ce0a897c0485b9393b0382fcb25811164e893eb8eb67b2ff392ca0d","src/lib.rs":"710b46c9d934f26f900e1366ca1df5f872896e7d8da03569c0f159859e899cc9","src/test/json/mod.rs":"99760925ccfefc40d2455d3567fb1ecfc99e9e55e70478190ef372a954825909","src/test/json/v1/devs.json":"b4fd010f0bae3584efde93387cf2dab5933b499cc30a2dd7635fdc994b56c3b8","src/test/json/v1/get_psu.json":"8c11b6495e0bd5da496dd5c10ca53ec53b2d8fe9a3737f470ec9ce2c1aaf9d99","src/test/json/v1/get_version.json":"c43e947e654792ab191210d50c6f793ee0dd7af41e8cb59f0722b70f32a203bc","src/test/json/v1/mod.rs":"e79509eee78a1fef63735afe385299813726822c8259a02d1dcf5e8b4db9d04e","src/test/json/v1/pools.json":"b570808a3428a0773d7d2ee322150d8fd0794a33804af970300a7fef128a8a01","src/test/json/v1/status.json":"00ec38dd9f980b7ac0ffd6f815374afdbbed98d601bd8ef18bcf0f76ae0aa853","src/test/json/v1/summary.json":"d6e3e75654eb4019e1f479b3d9cf3097130f1afb85dd3338682c094fd4ab498a","src/test/json/v1/summary_with_errors.json":"1ba682f6ad5c43e41ae22a4069d0f52f04da3f07a18031bf4c07e07b3c59cc97","src/test/json/v2/devs.json":"2d203e41ef6ef337c0c81456b73d08730882c3167403c557c3c9776022a972d1","src/test/json/v2/get_error_code.json":"e90b702fd97bceb4f62dcb8228f75ff5ce930290355dca94eefd7192f7f57009","src/test/json/v2/get_error_code_with_errors.json":"6cb6038366eb3835684421c41be0b2b30ae8ce79a7ed51a85f4f52f70da9df16","src/test/json/v2/get_miner_info.json":"55d2af984833a692f502188ae4df4e41bdc10386b47f921c896a452ef1de9062","src/test/json/v2/get_psu.json":"b43086b65897061521d1f6611e200ef372a1724f9ea1876e347c03d5fb19b8f2","src/test/json/v2/get_version.json":"b17e3a81603b43186b2e15745e6822b6c82b3c6f5928b22f84e683d7728dbfcd","src/test/json/v2/mod.rs":"c847205d076323bbd9698e393d241b08f3cf75d32aae86f7058cf8748266b935","src/test/json/v2/pools.json":"926d34e8dae774473ebfec83d4a38e77ca73231708f07683763e212be7af0580","src/test/json/v2/status.json":"fc268cd23864ef99e84813dbf8eb916b2e6f339351a0ee5dab217cbe02569fc3","src/test/json/v2/summary.json":"4e4c01b986e2960893f58d0f1ea4dce23b8ef88db4985348f7f0183eb4818478","src/test/json/v3/get_device_info.json":"83ac22ea9a11adbceb4c963db80aa62d9a2aa50d019a372394dece817d924cda","src/test/json/v3/get_device_info_with_errors.json":"24cee4b7840e87e12147cbfddf6c361f3b378a15bb85330b339d3be9e17cdbd5","src/test/json/v3/get_miner_status_edevs.json":"2d831c06113f555e0988df994c2e602a053a4aea603dded0db8f0f80e191ca5a","src/test/json/v3/get_miner_status_pools.json":"cd65c2efd3a5ce80b57aae46c420298a34ca06df7ac7f8c36fd556217703d242","src/test/json/v3/get_miner_status_summary.json":"799a94ba13ef54aed0f81a3d041d6c1fa263d4183754b384c69ca12d85a8d3ba","src/test/json/v3/mod.rs":"7ea3a8ff1b81c7a5b0f44f7c12dda880a9aeac5b0e6b56ac4fff4f4a7cbfe451","src/test/mod.rs":"ed52c3d613eabc4a0346bb38bcfdf7a94933d61e368d3c9094821edeab92f81b"},"package":"c85da6325b62f061327dc5f7605dd3721c823a9e8a2cfd6a356363dfbc84d66e"}
{"$comment":"This file only protects against accidental modifications. It is not a security mechanism and does not protect against malicious changes.","files":{".cargo_vcs_info.json":"30f09ad063df45fdf223aff235fe2da15cb1a7e79e86d7012074153b91662fc4","Cargo.lock":"9d0886791db53421d3218ab72d964145b86cfbe9738eaf09aac5d3c89a1c0190","Cargo.toml":"8c2e9938436850f2e250e8268ed7b385fce903e2077923b207a0560ca3e3242c","Cargo.toml.orig":"891fcfa45e79d6bc4d838c4f3075618f791bd013c99231da48e752b987f409d5","src/backends/mod.rs":"0f5a0ae31d5443d0d0f41a2540def806196238c92d22761b3ad9843cb2e77f45","src/backends/v1/mod.rs":"80f3915f1e87c6f7483e9bd0e5b1fb5552f8d017634c82eea6150fe5134b171f","src/backends/v1/rpc.rs":"4cee9caeb9bc291c4efec04f4b7fc2b8eaead904a1f2d0f30e13236476d9aac5","src/backends/v2/mod.rs":"bb2018a1e2b6782df93b99f0d1454f9cb403b4df5f4061612baa129d18daaffa","src/backends/v2/rpc.rs":"b7afc5357d24de42350d4ec15a6b5a37698e4fd77b2c2cc8071f303ee62e957c","src/backends/v3/mod.rs":"51edd45ca2016316842109ac6ade6178d2d66546e5df9f6e75a96aae26504ba8","src/backends/v3/rpc.rs":"7a5f80aec4af1bcaa0d36e67345aa9acbbd8ead73c0be474f06305358b38e81b","src/error_codes.rs":"de85845f52b1d4e1a0bff73462cef00962b60fad8a3ed71c7bb083c02df3a413","src/firmware.rs":"6d002e481ce0a897c0485b9393b0382fcb25811164e893eb8eb67b2ff392ca0d","src/lib.rs":"710b46c9d934f26f900e1366ca1df5f872896e7d8da03569c0f159859e899cc9","src/test/json/mod.rs":"99760925ccfefc40d2455d3567fb1ecfc99e9e55e70478190ef372a954825909","src/test/json/v1/devs.json":"b4fd010f0bae3584efde93387cf2dab5933b499cc30a2dd7635fdc994b56c3b8","src/test/json/v1/get_psu.json":"8c11b6495e0bd5da496dd5c10ca53ec53b2d8fe9a3737f470ec9ce2c1aaf9d99","src/test/json/v1/get_version.json":"c43e947e654792ab191210d50c6f793ee0dd7af41e8cb59f0722b70f32a203bc","src/test/json/v1/mod.rs":"e79509eee78a1fef63735afe385299813726822c8259a02d1dcf5e8b4db9d04e","src/test/json/v1/pools.json":"b570808a3428a0773d7d2ee322150d8fd0794a33804af970300a7fef128a8a01","src/test/json/v1/status.json":"00ec38dd9f980b7ac0ffd6f815374afdbbed98d601bd8ef18bcf0f76ae0aa853","src/test/json/v1/summary.json":"d6e3e75654eb4019e1f479b3d9cf3097130f1afb85dd3338682c094fd4ab498a","src/test/json/v1/summary_with_errors.json":"1ba682f6ad5c43e41ae22a4069d0f52f04da3f07a18031bf4c07e07b3c59cc97","src/test/json/v2/devs.json":"2d203e41ef6ef337c0c81456b73d08730882c3167403c557c3c9776022a972d1","src/test/json/v2/get_error_code.json":"e90b702fd97bceb4f62dcb8228f75ff5ce930290355dca94eefd7192f7f57009","src/test/json/v2/get_error_code_with_errors.json":"6cb6038366eb3835684421c41be0b2b30ae8ce79a7ed51a85f4f52f70da9df16","src/test/json/v2/get_miner_info.json":"55d2af984833a692f502188ae4df4e41bdc10386b47f921c896a452ef1de9062","src/test/json/v2/get_psu.json":"b43086b65897061521d1f6611e200ef372a1724f9ea1876e347c03d5fb19b8f2","src/test/json/v2/get_version.json":"b17e3a81603b43186b2e15745e6822b6c82b3c6f5928b22f84e683d7728dbfcd","src/test/json/v2/mod.rs":"c847205d076323bbd9698e393d241b08f3cf75d32aae86f7058cf8748266b935","src/test/json/v2/pools.json":"926d34e8dae774473ebfec83d4a38e77ca73231708f07683763e212be7af0580","src/test/json/v2/status.json":"fc268cd23864ef99e84813dbf8eb916b2e6f339351a0ee5dab217cbe02569fc3","src/test/json/v2/summary.json":"4e4c01b986e2960893f58d0f1ea4dce23b8ef88db4985348f7f0183eb4818478","src/test/json/v3/get_device_info.json":"83ac22ea9a11adbceb4c963db80aa62d9a2aa50d019a372394dece817d924cda","src/test/json/v3/get_device_info_with_errors.json":"24cee4b7840e87e12147cbfddf6c361f3b378a15bb85330b339d3be9e17cdbd5","src/test/json/v3/get_miner_status_edevs.json":"2d831c06113f555e0988df994c2e602a053a4aea603dded0db8f0f80e191ca5a","src/test/json/v3/get_miner_status_pools.json":"cd65c2efd3a5ce80b57aae46c420298a34ca06df7ac7f8c36fd556217703d242","src/test/json/v3/get_miner_status_summary.json":"799a94ba13ef54aed0f81a3d041d6c1fa263d4183754b384c69ca12d85a8d3ba","src/test/json/v3/mod.rs":"7ea3a8ff1b81c7a5b0f44f7c12dda880a9aeac5b0e6b56ac4fff4f4a7cbfe451","src/test/mod.rs":"ed52c3d613eabc4a0346bb38bcfdf7a94933d61e368d3c9094821edeab92f81b"},"package":"c85da6325b62f061327dc5f7605dd3721c823a9e8a2cfd6a356363dfbc84d66e"}
+3 -4
View File
@@ -637,11 +637,10 @@ impl SetFaultLight for WhatsMinerV2 {
impl SetPowerLimit for WhatsMinerV2 {
async fn set_power_limit(&self, limit: Power) -> anyhow::Result<bool> {
let parameters = Some(json!({"power_limit": limit.as_watts().to_string()}));
let data = self
.rpc
self.rpc
.send_command("adjust_power_limit", true, parameters)
.await;
Ok(data.is_ok())
.await?;
Ok(true)
}
fn supports_set_power_limit(&self) -> bool {
true
+16 -7
View File
@@ -669,12 +669,14 @@ impl SetFaultLight for WhatsMinerV3 {
#[async_trait]
impl SetPowerLimit for WhatsMinerV3 {
async fn set_power_limit(&self, limit: Power) -> anyhow::Result<bool> {
let data = self
.rpc
.send_command("set.miner.power_limit", true, Some(json!(limit.as_watts())))
.await;
// WhatsMinerOS wants a BARE INTEGER watt value; a float ("3000.0")
// trips the firmware's "invalid json" parser (round-9 #4).
let watts = limit.as_watts().round() as u64;
self.rpc
.send_command("set.miner.power_limit", true, Some(json!(watts)))
.await?;
Ok(data.is_ok())
Ok(true)
}
fn supports_set_power_limit(&self) -> bool {
true
@@ -806,8 +808,15 @@ impl HasDefaultAuth for WhatsMinerV3 {
impl HasAuth for WhatsMinerV3 {
fn set_auth(&mut self, auth: MinerAuth) {
// WhatsMiner V3 username is always "super", V2 is always "admin"
self.rpc.set_auth(MinerAuth::new("super", auth.password()));
// WhatsMiner V3 username is always "super", V2 is always "admin".
// The V3 privileged token authenticates against the "super" ACCOUNT,
// whose password is a separate v3 credential (factory default "super")
// -- NOT the web/admin password carried by `auth`. Pairing account
// "super" with the web password made every v3 privileged write fail with
// "invalid json or password is wrong" (round-9 #4, confirmed on the live
// fleet). Keep the super-account default password here; the web password
// still drives the v2 (admin) path below.
self.rpc.set_auth(MinerAuth::new("super", "super"));
self.v2_rpc
.set_auth(MinerAuth::new("admin", auth.password()));
}