Home Assistant not working after upgrade to 0.86.4

Configuration
1

Hi Guys,

I face problem that after upgrade in Home assistant in virtual ENV, HA is not working… can you please help?

This is last mesage from log:

2019-01-29 20:45:31 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/lib/python3.5/asyncio/tasks.py”, line 239, in _step
result = coro.send(None)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py”, line 1106, in async_call
raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: (ServiceNotFound(…), ‘Service persistent_notification.create not found’)

This is what I’m doing after upgrade and reboot:

root@GSpot:~# sudo -u hass -H -s
hass@GSpot:/root$ source /srv/homeassistant/bin/activate
(homeassistant) hass@GSpot:/root$ hass
Config directory: /home/hass/.homeassistant
2019-01-29 21:20:10 ERROR (MainThread) [homeassistant.config] Invalid config for [homeassistant]: [group] is an invalid option for [homeassistant]. Check: homeassistant->group. (See /home/hass/.homeassistant/configuration.yaml, line 2).
2019-01-29 21:20:10 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2019-01-29 21:20:10 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/lib/python3.5/asyncio/tasks.py”, line 239, in _step
result = coro.send(None)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py”, line 1106, in async_call
raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: (ServiceNotFound(…), ‘Service persistent_notification.create not found’)
2019-01-29 21:20:10 INFO (MainThread) [homeassistant.core] Timer:starting

2

@Ivan_Galic
Did you check there are no double underscores in any entity names, both in YAML and Core Registry files?
Same token, no leading underscore and no trailing underscores?

I have bugs with 0.86.x, but it does boot successfully.

3

The underscore thing was a big issue for me. I had about 7 files I needed to go and change one entity and remove the underscore at the end of the entity id. It had been that way for at least 2 years, once I got that all fixed it was off and running. I keep a second pi to test the updates on before I push it to my main pi. This is mainly so I dont have an angry wife lol.

4

Seems to me you have an issue with your configuration. Did you check this section of your config and move the group: out of the homeassistant: section?