v0.2.0

v0.2.0 - 2026-05-05

Added

• Homebridge REST API authentication: the config flow now asks for a username and password, which are stored in the config entry and used to obtain a JWT access token from the Homebridge API (POST /api/auth/login). Credentials are validated during setup.
• Update sensor – Homebridge (update.homebridge_homebridge_update): reports whether a Homebridge core update is available, showing the installed and latest versions. Data is sourced from GET /api/status/homebridge-version.
• Update sensor – Homebridge UI (update.homebridge_homebridge_ui_update): reports whether a Homebridge UI (homebridge-config-ui-x) update is available. Data is sourced from GET /api/plugins.
• Update sensor – Plugins (update.homebridge_plugins_update): reports whether any installed Homebridge plugin has an update available. The sensor state is on when one or more plugins are outdated; the plugins_with_updates attribute lists each plugin name together with its installed and latest version.
• Token refresh: the coordinator automatically re-authenticates when it receives an HTTP 401 response, so the integration keeps working when the JWT access token expires.

Changed

• Coordinator now returns a structured HomebridgeData typed dictionary instead of a plain bool; the connectivity binary sensor reads data["connected"].
• Config flow initial step extended with username and password fields. An invalid_auth error is shown when the supplied credentials are rejected by Homebridge.