Open PilgrimToHyperion opened 3 months ago
Hi! That is strange. Sorry you experienced this! Do you have a copy of the .yaml file changes you made to the trusted networks section? I wonder if integrations etc missing because it started in safe mode perhaps? As making a change to a .yaml file shouldn't remove any integrations...
Please don't be sorry! I should have been careful and made a brand new backup before adding this! :)
Retyped what I had in configuration.yaml. See attached file. I added the portion of trusted network config underneath existing homeassistant: entries.
The integrations were missing after removing the trusted network config. HA started up normally (not in recovery mode), but everything was broken.
I don't see anything in there that would cause an issue really.. other than 'batman' being the user ID, but I assume you removed the actual ID for safety reasons... Could you try again maybe and get the full logs? And doing a backup prior.
Hi @PilgrimToHyperion did you get anywhere with this?
Hello @b0mbays , alright, followed the same steps. Here's some more info:
Changes to configuration.yaml:
homeassistant: allowlist_external_dirs:
Then I did a restart for that to take effect. After HA came up:
Log file entries:
2024-06-18 09:16:12.886 ERROR (MainThread) [homeassistant.auth.providers] Invalid configuration for auth provider trusted_networks: expected a dictionary for dictionary value @ data['trusted_users']. Got '192.168.5.152/32 beylie 192.168.5.153/32 beylie' 2024-06-18 09:16:12.887 ERROR (MainThread) [homeassistant.config] Invalid config for 'homeassistant' at configuration.yaml, line 100: expected a dictionary for dictionary value 'trusted_users', got None 2024-06-18 09:16:12.888 WARNING (MainThread) [homeassistant.bootstrap] Unable to set up core integrations. Activating recovery mode 2024-06-18 09:16:13.229 WARNING (MainThread) [homeassistant.components.hassio.handler] Found incompatible HTTP option 'server_host'. Watchdog feature disabled
I got such a fright. Restoring the backup took twice as long as previously. I thought I'd completely broken my installation this time!
Had exactly the same issue just now.
When I added the trusted_users
section under to configuration.yaml HA refused to restart at all. Definately something strange going on. I removed those few lines and it booted up OK again.
Hi, I second (third) this issue. This is strange, as trusted_users is still available in the official home assistant documentation. Anyone aware of what changed? As soon as I remove the trusted_users, it will exit recovery mode and boot just fine
Well that was stupid on my end. @kitkat270, @PilgrimToHyperion; the user specified actually has to be the real system ID (32 digit hex ID) and cannot be anything else. You can find it when you click on the user in system settings, right under 'ID'
Ha - YES! I'd just found the same although I've not tried it yet.
I added the repository and integration as per instructions and restarted HA. I then proceeded to perform the trusted network setup as per the instructions in prerequisites #3. Restarted HA. HA went into recovery mode. It showed an error (unfortunately I didn't copy the log entries) but they were related to the trusted_users: part of the configuration.yaml file. It complained that it couldn't find the username (if the username was Apple it would show couldn't find A, if it was Batman, it would show couldn't find B). Creating a new admin username and specifying that lead to the same upon restart.
I decided to just remove the trusted network setup portion I added and only that from the configuration.yaml file. Restarted HA again. It started up but was a complete mess.
All integrations were missing. Entities missing. Triggers defined in automation broken etc.
I had to restore a backup to get back to a working copy of HA. Almost lost 4 days worth of changes I made, but I copied the contents of the automations.yaml and the raw dashboards config and replaced after the backup restore. :D
As I'm not the first user to experience this, I think some investigation needs to be done.