Hassbian Stopped Working

Was working fine for about 5 days. Added dark sky tags to configuration.yaml. Verified ok. Now, can’t get into it. Here are the errors when I do a status command:

  • [email protected] - Home Assistant for homeassistant
    Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: ena
    Active: failed (Result: exit-code) since Tue 2018-04-24 19:32:25 EDT; 51s ago
    Process: 511 ExecStart=/srv/homeassistant/bin/hass (code=exited, status=1/FAILURE)
    Main PID: 511 (code=exited, status=1/FAILURE)

Apr 24 19:32:25 hassbian hass[511]: File "/srv/homeassistant/lib/python3.5/site-packages/requests/__in
Apr 24 19:32:25 hassbian hass[511]: from . import utils
Apr 24 19:32:25 hassbian hass[511]: File "/srv/homeassistant/lib/python3.5/site-packages/requests/util
Apr 24 19:32:25 hassbian hass[511]: from . import certs
Apr 24 19:32:25 hassbian hass[511]: File "/srv/homeassistant/lib/python3.5/site-packages/requests/cert
Apr 24 19:32:25 hassbian hass[511]: from certifi import where
Apr 24 19:32:25 hassbian hass[511]: ImportError: cannot import name ‘where’
Apr 24 19:32:25 hassbian systemd[1]: [email protected]: Main process exited, code=exi
Apr 24 19:32:25 hassbian systemd[1]: [email protected]: Unit entered failed state.
Apr 24 19:32:25 hassbian systemd[1]: [email protected]: Failed with result 'exit-code

I have no idea where to go from here.

Help!!!

Can you access configuration.yaml where you have add dark sky into it. If you can then remove the dark sky (what you have added in) and try reboot to see if home-asssitant can load normally.

For dark sky, if you can show your configuration for dark sky then we can check.

Thanks for your response…I am happy to say that I resolved the issue, though I had to do a complete re-install. Fortunately I backed up the yaml file.

Bill