Troubleshooting

Troubleshooting

The Hub Is Not Found

1. Wake and power the hub.
2. Move it closer to Home Assistant's Bluetooth adapter.
3. Fully close the official Weber app.
4. Select Scan Again.

Pairing Times Out

1. Press the physical hub button when it beeps.
2. Ensure no phone or tablet owns Bluetooth.
3. Keep the hub nearby for the full 90-second confirmation window.
4. Power-cycle the hub after a decline and retry.

No MQTT Entities

1. Check the panel footer for a publishing error.
2. Confirm the MQTT integration and broker are running.
3. Reload MQTT entities if discovery was enabled after the add-on started.

Cloud Pairing Is Still Waiting

1. Allow the full five-minute association window.
2. Keep the hub powered and connected to its existing Wi-Fi.
3. Confirm any physical prompt.
4. Select Test after setup completes.
5. If appliance access is denied, remove that failed identity and repeat the bridge-owned pairing flow.

Cloud Has No Current Reading

1. Confirm the official app displays a current probe temperature.
2. Start or resume a cook/recipe.
3. Wait one or two configured poll intervals.
4. An inactive session is intentionally reported as idle/stale.

The Phone Cannot Connect

Select Use Weber app, select Release Bluetooth, wait for Bluetooth available, then reopen the official app.

Recipe Guidance Is Missing

1. Confirm Weber app access is enabled and passes Test.
2. Start a guided recipe; a basic unguided probe target may not have an installed instruction program.
3. Confirm the hub is online so the live companion request can complete.
4. Review the panel's live-session error. REST probe history may continue even when the WebSocket is temporarily unavailable.
5. If probe telemetry remains current, missing guidance may be a Weber companion limitation. Report your redacted model, firmware, app version, and region so the compatibility matrix can grow.

Remote Controls Are Missing

1. Configure and test Weber app access.
2. Turn on Remote cook controls in Settings.
3. Confirm MQTT is connected and trusted.
4. Confirm/stop are unavailable when no active cook is present.

When reporting a bug, include the add-on version, Home Assistant version, hub model, and redacted logs. Never attach credentials or full captures publicly.