v0.2.2 — new screenshots

Documentation only — the integration itself is unchanged from 0.2.1.

Changed

• New screenshots. The old pair predated the rename to Weber Connect and the appliance-details step: they showed the title "Weber Spirit / June", generic device info and a setup form without the Companion id field. The new shots come from a live install — model and serial read from the cloud, the brand icon, current sensor values, and the config flow as it stands today. Rendered at 2x for HiDPI; the serial number is masked and the README says so.

Full changelog: https://github.com/jrx-code/hassio-integration-weber/blob/main/CHANGELOG.md

v0.2.1 — HACS packaging

Packaging only — no functional change to the integration. If you are on 0.2.0, nothing about your entities or config entry changes.

Changed

• HACS validation now runs the full check set, brands included — it passes on the brand assets shipped inside custom_components/weber_june/brand/.
• README leads with an Install section (HACS and manual), My Home Assistant one-click links, badges and a link to the changelog.
• Issue templates ask for versions and warn against pasting refresh tokens, appliance ids, companion ids or serial numbers — the diagnostics download redacts those for you.

Removed

• info.md. HACS 2.x renders the README and no longer reads an info file, so it was a second copy of the description that nothing displayed.

Full changelog: https://github.com/jrx-code/hassio-integration-weber/blob/main/CHANGELOG.md

v0.2.0 — Weber Connect

Renames the integration to Weber Connect, gives it a proper icon, and makes a
retired refresh token recoverable from the UI.

Added

• Brand icon and logo — shipped in custom_components/weber_june/brand/, so
  Home Assistant serves them locally; no home-assistant/brands PR needed.
• Reauth flow — the cloud can retire a refresh token. When that happens the
  entry now asks for a new one instead of retrying forever, and the device, its
  entities and their history are kept.
• Appliance model and serial from the cloud — device name, model, model id and
  serial number are read from GET /2/devices/{companionId}/associated instead of
  being hardcoded. Optional: leave Companion id empty and generic info is used.
• Reconfigure step — an existing entry can gain a companion id without being
  removed and re-added.
• Diagnostics — dumps the raw REST snapshot and a full field inventory of the
  last companion frame, including fields the integration does not decode.
  Appliance, session and probe identifiers are redacted.
• Cook mode table in the README, mapping the raw values (0–10) to the cloud's
  own names.

Fixed

• Rotated refresh tokens are now persisted. The client adopted a rotated token
  in memory only, so a restart fell back to one the cloud had already retired and
  authentication failed. The README's claim that the token "does not rotate" was
  wrong and has been corrected.

Notes

Still read-only, still single-session (cannot run alongside the official app), and
the probe target remains unavailable — the cloud does not carry it.

v0.1.0 — first release

First release of the Weber Spirit / June integration.

• Cavity temperature + target (setpoint), probe temperature(s), connection, mode
• App-free (cloud), no companion app or Android VM
• Zero external dependencies (Python stdlib only)
• Read-only; single-session (cannot run alongside the official app)
• Client credentials via environment (WEBER_CLIENT_ID / WEBER_CLIENT_SECRET) or a config-dir file

Install via HACS as a custom repository (category: Integration). See the README.