Skip to content

Installation and Setup

Jump to bottom
pickaxe edited this page Jul 22, 2026 · 6 revisions

Installation and setup

Requirements

  • Home Assistant 2026.7.0 or newer
  • HACS
  • A connectable Home Assistant Bluetooth adapter or active ESPHome Bluetooth proxy in range during setup
  • Home Assistant internet access
  • A hub already online in Weber Cloud

An ESPHome proxy must have bluetooth_proxy.active enabled and at least one connection slot available. The integration does not need the proxy's address, encryption key, or credentials; Home Assistant owns proxy selection.

Install with HACS

  1. Open HACS → Integrations → ⋮ → Custom repositories.

  2. Add the following repository with category Integration:

    https://github.com/ProspectOre/weber-connect-unofficial

  3. Download Weber Connect Unofficial and restart Home Assistant.

  4. Open Settings → Devices & services. Select the discovered Weber hub, or choose Add integration → Weber Connect Unofficial.

No MQTT broker or Home Assistant add-on is required.

Pair the hub

  1. In the Weber app, turn off Bluetooth on the phone or tablet and confirm the hub still appears online. If it becomes offline, restore the hub's Wi-Fi before continuing.
  2. Fully close the Weber app. Leave Bluetooth off on every phone or tablet that uses the hub so none can reclaim its single Bluetooth connection.
  3. Wake the hub and continue setup in Home Assistant. The route displayed by Home Assistant identifies the selected local adapter or active ESPHome proxy.
  4. A proxy may need up to 90 seconds to open the first connection. When the hub asks, approve Home Assistant within 60 seconds.
  5. Home Assistant then waits for Weber Cloud to publish the new association. This can take up to five minutes and advances automatically.
  6. After setup completes, turn phone or tablet Bluetooth back on and reopen the Weber app.

Setup generates a private companion for Home Assistant. It never asks for the user's Weber account password or copies a credential from the official app.

Native entities

The device contains exactly four temperature entities: Probe 1 through Probe 4. Probe state, type, and battery level—when reported—are attributes of the same temperature entity rather than additional entities.

Two context entities are also enabled by default. Connection reports the current Connected or Disconnected state and Weber Cloud or Bluetooth method. Last successful update records when fresh hub data most recently arrived.

Optional nicknames retain the physical number, such as Brisket · Probe 2, and do not change the entity's stable unique ID.

Replacing the 2.1 add-on

Version 3.0 is a clean native integration, not an in-place add-on upgrade.

  1. In the 2.1 panel, use Forget This Hub.
  2. Stop and uninstall the old add-on.
  3. Install and pair the native integration using the steps above.
  4. If the old MQTT device remains unavailable, remove its retained discovery records from the broker and delete that MQTT device from Home Assistant.

The native integration does not import the add-on's MQTT entities or settings.

Weber Connect Unofficial

Source repository

Clone this wiki locally