core: Upgrade from 0.85.1 to 0.86.2 fails

Upgrade from within hass.io from 0.85.1 to 0.86.2 fails with the following error msg.

home-assistant   | 2019-01-25 22:23:18 INFO (MainThread) [homeassistant.core] Starting Home Assistant
home-assistant   | 2019-01-25 22:23:18 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
home-assistant   | Traceback (most recent call last):
home-assistant   |   File "/usr/local/lib/python3.6/site-packages/homeassistant/core.py", line 1106, in async_call
home-assistant   |     raise ServiceNotFound(domain, service) from None
home-assistant   | homeassistant.exceptions.ServiceNotFound: (ServiceNotFound(...), 'Service persistent_notification.create not found')
home-assistant   | 2019-01-25 22:23:18 INFO (MainThread) [homeassistant.core] Timer:starting

Reverting to 0.85.1 docker image fixes issue

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 19 (5 by maintainers)

Most upvoted comments

Solution… Remove every entry in every file where there is a double _ … f.e. date__time. Removed them in every file and it started up again like nothing ever happend.

https://www.home-assistant.io/blog/2019/01/23/release-86/#noteworthy-breaking-changes

``The following things are not allowed in entity IDs:

No capital letters No leading or ending underscores No double underscores

This issue also impacts the entity registry, which could contain in some cases invalid entity IDs. Expect entity IDs to change if they contained a double underscore (which becomes 1) or if they started/ended in an underscore (which will be removed).``

Daandamhuis on Jan 26, 2019

Also for me, deleting _ and the end of an unused entity_id( found in customize.yaml) was the solution.

fctpn on Jan 26, 2019

``The following things are not allowed in entity IDs:

No capital letters No leading or ending underscores No double underscores

Has anyone tested special characters? This was possibly one of the problems i had. info 3

Solution:

check all off your .yaml files if they have an (__) double underscore

scheric on Jan 26, 2019

Seems I made a mistake. I did find one entity that had a __ .
A device I had previously removed, but was still lurking in the entity registry.

Manual removal fixed issue.

ghost on Jan 26, 2019

Solution… Remove every entry in every file where there is a double _ … f.e. date__time. Removed them in every file and it started up again like nothing ever happend.

https://www.home-assistant.io/blog/2019/01/23/release-86/#noteworthy-breaking-changes

``The following things are not allowed in entity IDs:

No capital letters No leading or ending underscores No double underscores

This issue also impacts the entity registry, which could contain in some cases invalid entity IDs. Expect entity IDs to change if they contained a double underscore (which becomes 1) or if they started/ended in an underscore (which will be removed).``

You are right. I fixed a double underscore in one of the entities and it started up.

slipx06 on Jan 26, 2019