Broken after 105.2 update

Configuration
1

Hi!
After updating to 105.2 ha doesn’t work anymore. I get:

Feb 08 17:29:49 cs hass[4939]: Exception in thread Thread-1:
Feb 08 17:29:49 cs hass[4939]: Traceback (most recent call last):
Feb 08 17:29:49 cs hass[4939]:   File "/usr/lib/python3.7/threading.py", line 926, in _bootstrap_inner
Feb 08 17:29:49 cs hass[4939]:     self.run()
Feb 08 17:29:49 cs hass[4939]:   File "/usr/lib/python3.7/threading.py", line 870, in run
Feb 08 17:29:49 cs hass[4939]:     self._target(*self._args, **self._kwargs)
Feb 08 17:29:49 cs hass[4939]:   File "/usr/local/lib/python3.7/dist-packages/homeassistant/util/logging.py", line 85, in _process
Feb 08 17:29:49 cs hass[4939]:     self._queue.get(), self.loop
Feb 08 17:29:49 cs hass[4939]:   File "/usr/lib/python3.7/concurrent/futures/_base.py", line 433, in result
Feb 08 17:29:49 cs hass[4939]:     raise CancelledError()
Feb 08 17:29:49 cs hass[4939]: concurrent.futures._base.CancelledError
Feb 08 17:29:49 cs hass[4939]: /usr/lib/python3.7/asyncio/base_events.py:604: RuntimeWarning: coroutine 'async_search.<locals>.on_data' was never awaited
Feb 08 17:29:49 cs hass[4939]:   self._ready.clear()
Feb 08 17:29:49 cs hass[4939]: RuntimeWarning: Enable tracemalloc to get the object allocation traceback

any ideas?

2

Do you use any of the ‘breaking changes’ affected integrations?

3

that would be? any pointer to those?

4

Please read the blog post for 0.105.

5

Hmm, I don’t see any of those. If there is a problem it should also appear in the check_config shouldn’t it?
I downgraded to 105.1 and this one now just gets stuck on
(MainThread) [homeassistant.setup] Setting up logger
PS:
The only thing that I get from a config check is:
WARNING:homeassistant.components.group:The ‘view’ option (with value ‘True’) is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0

6

How long did you wait after updating? The update might take a while depending on your setup. I had to wait for 30+ minutes sometimes on a RPi3.

7

Yes actually 105.1 came up after a long time. having some issues with netatmo (see other thread) and haven’t tried 105.2 yet. Can it be the error message isn’t fatal?

8

I have no idea what you mean by that.

9

I had the same issue, from 104.x -> 105.2 and It was broken.

Downgrading to 105.1 fixed it right up.