Lost web access after reboot (do not have Owntracks): Fixed

Configuration
1

Hassio Version: 0.84.5 running in VM.
A few days ago I tried upgrading it to 0.84.6, but I lost the web access right after (the system was still working). Luckily I have snapshots of the VM so rolling it back was easy, though the cpu usage was extremely high (100%) after it came back. If I restart hassio, I’d lose the access again.

Took me a day to figure our a way to fix it (deleting auth, auth_provider.homeassistant and onboarding from .storage folder), but it always comes back after a restart.

Has anyone experienced this issue? I am having a difficult time finding the root cause.
here is the relevant part from the log:

2018-12-26 18:29:23 INFO (SyncWorker_2) [homeassistant.components.zwave] Z-Wave polling interval set to 60000 ms
2018-12-26 18:29:23 INFO (SyncWorker_0) [pyhap.accessory_driver] Starting accessory Home Assistant Bridge on address 192.168.86.251, port 51827.
2018-12-26 18:29:23 ERROR (MainThread) [homeassistant.setup] Error during setup of component hassio
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/setup.py”, line 145, in _async_setup_component
hass, processed_config)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/hassio/init.py”, line 181, in async_setup
user = await hass.auth.async_get_user(data[‘hassio_user’])
File “/usr/local/lib/python3.6/site-packages/homeassistant/auth/init.py”, line 114, in async_get_user
return await self._store.async_get_user(user_id)
File “/usr/local/lib/python3.6/site-packages/homeassistant/auth/auth_store.py”, line 69, in async_get_user
await self._async_load()
File “/usr/local/lib/python3.6/site-packages/homeassistant/auth/auth_store.py”, line 277, in _async_load
self._store.async_load(),
concurrent.futures._base.CancelledError

2

Troubleshooted for 4 days (and 3 hours per day), I finally got this fixed.
Issues was related to Bluetooth: I have 3 miflora sensors and one of the plants were moved away from the room hence it was out of range. Figured this out by disabling all bluetooth related sensors first. Adding them back one by one, eventually it was clear. Moved the plant back to the room and all is good .

3

I have the same problem, started after adding a MiFlora bluetooth sensor. Though mine is in range I still have to delete all the auth files and recreate users after any restart.

Disabling the bluetooth devices, rebooting, then re-adding them also cleared up the problem for me. Thanks for the info!