HA broke after update (logbook, mobile_app, default_config)

Configuration
1

I did a regular update yesterday and since then massive errors like:

The following integrations and platforms could not be set up:

* [logbook](https://www.home-assistant.io/integrations/logbook)
* [mobile_app](https://www.home-assistant.io/integrations/mobile_app)
* [default_config](https://www.home-assistant.io/integrations/default_config)

Please check your config.

Is there a “reset something” step which needs to be done after every update? ~/.homeassistant/.storage/core.device_registry has garbage in it (literally chunk of random crap at the end), I fixed that and things got better but still getting there errors.

Also, getting Sep 25 11:39:47 aikhass hass[1970]: 2020-09-25 11:39:47 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook d5f8a711a313d79810eaec84362e46100ec2d89e32804168a42ffdeb771cb44e from 192.168.10.95 - what is with that?

And one more:
Sep 25 11:51:58 aikhass hass[2161]: 2020-09-25 11:51:57 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ as_timestamp(states.sun.sun.attributes.next_setting) | timestamp_custom('%-H:%M') }}") - was working fine for ages, what changed?

Wow it is even better - the templates from the “templates” tool in devtools fails to parse the default template.

2

I’ve received these as well. I have not investigated but I assumed there is an inbound call being mistakenly rendered as a webhook request. I still need to check mine out.

You didn’t mention what HA flavour you have. I assume HA Core (Python venv)?

3

yes it is python venv.

4

Check breaking changes, specifically the one about templates

6

https://www.home-assistant.io/blog/2020/09/17/release-115/#release-01152---september-19 does not mention anything which would break template. Neither says that /developer-tools/template is expected to be broken :slight_smile:

8

reinstalling everything seems have fixed things, this thread can be deleted as there is no way to debug this broken upgrade any further…