-
Notifications
You must be signed in to change notification settings - Fork 3
Troubleshooting
- Wake the hub.
- Keep it near a Home Assistant adapter or an active ESPHome Bluetooth proxy.
- Fully close the Weber app and turn off Bluetooth on every phone or tablet that uses the hub.
- Confirm an ESPHome proxy has active connections enabled and a slot free.
- Search again in Home Assistant.
The hub may be awake enough to advertise but not ready for a pairing request. Unplug any probe, hold the hub button for about ten seconds to restart it, then retry. A proxy can need up to 90 seconds to establish the first connection.
Keep the app closed and phone Bluetooth off, wake the hub, and retry using the prepared private connection. No Home Assistant config entry is saved after a failed attempt.
- Turn off phone or tablet Bluetooth.
- Open the Weber app and confirm the hub remains online through Wi-Fi.
- If the app also shows the hub offline, restore the hub's Wi-Fi before retrying.
- Confirm Home Assistant has internet access.
- Use Check Weber Cloud again. Each check may wait up to five minutes; the hub does not need another approval.
Unknown is expected for an empty slot or sleeping hub. Wake the hub and insert
the probe. If the hub is active, allow at least one 10-second update interval.
All four entities intentionally remain visible.
Confirm the integration is in Phone + Home Assistant mode. Home Assistant only owns the hub's single Bluetooth connection and cannot share it with the app. After changing modes, reopen the app.
Home Assistant will retry automatically. Check the ESPHome proxy page for its active connection count. If a slot remains stale after an interrupted test, restart the proxy; do not copy its key or configure it directly in this integration.
Update to 3.0.2 and restart Home Assistant. Routine hub sleep, power-off, Wi-Fi loss, and temporary cloud outages now recover quietly without raising a repair; the restart also clears every retired connection-loss repair, including one left behind by an earlier deleted integration entry.
The only repair 3.0.2 creates means Weber rejected Home Assistant's generated companion credential. That condition cannot recover by retrying, so follow the repair to remove the entry and pair the integration again.
Include the integration and Home Assistant versions, Weber model and firmware, official app platform/version and region, and adapter or ESPHome proxy details. Describe which of discovery, physical pairing, cloud association, phone coexistence, local reads, and proxy failover succeeded.
Do not post MAC addresses, appliance or companion IDs, passwords, tokens, account details, packet captures, config-entry exports, or unredacted diagnostics.