Hanging on start up on version 0.77.3

I use lots of nest protects but don’t have a camera. On start up home assistant is hanging saying “Setting up camera.nest”.

Any idea how I can stop this happening? I’ve just upgraded to 0.77.3 and it is still happening.

I have commented out the nest component in my config and that didn’t fix it. Then I commented out the cameras and now I’m hanging on another part.

This is the first start since upgrading - so maybe its the DB migration but will that really take 20 mins? Or is that worst case on a pi or similar?

I also ctrl-c and tried again a few times (I’m impatient!) wonder if that can kill the migration if it is that?

I’ve deleted the sqlite file as well - and still seems to hang.

I can’t login using my password which either means the new auth is stopping me or home assistant hasn’t started up.

I can’t see anything going through the logs and usually i’d see state updates flowing through.

Any ideas?

My migration took about an hour and I’m on a home server, not a raspberry…
Might be quit long.

Even if I deleted the sqlite db?

Does it log saying “starting migration” or does it just look like it hangs?

So eventually it seems my installation kicked into some form of life… 16 hours later - has anyone seen this? could the pychromecast really be the cause or something else?

2018-09-05 10:29:25 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=switch>
2018-09-06 02:36:53 WARNING (Thread-5) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-09-06 02:36:53 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.chromecast_video, old_state=<state media_player.chromecast_video=off; friendly_name=Chromecast Video, supported_features=21437 @ 2018-09-05T10:29:19.836012+01:00>, new_state=<state media_player.chromecast_video=unavailable; friendly_name=Chromecast Video, supported_features=21437 @ 2018-09-06T02:36:53.544656+01:00>>

So restarting again is now quick - so maybe it was the migration but wouldn’t it usually log a line to say the migration is starting?