Skip to content

2.9.4

Choose a tag to compare

View all tags
@acdcnow acdcnow released this 21 Sep 22:13
· 5 commits to master since this release
v2.9.4
c8e946c

2.9.4 — fix: the integration could not connect

Fixed

  • Setup failed with "Failed to connect" — this was the blocking bug. The TCP port is now coerced to an integer before it is used in a device URL. The Home Assistant number selector always returns a float, so 2.9.3 requested
    http://<ip>:5333.0/pontos-base/... — a port that cannot exist — and every request failed.
  • Polling with retries could raise TypeError — the retry count reached range() as a float.
  • The settings dialog could not be opened — _make_schema() was called with an argument, raising TypeError in the options flow.
  • The connection test no longer requires a payload key starting with get; any non-empty response is accepted and the device's answer is logged at debug level.
  • configuration_url now shows the port without a trailing .0.
  • __pycache__ and *.pyc are ignored repo-wide (24 bytecode files that slipped into an earlier commit were removed).

Upgrade

Nothing to do: update through HACS (or replace custom_components/pontos) and restart Home Assistant.

Already added the device with 2.9.3? No reconfiguration is needed — the stored port is corrected when read, so the integration connects on the next start.

Verified

  • URL building, option coercion and both config/options schemas were executed against the real modules with stubbed Home Assistant imports (local Python 3.11 cannot run HA 2026.9, which requires 3.14).
  • All five device configurations' URL lists and all service endpoint templates format correctly with an integer port.
  • hassfest and the HACS validation pass on this commit.
Assets 2
Loading