Skip to content

fix Fronius: Login schlägt manchmal fehl trotz korrekter Zugangsdaten - #4199

Merged
LKuemmel merged 1 commit into
openWB:masterfrom
seaspotter:fronius-auth-fix
Nov 11, 2026
Merged

LKuemmel merged 1 commit into
openWB:masterfrom
seaspotter:fronius-auth-fix

Conversation

@seaspotter

Copy link
Copy Markdown
Collaborator

Fix für: #3465 (comment)

Beim Login wurde teilweise mit zwei unterschiedlichen Hash-Verfahren gleichzeitig gerechnet, wodurch der Login fehlschlagen konnte, obwohl die Zugangsdaten stimmen. Jetzt wird durchgängig dasselbe Verfahren verwendet.

@ndrsnhs – kannst du drüberschauen, ob der Fix passt?

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Approval is deferred because interoperability of both SHA256 and MD5 fallback Digest authentication with relevant Fronius firmware cannot be confirmed without a representative inverter or protocol-level integration test.

No open issues 🎉

What changed in this PR

This PR fixes intermittent Fronius authentication failures by consistently using the negotiated hash algorithm throughout HTTP Digest authentication.

Changes:

  • Applies the selected algorithm to HA1, HA2, response hashing, and the authorization header.
  • Preserves the existing MD5/SHA-256 fallback behavior.
File Description
packages/​modules/​devices/​fronius/​fronius_http_api/​fronius_api.py Aligns all Fronius Digest authentication calculations and authorization header generation with the selected hash algorithm.

Review effort: Lite

@LKuemmel
LKuemmel merged commit 2212f19 into openWB:master Nov 11, 2026
1 check passed
@LKuemmel
LKuemmel removed the request for review from ndrsnhs November 11, 2026 09:32
@seaspotter
seaspotter deleted the fronius-auth-fix branch November 11, 2026 09:40
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.

3 participants