[upstream-doc] foxess_h3_smart: nathanmarlor/foxess_modbus community register map (Inv.H3_SMART profile) changed (c4c6bf8b)

[github-actions]

The upstream document foxess_h3_smart is watched against has changed.

• Driver: foxess_h3_smart — drivers/lua/foxess_h3_smart.lua, manifests/foxess_h3_smart.yaml
• Document: nathanmarlor/foxess_modbus community register map (Inv.H3_SMART profile)
• URL: https://github.com/nathanmarlor/foxess_modbus
• Kind: register_map
• URL stability: stable
• Previous SHA-256: 7c1b7ee30cb560df896dbd5be771385c9d8e36650b2c8842e3714822a58f5fd2
• New SHA-256: c4c6bf8bfdbdeb0e10a180a09f2612c5680cd6ace1eae4c823fbfead27f384ea
• Detected: 2026-08-31T06:47:39+00:00

Review

• Read the new document and note what changed (registers renumbered,
  parameters added, scaling corrected).
• Cross-check against the registers/parameters foxess_h3_smart reads.
• If the driver is affected, open a fix and bump its version;
  otherwise close this issue.

Detection is a raw-byte hash: the file's bytes moved. That can be a
genuine content change or just rebuild churn in the PDF metadata —
this issue is a prompt to look, not proof the registers changed.

[frahlg]

Reviewed and closing as not affecting the driver.

The watched URL (manifests/foxess_h3_smart.yaml → upstream_docs) is https://github.com/nathanmarlor/foxess_modbus — the repository's landing page, not a specific register-map file. Fetching it confirms it's the standard GitHub repo page: description, star/fork/issue counts, install instructions, service docs. There is no register map or Inv.H3_SMART profile content on that page at all — the actual register definitions live elsewhere in that repo (its wiki or a config/const file), so this watch has never actually been hashing the registers foxess_h3_smart decodes by.

That also explains the byte delta here (307933 → 307299 bytes, -634 bytes): far more consistent with routine landing-page churn (star count, commit count, relative timestamps) than with a content edit. I found nothing to cross-check against the driver's registers because there's nothing register-specific on this page to check.

No driver change needed. Separate from this issue: the upstream_docs.url for foxess_h3_smart should probably point at a specific, stable file in that repo (e.g. the actual Modbus profile/const source) rather than the repo root, so future watch hits carry signal instead of tracking page-view noise. Leaving that for a maintainer to pick the right pinned file rather than guessing here — repo-root PR #105 (accepting this baseline) is being merged separately.

---

Generated by Claude Code