-
Notifications
You must be signed in to change notification settings - Fork 3
Recipes and Home Assistant
The integration creates one permanent temperature entity for each physical probe slot:
- Probe 1
- Probe 2
- Probe 3
- Probe 4
A connected probe shows its temperature. Probe state, type, and battery level when available appear as attributes on that same entity. Optional nicknames always retain the physical slot number.
An empty probe slot or sleeping hub shows Unknown with the probe-off icon.
The entity remains present so dashboards and automations keep stable IDs.
Two additional entities are enabled by default:
- Connection shows Connected or Disconnected and identifies whether the integration is using Weber Cloud or Bluetooth.
- Last successful update retains the timestamp of the most recent fresh hub data, even during normal hub sleep or power-off.
Keep the integration in Phone + Home Assistant mode for normal use. Start a recipe, set a target, and manage the cook from the official Weber app. Home Assistant continues receiving current probe temperatures through its private cloud companion while the app uses Bluetooth.
The tested app and Home Assistant readings matched after normal unit rounding during an active cook. The final cloud endurance run remained connected for more than 70 minutes with the app open and a recipe active.
- Recipe title or installed-program details
- Guided instructions or current step
- Targets, progress, mode, or doneness
- Cavity temperatures
- Timers
- Confirm, stop, start, reset, ignition, or other cooking controls
- Wi-Fi or grill-mode configuration
The integration is a dependable temperature source, not a second cooking controller. This narrow contract keeps entity behavior stable across Weber models and private-cloud response differences.