Unable to Upgrade Home Assistant Container to 2024.11

I’m running Home Assistant Container on my Unraid server. No issues till upgrading to 2024.11, I can’t upgrade from 2024.10 to the latest release. It appears to be unhappy about one of my entity IDs being an email address. This seemed much different from the problem others have been having with this version. I thought the error was referencing a Google calendar that had the email address as the entity ID. I did add a different unique ID but that didn’t seem to resolve the issue. I tried enabling debug logging but I’m not getting any more useful information. I’m hoping someone could give some ideas of where to look next.

2024-11-16 18:52:40.397 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration weatheralerts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.407 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration schlage which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.410 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nfl which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.412 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.416 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.419 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ui_lovelace_minimalist which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.421 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.424 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.427 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.429 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:40.432 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-16 18:52:41.057 ERROR (MainThread) [root] Uncaught exception
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
                ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 157, in setup_and_run_hass
    hass = await bootstrap.async_setup_hass(runtime_config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 326, in async_setup_hass
    await async_from_config_dict(config_dict, hass) is not None
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 458, in async_from_config_dict
    await async_load_base_functionality(hass)
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 427, in async_load_base_functionality
    await asyncio.gather(
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1977, in async_initialize
    entries[entry_id] = config_entry
    ~~~~~~~^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1618, in __setitem__
    self.check_unique_id(entry)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1659, in check_unique_id
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: The entry unique id ['[email protected]'] is not a string.

Thanks in advance for any help anyone can provide.

I’ll try to help here a little bit … according to this document, unique_id is not suppose to be an email address.

If you look inside your HA’s /config/.storage folder you’ll see a file core.entity_registry. Take a look and see if you find a unique_id that has an email address. I would not edit this file, but it may point out which integration/entity has the problem. I should mention that in my case, I see google calendar whose unique_id(s) have an email address followed by a - along with more string characters and these don’t seem to produce an error, but I have no idea what the “more string characters” means.

Thanks for the suggestion, no luck unfortunately. It did appear I had one calendar entity as [email protected][email protected] for the unique ID. I really hoped that was it and removed it. The only other entries with an email address in the unique ID were related to Tile. They were similar what you mentioned you were seeing for the Google Calendar entries (i.e. email_more string characters). I removed the Tile integration as another step, not seeing the email address anywhere else in core.entity_registry for a unique ID. I’m going to try spinning up a new container running the latest version and see if it will import a backup. Not ideal but not sure where to look next.

Just wanted to close the loop on this in case someone else runs into the issue. This was completely my fault :man_facepalming: . I realized my Unraid docker template was pretty old, seemed like a good reason to spin up another container and restore a backup to see if it would resolve the issue. No surprise but it was still broken. I downgraded back to 2024.10.4 and I noticed early on in the container’s logs a similar message:

2024-11-17 11:12:50.504 ERROR (MainThread) [homeassistant.config_entries] Config entry 'Schlage Locks' from integration schlage has an invalid unique_id '['[email protected]']', please create a bug report at https://github.com/mcnutter1/homeasssitant-schlage/issues

Sure enough once I removed the Schlage integration, the container was able to run at 2024.11.2. I looked at the log message further and the Github repository didn’t make sense since Schlage had an official integration. I checked my custom_components folder and the old integration folder was still there. I removed that and I am now using the official integration without any issues.