You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The installation instructions can't be followed as written.
I already use HACS so it is installed.
But these instructions can't be followed because HACS -> Integrations doesn't exist:
In Home Assistant, go to HACS -> Integrations, click on + Explore & Download Repositories, search for Bradford White Connect, and click download. After download, restart Home Assistant.
Likewise, the "ADD INTEGRATION TO MY HOME ASSISTANT" button does not work.
I suspect that recent Home Assistant changes are responsible for the disparity.
My current Home Assistant version:
Core 2024.5.3
Supervisor 2024.05.1
Operating System 12.3
Frontend 20240501.1
Debug log
Not applicable, but the issue bot demands text here.
The text was updated successfully, but these errors were encountered:
Go to HACS then add "ablyler/home-assistant-bradford-white-connect" to custom repositories as an integration. Then download for HACS and restart Home Assistant. You will then see Bradford White Connect in the integrations to add in Devices and Settings.
Thanks @almoney! That is precisely what must be done until hacs/default#2391 is approved and merged. Do you mind putting up a PR to update the README.md with these instructions as well?
Version of the custom_component
Component not installed.
Configuration
Component not configured.
Describe the bug
The installation instructions can't be followed as written.
I already use HACS so it is installed.
But these instructions can't be followed because HACS -> Integrations doesn't exist:
Likewise, the "ADD INTEGRATION TO MY HOME ASSISTANT" button does not work.
I suspect that recent Home Assistant changes are responsible for the disparity.
My current Home Assistant version:
Core 2024.5.3
Supervisor 2024.05.1
Operating System 12.3
Frontend 20240501.1
Debug log
The text was updated successfully, but these errors were encountered: