Weber Connect Unofficial 3.1.2

What changed

• Added one-click HACS installation with a manual custom-repository fallback while the default listing is queued.
• Added focused setup, troubleshooting, diagnostics, and removal guidance.
• Added normal- and high-DPI transparent brand assets with release-contract validation.
• Refreshed repository metadata and HACS-facing presentation.
• Scoped the unchanged-runtime evidence exception specifically to presentation-only release 3.1.2, so future releases require matching fresh evidence by default.

Runtime

There are no integration runtime behavior changes from 3.1.1.

Validation

• 130 tests passed with 95.66% combined statement/branch coverage.
• Ruff, strict mypy, Bandit, pip-audit, and actionlint passed.
• HACS, Hassfest, CodeQL, and the native integration release gate passed on the tagged commit.
• The post-review correction passed an exact-head Codex review with no findings.

Upgrade

Upgrade through HACS and restart Home Assistant when prompted.

Weber Connect Unofficial 3.1.1

What changed

• Prevent partial appliance-status frames from clearing stable hub telemetry.
• Preserve battery, charging, Wi-Fi, cloud status, and device state across transient reconnects and sustained cloud outages.
• Require fresh appliance data before republishing fuel and version fields after reconnect.
• Continue clearing live cook and probe values when connectivity is lost.

Validation

• 130 native integration tests passed with 95.66% combined statement/branch coverage.
• Ruff, strict mypy, Bandit, pip-audit, actionlint, Hassfest, HACS, and CodeQL passed.
• Live Home Assistant validation recorded zero post-baseline hub telemetry dropouts, versus 47 synchronized dropouts before the fix.
• Corrective follow-up passed a clean Codex review with no findings.

Upgrade

Upgrade to 3.1.1 through HACS, then restart Home Assistant when prompted.

Weber Connect Unofficial 3.1.0

What changed

• Added capability-driven hub battery and charging entities, including the battery level requested in #42.
• Added available Wi-Fi, cloud, device-state, fuel, grill-control, timer, burner, wireless-probe, and firmware telemetry.
• Preserved stable entity identities while allowing newly reported capabilities to appear dynamically.
• Prevented stale idle probe timing fields from creating a misleading countdown entity.
• Expanded diagnostics, translations, protocol coverage, and lifecycle regression tests.

Production validation

• 127 tests passed with 95.65% combined statement/branch coverage.
• Native integration, HACS, Hassfest, CodeQL, Ruff, strict mypy, Bandit, pip-audit, actionlint, and release-contract checks passed.
• The exact 3.1.0 candidate was validated on Home Assistant 2026.8.1 running on Home Assistant Yellow with a live Weber Connect Hub.
• Battery telemetry changed live from 65% to 70%; charging, Wi-Fi, cloud, device state, firmware, and probe telemetry were verified.
• Core restart and config-entry reload completed with stable entity IDs and no Weber warning/error log entries.

Upgrade

Update to 3.1.0 in HACS and restart Home Assistant. Only entities supported by telemetry reported by your Weber device are created.

Weber Connect Unofficial 3.0.7

What changed

• The No Weber hub found screen now explains that initial setup requires a connectable Bluetooth path, even when Weber Cloud will be used afterward.
• The screen now gives the complete recovery path: close the Weber app, turn off Bluetooth on phones and tablets that use the hub, wake the hub, and use a nearby Home Assistant adapter or an active ESPHome Bluetooth proxy with a free connection slot.
• Added a regression contract so this required setup guidance remains present.

This is a guidance-only release. Runtime discovery and connection behavior are unchanged.

If setup cannot find your hub

1. Update to 3.0.7 in HACS and restart Home Assistant.
2. Fully close the Weber app and turn Bluetooth off on every phone or tablet that uses the hub.
3. Wake the hub/controller.
4. Confirm a nearby Home Assistant Bluetooth adapter or ESPHome Bluetooth proxy is online.
5. If using a proxy, confirm active connections are enabled and a connection slot is free.
6. Add the integration and search again.

After setup, Phone + Home Assistant cloud mode does not require the hub to remain in Bluetooth range.

Prompted by this Home Assistant community report.

Weber Connect Unofficial 3.0.6

What changed

• Fixed missing Grill temperature readings on affected appliances, including the Weber EXP325S, by preserving a valid cavity display temperature when optional per-unit tags are absent.
• The normalized grill temperature now prefers the actual cavity reading and falls back to the display reading only when needed, across Bluetooth and cloud connections.
• Reviewed fork contributions can now satisfy the required review gate while still requiring an explicit maintainer merge.

Contributor

Thanks to @jarnose for reporting the cavity-temperature issue and contributing the fix in #36.

Full changelog: v3.0.5...v3.0.6

Weber Connect Unofficial 3.0.5

What changed

• Pairing setup now states that approval happens on the physical Weber hub, not in the Weber app.
• Standalone Smart Grilling Hub users are told to wait for all four probe indicators and press down once on the top/display within 60 seconds.
• Grill-controller users are directed to press the dial or confirmation control when prompted.
• Retry guidance now repeats the physical confirmation instructions after TIMED_OUT and other incomplete pairing attempts.

Why

Issue #34 confirmed that the previous wording led users to search for an approval action inside the Weber app even though Bluetooth pairing was working correctly. This release makes the required physical action explicit.

There is no pairing protocol or runtime behavior change. Existing installations do not need to re-pair.

#34

Full changelog: v3.0.4...v3.0.5

Weber Connect Unofficial 3.0.4

What's changed

• Probe 1 and Probe 2 remain the baseline entity set.
• Probe 3 and Probe 4 now appear only after the controller reports those slot numbers, avoiding unused entities on two-port models.
• Optional probes keep their stable slot-based entity IDs and remain available as Unknown during normal idle periods after discovery.
• Documentation now describes model-aware probe support instead of a fixed four-probe contract.

Why

The Performer Deluxe/Premium Smart reporter in issue #24 confirmed that the model has two physical probe ports. Version 3.0.4 adapts the entity surface to the slots each controller actually reports while retaining support for controllers with Probe 3 and Probe 4.

Any probe entities you manually disabled remain disabled after the update.

#24

Full changelog: v3.0.3...v3.0.4

Weber Connect Unofficial 3.0.3

What's changed

• Added a native Grill temperature entity for appliances that report a built-in cavity/ambient sensor.
• The entity appears automatically after the appliance sends its first valid built-in temperature, so standalone Connect Hubs do not gain an unsupported entity.
• Added the normalized grill temperature to privacy-safe diagnostics.

Performer Smart testing requested

Support uses the current cavity-temperature field that the integration already decoded, but the diagnostics in issue #24 were captured while the grill was disconnected. Performer Deluxe/Premium Smart owners can help confirm the model-specific behavior:

1. Update through HACS and restart Home Assistant.
2. Wake the grill and start an active cook so its built-in temperature is visible in the Weber app.
3. Look for Grill temperature on the Weber device page.
4. If it does not appear or is incorrect, enable debug logging for the integration, reproduce the problem while the grill remains active, then attach the downloaded debug log and fresh integration diagnostics to issue #24.

#24

Full changelog: v3.0.2...v3.0.3

Weber Connect Unofficial 3.0.2

What changed

• Connection is enabled by default and reports Connected or Disconnected, identifies Weber Cloud or Bluetooth, and uses a transport-aware icon.
• Last successful update is enabled by default and preserves the exact time fresh hub data most recently arrived, including while the hub sleeps or is powered off.
• Every retired connection-loss repair is removed when the integration starts, including stale repairs tied to an earlier deleted config entry.
• The established four permanent probe-temperature entities and their stable IDs remain unchanged.

Update

Update Weber Connect Unofficial through HACS, then restart Home Assistant. No re-pairing or configuration changes are required. The two new context entities appear automatically, and the obsolete connection-loss repair is removed during startup.

Validation

The release passed 110 tests with 96.06% combined statement and branch coverage, HACS validation, Hassfest, strict typing, security scanning, dependency auditing, CodeQL, Actionlint, and the full release contract.

Weber Connect Unofficial 3.0.1

What changed

• Sleeping, powered-off, or temporarily unreachable hubs no longer raise Home Assistant repair issues.
• All four probe entities remain visible and show Unknown while the hub is unavailable.
• The integration continues retrying quietly and resumes readings automatically when the hub returns.
• Connection-loss repair records created by 3.0.0 are cleared when 3.0.1 starts.
• A repair is still raised when Weber rejects Home Assistant’s generated companion credential, because that condition requires pairing again.
• The pinned WebSocket runtime is updated from 16.1 to 16.1.1.

Update

Update Weber Connect Unofficial through HACS, then restart Home Assistant. No re-pairing or configuration changes are required.

Validation

The release passed 108 tests with 95.77% combined statement/branch coverage, HACS validation, Hassfest, strict typing, security scanning, dependency auditing, CodeQL, and the full release contract.