Lots of HA problems after full SD card

Configuration
1

Hi all,

Last weekend I noticed that some automations did not work anymore. I had a lot of errors but I found out that my SD card was full. This was caused by my “home-assistant_v2.db” file. This was over 4GB’s. So I stopped HA with the “systemctl stop” command, deleted the .db file, and started HA again. After that and some reboots/HA restarts the most stuff started working again. However, I still have some problems. After a restart I get this errors in my log:

Log Details (ERROR)
Mon Feb 04 2019 16:05:46 GMT+0100 (Central European Standard Time)

Error while setting up platform spotify
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/lib/python3.5/asyncio/tasks.py", line 400, in wait_for
    return fut.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/media_player/spotify.py", line 85, in setup_platform
    token_info = oauth.get_cached_token()
  File "/srv/homeassistant/lib/python3.5/site-packages/spotipy/oauth2.py", line 132, in get_cached_token
    token_info = json.loads(token_info_string)
  File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

And this one:

Log Details (ERROR)
Mon Feb 04 2019 16:05:52 GMT+0100 (Central European Standard Time)

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/tasks.py", line 241, in _step
    result = coro.throw(exc)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/cloud/__init__.py", line 256, in async_start
    info = await self.hass.async_add_job(load_config)
  File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/cloud/__init__.py", line 254, in load_config
    return json.loads(file.read())
  File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

And I get this error for 3 of my Zwave devices:

Z-Wave node 7 not ready after 30 seconds, continuing anyway

I tried some things like “Heal network” and “Soft reset” in my Zwave config panel, but no results there.

2

coincidence nothing more. Unrelated to the SD card being full. The z-wave node thing is also normal and the devices will come alive after a few minutes.

Sounds like you need to suppress your logging. I only log critical errors in the HA logs. Example setup:

logger:
  default: error
  logs:
    #for this item anything below error will not be logged
    requests.packages.urllib3.connectionpool: critical 
    py.warnings: critical

FYI

first error is related to a response from spotify being malformed.

Your second error is related to a response from the could being malformed.

3

Yes, I agree that I have to log less stuff.

It might be coincidence, I can’t now for sure. But fact is that I never experienced this error before, and I am using Zwave for years now. And yes, it is normal that the Zwave devices come alive after a few minutes, but the ones that report an error don’t come up. It’s 3 days ago now.