Got a reply on the GitHub. Here is the fix:
If it detects, go stand by the Weber Connect Hub and add it. Then, when you see the Bluetooth Icon Light, click on the Connect Hub to accept the pairing.
I have wanted this for YEARS!!! Thank you!!!
Got a reply on the GitHub. Here is the fix:
If it detects, go stand by the Weber Connect Hub and add it. Then, when you see the Bluetooth Icon Light, click on the Connect Hub to accept the pairing.
I have wanted this for YEARS!!! Thank you!!!
Planning a test tomorrow, should i use version 2.0 or 3.0?
I am using 3.0.5, which is the latest.
Version 3.0.5 installed (earlier/cloud versions deleted). I canât add the integration anymore. Message: Home Assistant cannot currently see a connectable Weber hub.
Thanks for testing, @Sander_van_den_Broek. Version 3.x, like 2.x, requires a connectable Bluetooth path during initial setup, even if you plan to use Weber Cloud afterward. Neither version asks for a Weber account sign-in: setup creates a private cloud-companion identity and pairs it with the physical hub over Bluetooth.
Iâve released 3.0.7 to make this explicit on the No Weber hub found screen.
Please:
After setup, Phone + Home Assistant cloud mode does not require the hub to remain in Bluetooth range.
If it still cannot find the hub, please open a GitHub issue and include your Home Assistant version and installation type, Weber model and firmware, Bluetooth adapter/proxy details, relevant logs, and whether the hub appears in Home Assistantâs Bluetooth advertisement monitor. That will keep diagnosis and any code fix traceable.
Update: Weber Connect Unofficial 3.1.0 is now available.
View the 3.1.0 release and notes
Whatâs new:
To upgrade, update to 3.1.0 in HACS and restart Home Assistant. Newly supported entities will appear only when your hub reports the corresponding telemetry.
Battery reporting was tracked in GitHub issue #42. If your Weber model exposes telemetry that is still missing, please open a GitHub issue with the model, firmware version, and diagnostics.