Config flow could not be loaded
See original GitHub issueSystem Health details
System Health
version | core-2021.6.5 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
virtualenv | false |
python_version | 3.8.9 |
os_name | Linux |
os_version | 5.10.42 |
arch | x86_64 |
timezone | America/New_York |
Home Assistant Cloud
logged_in | true |
---|---|
subscription_expiration | July 16, 2021, 8:00 PM |
relayer_connected | true |
remote_enabled | true |
remote_connected | true |
alexa_enabled | false |
google_enabled | true |
can_reach_cert_server | ok |
can_reach_cloud_auth | ok |
can_reach_cloud | ok |
Home Assistant Supervisor
host_os | Home Assistant OS 6.0 |
---|---|
update_channel | stable |
supervisor_version | supervisor-2021.06.3 |
docker_version | 20.10.6 |
disk_total | 30.8 GB |
disk_used | 3.9 GB |
healthy | true |
supported | true |
board | ova |
supervisor_api | ok |
version_api | ok |
installed_addons | Mosquitto broker (6.0.1), Visual Studio Code (3.4.1), Samba share (9.5.1), Tor (3.0.5), Google Assistant SDK (2.5.0), Example (4.1.0), SSH & Web Terminal (8.2.4) |
Lovelace
dashboards | 2 |
---|---|
resources | 0 |
views | 3 |
mode | storage |
Checklist
- I’m running the newest version of HACS https://github.com/hacs/integration/releases/latest
- I have enabled debug logging for my installation.
- I have filled out the issue template to the best of my ability.
- I have read https://hacs.xyz/docs/issues
- This issue is related to the backend (integration part) of HACS.
- This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
Describe the issue
Trying to install HACS on HA hosted on Virtual machine(Virtual box).
I ended up copying the files manually to the config folder through samba. Now, I could search HACS but when I try to install it it gives me the above error.
I tried restarting my vm, HA, PC, I made sure the updated version of hacs file is downloaded.
Reproduction steps
- I tried restarting my vm, HA, PC,
- I made sure the updated version of hacs file is downloaded.
…
Debug logs
aa
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
HACS installing problem via integration "error: Config flow ...
Is there a solution for this bug? Have the same problem: “Config flow could not be loaded” after following the installation steps for...
Read more >"config flow could not be loaded" : r/homeassistant - Reddit
Vanilla install of latest version on a Raspi 3. I'm getting "config flow could not be loaded" when trying to add my first...
Read more >Home Assistant | Dose any 1 know why config flow could not ...
Occasionally have a zigbee2mqtt device hang and get stuck sometimes a lightbulb, sometimes a radiator valve. A reboot of HASS doesn't solve it,...
Read more >Config flow could not be loaded: undefined (Deconz) #68165
The problem I am continually getting the following error after any system update to the HA system. Then when you click on configure...
Read more >How to Set Up Tuya Integration (Stable) in Home Assistant
I got an error saying 'Config flow could not be loaded' when setting up the Tuya ... for your cloud project cannot serve...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like the installation process takes a long time. If you are accessing the home assistant using reverse proxy, the reverse proxy would throw 504 Gateway Time-out when the origin server doesn’t respond for some time. You can see this on the devtool’s Network tab. And you’ll see the error “Config flow could not be loaded”
Great! that makes sense @aygee 👍 so for anyone else that gets this, use local access with an IP address, or try multiple times.