- I sanitized the yaml, looks better?
- the customize.yaml file is in the config folder. Yes i pasted it from the logfile, the error message
- I will try that, even with double line between everything shouldn´t effect things, right?
You pasted one error message. Is that the only one?
You have told your configuration yaml to ignore hacs: yet you left the following lines which get read and cause errors…
Error loading /config/configuration.yaml: in “/config/configuration.yaml”, line 14, column 14: Unable to read file /config/customize.yaml.
This is the error message i get from HA, and it will boot up in safe mode.
The HACS i enabled that again, i saw what you say about comment out the hacs.
Stil get the same error msg.
And there is NOTHING else in the log file? Not the GUI, but the log FILE.
It appears to me like it’s not actually reading your configuration yaml. Explain how you performed the upgrade.
Where can i find the log file?
I updated via HA in the GUI/Supervisor
Found it, will paste it
There ALOT in the logfile, what am i looking for? 
Alot of msg about volvooncall, and i dont like that looks error to me
Errors. I thought that was obvious.
Yes i know.
What if i just replace my config.yaml with a basic simple one? Could that work?
If you stop HA, rename your configuration.yaml to configuration.bak, it should generate a new basic config on first launch, but it may conflict with items in your .storage directory (auth, registry entries, etc)
2020-05-12 11:00:16 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/volvooncall/__init__.py", line 165, in update
if not await connection.update(journal=True):
File "/usr/local/lib/python3.7/site-packages/volvooncall/volvooncall.py", line 113, in update
await vehicle.update(journal=journal)
File "/usr/local/lib/python3.7/site-packages/volvooncall/volvooncall.py", line 154, in update
await self._connection.update_vehicle(self, journal)
File "/usr/local/lib/python3.7/site-packages/volvooncall/volvooncall.py", line 121, in update_vehicle
self._state[url].update(await self.get("status", rel=url))
File "/usr/local/lib/python3.7/site-packages/volvooncall/volvooncall.py", line 90, in get
return await self._request(METH_GET, self._make_url(url, rel))
File "/usr/local/lib/python3.7/site-packages/volvooncall/volvooncall.py", line 75, in _request
response.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 946, in raise_for_status
headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://vocapi.wirelesscar.net/customerapi/rest/v3.0/vehicles/YV1MZ74L1H2135485/status
I will try that, brb
2020-05-12 19:38:51 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2020-05-12 19:38:51 INFO (MainThread) [homeassistant.core] Timer:starting
2020-05-12 19:40:19 ERROR (MainThread) [homeassistant.components.hassio] Error loading /config/configuration.yaml: in “/config/configuration.yaml”, line 14, column 14: Unable to read file /config/customize.yaml.
Above is from the log from docker, and it didn´t create a new config.yaml.
I think i will delete HA and reinstall it again.
Then it’s not using YOUR configuration yaml.
This is very wierd, i will reinstall HA from scratch. But thanks for your help anyway. 
This could be the answer for my problem.
But it’s not…
The deprecation has been put on hold, but the deprecation doesn’t have anything to do with currently running systems using this installation method.
1 Like
In an indirect way it is. He is the posterboy (no offence) to why they want to stop support. To be honest, when I read this thread my eyes hurt. How do people get this far?
1 Like