Started using Nabu Casa. After changing default_config:
to cloud:
in configuration.yaml, I now receive 404: Not Found when attempting to login. I also cannot SSH in either.
EDIT: Cannot remote connect through Nabu Casa as well.
Started using Nabu Casa. After changing default_config:
to cloud:
in configuration.yaml, I now receive 404: Not Found when attempting to login. I also cannot SSH in either.
EDIT: Cannot remote connect through Nabu Casa as well.
So you removed default_config:
from your configuration.yaml and put in cloud:
Did you replace the other items from default_config that are needed?
Like automation:
, config:
, frontend:
, history:
, logbook:
, input_boolean:
, etc…?
The full list is here:
If you use any of thse integrations you have to manually add them back to your configuration.yaml file.
No, I only changed that line.
# Example configuration.yaml entry to enable the cloud component
cloud:
But you did delete default_config:
?
Yes, replaced default_config:
with cloud:
By doing that you have removed all the integrations listed below:
automation
)cloud
)config
)counter
)dhcp
)frontend
)history
)image
)input_boolean
)input_datetime
)input_number
)input_select
)input_text
)logbook
)map
)media_source
)mobile_app
)my
)person
)scene
)script
)ssdp
)stream
)sun
)system_health
)tag
)timer
)updater
)zeroconf
)zone
)If you do not want to use default_config you have to manually add back a lot of them for Home Assistant to work.
So I screwed myself and will need to start over?
Have you been making snapshot backups?
Yes. Hopefully will only lose a few things (which would be a win for my absent minded moves).
You don’t mention how you installed home assistant. If it was on a Raspberry Pi with SD card you could take out the SD card and then using a Linux PC edit the configuration.yaml file back to using default_config:
.
Search the forum to find the location of the configuration.yaml file on the SD card. I can never remember which mount it is in.
Thank you again. I’ll find it.