Skip to content

v0.16.4-beta.1 - Config flow fix for recent HA versions (beta)

Pre-release
Pre-release

Choose a tag to compare

@bvis bvis released this 11 Jun 19:05
8a8f77f

Beta release — please test before promoting to stable

Fixed

  • Config flow could not render on recent Home Assistant versions (#8, #9, #10, #11) — the credentials form schema used a custom callable HTTPS validator that voluptuous_serialize cannot convert (ValueError: Unable to convert schema: <function _https_url ...>), blocking login entirely. URL fields are now plain strings in the form schema and HTTPS validation runs after submit, returning a translated invalid_url error in all 10 languages. Contributed by @pespinel (#7) — thank you!
  • OAuth authentication diagnostics — non-JSON responses, HTTP errors, OAuth error payloads, and missing access_token are now handled explicitly with safe, redacted log messages; invalid_client errors point to the OAuth Basic header instead of the user's email/password.
  • APK credential extractionscripts/extract_credentials.py ignores unrelated Basic headers from tracing/telemetry code and generates the OAuth header from OAuthUtils.java + Urls.clientId()/Urls.clientSecret(), detecting the production environment; extracted secrets are redacted in console output.

How to test

  1. Install via HACS with Show beta versions enabled, or download the source for v0.16.4-beta.1 manually.
  2. Restart Home Assistant.
  3. Add the integration (Settings → Devices & Services → Add Integration → Fermax Blue). The login and credentials forms should now render and submit correctly.
  4. Complete the setup and verify entities appear.

If everything is stable for a few days, this will be promoted to v0.16.4.

PRs