-
Notifications
You must be signed in to change notification settings - Fork 3
Cloud Pairing and Phone Handoff
The Weber hub accepts one active Bluetooth client. Version 3.0 provides two explicit connection modes so users can decide who owns that connection.
Home Assistant keeps one generated Weber companion WebSocket open and requests fresh status on a 10-second cadence. The official Weber app remains free to own Bluetooth, so both can show the current probe temperature at the same time. The enabled Connection entity identifies Weber Cloud as the active method, and Last successful update shows when fresh data most recently arrived.
Start and manage recipes in the Weber app as usual. Home Assistant follows the four probe temperatures; it does not import recipe text, instructions, targets, timers, or cooking controls.
The private companion is created automatically during physical-confirmation setup. There is no Weber account-login form, manual secret, or phone extraction step.
Home Assistant keeps one local GATT connection open through the adapter or active ESPHome proxy selected by its Bluetooth manager. This avoids Weber Cloud traffic after setup, but the official app cannot use the hub's Bluetooth connection at the same time.
Initial setup still requires Home Assistant internet access and a working hub-to-Weber Cloud path, even when this mode will be selected afterward.
Open Settings → Devices & services → Weber Connect Unofficial → Configure. Choose the connection mode and submit. Home Assistant closes the current transport before starting the other one.
There is no automatic fallback between cloud and Bluetooth. This is deliberate: silently taking Bluetooth would disconnect the phone in the recommended mode.
Deleting the config entry removes the local companion credential, device, and entities. Weber exposes no supported companion-revocation endpoint, so an unused server-side companion record may remain.