-
Notifications
You must be signed in to change notification settings - Fork 3
Installation and Setup
- Home Assistant with add-on support
- A Bluetooth adapter available to the Home Assistant host
- MQTT integration and a broker such as Mosquitto
- A powered Weber Connect Hub
- Internet access for the recommended phone + Home Assistant setup
Add this repository in Settings > Apps > Install app > Repositories:
https://github.com/ProspectOre/weber-connect-home-assistant-addon
Older Home Assistant versions may use Settings > Add-ons > Add-on Store.
Install and start Weber Connect for Home Assistant (Unofficial), then open its Web UI.
- Wake the hub and keep it near Home Assistant's Bluetooth adapter.
- Fully close the official Weber app so it releases Bluetooth.
- Select Set Up My Hub.
- Press the hub's physical button when it beeps.
- Keep the hub powered and online while Weber publishes the association. This can take up to five minutes.
- Wait for Connected.
The bridge registers its own private companion before BLE pairing and presents that same identity to the hub. Local and cloud access therefore complete with one setup action and one physical confirmation. No Weber login or phone secret is required. Local only remains available for users who explicitly do not want the cloud route.
The add-on publishes four stable probe slots automatically. Empty slots remain
available with No probe state so entity IDs do not change when probes are
inserted or removed.
Select the pencil beside any slot to add an optional nickname. The panel and Home Assistant always retain the number—for example, Brisket · Probe 1—and the MQTT unique ID does not change when a nickname changes.
Fresh installs use the Live · 10 sec local read interval. Existing installs keep their saved interval until it is changed in Settings.
Each probe slot exposes:
- Temperature
- State
- Battery when supported by the probe
With Weber app access configured, the same MQTT device also creates entities for active cook guidance, progress, cavity temperatures, and timers. Those values populate only when Weber returns live-session details to the bridge companion. Remote-control entities do not appear unless Remote cook controls is explicitly enabled in Settings.
The panel footer reports whether MQTT discovery and state publishing are working.