Another 'Can't upgrade from 2024.10.4' instance

Installation
1

I’m running 2024.10.4 and have been unable to upgrade.

I’ve read several threads on what to try, including restarting in safe mode and looking at the logs.

I’m at a total loss.

Does this help:

2025-06-22 08:34:27.034 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
2025-06-22 08:34:27.034 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2025-06-22 08:34:27.035 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
2025-06-22 08:34:27.035 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.10.4
2025-06-22 08:34:27.036 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2025.6.1 to ghcr.io/home-assistant/qemux86-64-homeassistant:2024.10.4
2025-06-22 08:34:27.036 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2024.10.4.
2025-06-22 08:34:27.409 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning homeassistant application
2025-06-22 08:34:27.468 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2025-06-22 08:34:27.710 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2024.10.4
2025-06-22 08:34:27.710 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-06-22 08:34:33.647 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2025-06-22 08:34:33.746 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-06-22 08:34:33.834 WARNING (MainThread) [supervisor.addons.options] Option 'dns' does not exist in the schema for AdGuard Home (a0d7b954_adguard)
2025-06-22 08:34:37.745 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='NOT_RUNNING', offline_db_migration=False)
2025-06-22 08:36:37.881 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='STARTING', offline_db_migration=False)
2025-06-22 08:36:42.783 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2025-06-22 08:36:42.786 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
2025-06-22 08:36:42.798 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API proxy running
2025-06-22 08:36:42.915 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='RUNNING', offline_db_migration=False)
2025-06-22 08:36:42.916 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
2025-06-22 08:36:42.916 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2024.10.4

Or this from the rollback log:

2025-06-22 08:34:21.880 WARNING (SyncWorker_0) [annotatedyaml.constructors] YAML file /config/configuration.yaml contains duplicate key "template". Check lines 47 and 309
2025-06-22 08:34:21.933 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pirateweather 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
2025-06-22 08:34:21.934 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonoff 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
2025-06-22 08:34:21.935 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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
2025-06-22 08:34:21.935 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration average 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
2025-06-22 08:34:21.936 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc 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
2025-06-22 08:34:21.936 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration remote_homeassistant 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
2025-06-22 08:34:21.937 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration weatherflow_forecast 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
2025-06-22 08:34:21.937 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration flair 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
2025-06-22 08:34:21.937 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwains_dashboard 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
2025-06-22 08:34:21.938 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
2025-06-22 08:34:21.939 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration multiscrape 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
2025-06-22 08:34:21.939 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration openweathermaphistory 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
2025-06-22 08:34:21.939 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration whatsapp 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
2025-06-22 08:34:21.939 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors 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
2025-06-22 08:34:21.940 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mikrotik_router 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
2025-06-22 08:34:21.942 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration blueiris 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
2025-06-22 08:34:21.943 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ha_kia_hyundai 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
2025-06-22 08:34:21.943 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fullykiosk 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
2025-06-22 08:34:21.944 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration measureit 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
2025-06-22 08:34:21.944 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
2025-06-22 08:34:21.944 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration emporia_vue 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
2025-06-22 08:34:21.945 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration icloud3 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
2025-06-22 08:34:22.157 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 227, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 719, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 122, in setup_and_run_hass
    hass = await bootstrap.async_setup_hass(runtime_config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 337, in async_setup_hass
    await async_from_config_dict(config_dict, hass) is not None
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 474, in async_from_config_dict
    await async_load_base_functionality(hass)
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 443, in async_load_base_functionality
    await asyncio.gather(
    ...<13 lines>...
    )
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2178, in async_initialize
    entries[entry_id] = config_entry
    ~~~~~~~^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1795, in __setitem__
    self.check_unique_id(entry)
    ~~~~~~~~~~~~~~~~~~~~^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1836, in check_unique_id
    raise HomeAssistantError(
        f"The entry unique id {unique_id} is not a string."
    )

Thank you!

2

FiRST
Best to upgrade single major version at a time so

2024.10.4 >> 2024.11.0 >> 2024.12.0 and so on. With backups you go.

You can skip version or other things but this is the easiest method that allows you to correct broken things as you go

SECOND
You use a lot of third part integrations?
Did you check all the versions for breaking changes before upgrade and fix them?

These two may cause you lots of issues with big version jumps

THIRD

Did you check this error?
Looks like a problem in your config file.

3

Thank you very much for your help.

I updated as much as possible. Some items needed to be removed, and some won’t update because it needs a more current version of HA.

In SYSTEM | UPDATES everything is updated except core.

(I had to disable Z-Wave JS because it is “not compatible” with this version.)

In HACS, all INTEGRATIONS are updated (and there were indeed many)

configuration.yaml, line 47:

“template: !include propane_monitoring.yaml”

line 309 starts all my templates:

“template:”

Is there a problem with it like this?

I tried to research how to install specific versions and got completely lost.

4

Not sure. I’m thinking yes

Why did tou seperate propane template?
Can you just add it with other templates

5

Definitely a problem. You’ve already defined template: in your configuration.yaml. Adding it again in your included file will cause an exception.

Read through the docs on how to set it up properly - the error you are getting isn’t caused by the upgrade.

6

When I try to move:

"!include propane_monitoring.yaml”

to after line 309 (which starts the “template:” definitions), it fails.

I don’t know what you mean by “the error you are getting isn’t caused by the upgrade.” Is this “template” config error causing the failure to upgrade?

I am sure you are correct about not putting “template: !include propane_monitoring.yaml” above “template:” but it seems to work, despite throwing off an error.

I just want to upgrade to the current version and I don’t know how.

EDIT: I opened TERMINAL and issued:

“ha core update --version 2024.11.0”

It went through a severla minute process that ended with a restart of HA.

But, looking in SYSTEM | UPDATES it still shows core at 2024.10.4

And I see the same error:

“2025-06-22 17:31:51.904 ERROR (MainThread) [root] Uncaught exception”

7

Remove propane.yaml

If it start without error that was the only problem

You can add contents of propane.yaml into the template section (309) after verifying if you desire

8

Great troubleshooting (I should’ve thought of that).

Tried commenting the !include, restarted, ran update via CLI as well as GUI and still at 2024.10.4

Log has these entries:


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 227, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 719, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 122, in setup_and_run_hass
    hass = await bootstrap.async_setup_hass(runtime_config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 337, in async_setup_hass
    await async_from_config_dict(config_dict, hass) is not None
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 474, in async_from_config_dict
    await async_load_base_functionality(hass)
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 443, in async_load_base_functionality
    await asyncio.gather(
    ...<13 lines>...
    )
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2178, in async_initialize
    entries[entry_id] = config_entry
    ~~~~~~~^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1795, in __setitem__
    self.check_unique_id(entry)
    ~~~~~~~~~~~~~~~~~~~~^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1836, in check_unique_id
    raise HomeAssistantError(
        f"The entry unique id {unique_id} is not a string."
    )

Anything else I can try?

9

Look for “unique id” in config

It may be a customize entry

10

I looked in configuration.yaml

There are 17 instances of unique_id, such as:

rest:
  - resource: https://ws.otodatanetwork.com/neevoapp/v1/DataService.svc/GetAllDisplayPropaneDevices
    authentication: basic
    username: "<user>@yahoo.com"
    password: "<password>"
    scan_interval: 720000000
    headers:
      Content-Type: application/json
    sensor:
      - name: "Propane Tank Neevo 371 Gallons Rest"
        unique_id: propane_tank_371_gallons_rest
        value_template: "{{ value_json[0].Level|float(0) * 2.4 if value_json[0].Level is defined else this.state }}"
        state_class: measurement
        unit_of_measurement: "gal"

I don’t find any with curly brackets around it: {unique_id}

I tried to find:

/usr/src/homeassistant/homeassistant/config_entries.py

but could not.

11

Propane tank doesn’t exist— remember you removed it — so maybe that causes issue

Add back propane tank or comment out

12

Yes, I uncommented the !include and that error went away.

Is there a way to know what is preventing the upgrade without looking at resolving all errors?

13

No. Take the items from the include file and place them directly into config file. you cannot have two of the same sections (template section twice)

It tells you but you don’t know how to fix it because you have limited understanding of how things work. This is understandable but this is what you get when you use severall third party integrations and wait >6 months to update.

Basic HA you can update after 2yrs without much issue but third party integrations will cause large headaches even after single version update

Patience will get it done

14

Change unique_id: propane_tank_371_gallons_rest to unique_id: “propane_tank_371_gallons_rest”

15

I tried to move the code into configuraiton.yaml, but the formatting requirement is beyond me.

I commented the !include so there is only one “template” section now.

I ran:

ha core update --version 2024.11.0

And the rollback log shows:

2025-06-23 05:09:53.517 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pirateweather 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
2025-06-23 05:09:53.520 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonoff 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
2025-06-23 05:09:53.522 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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
2025-06-23 05:09:53.525 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration average 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
2025-06-23 05:09:53.527 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc 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
2025-06-23 05:09:53.528 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration remote_homeassistant 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
2025-06-23 05:09:53.529 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration weatherflow_forecast 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
2025-06-23 05:09:53.530 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration flair 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
2025-06-23 05:09:53.532 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwains_dashboard 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
2025-06-23 05:09:53.534 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
2025-06-23 05:09:53.535 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration multiscrape 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
2025-06-23 05:09:53.536 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration openweathermaphistory 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
2025-06-23 05:09:53.537 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration whatsapp 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
2025-06-23 05:09:53.539 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors 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
2025-06-23 05:09:53.540 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mikrotik_router 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
2025-06-23 05:09:53.542 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration blueiris 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
2025-06-23 05:09:53.544 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ha_kia_hyundai 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
2025-06-23 05:09:53.546 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fullykiosk 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
2025-06-23 05:09:53.547 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration measureit 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
2025-06-23 05:09:53.549 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
2025-06-23 05:09:53.551 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration emporia_vue 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
2025-06-23 05:09:53.552 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration icloud3 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
2025-06-23 05:09:54.320 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 ['<my-email-address'] is not a string.
16

I put quotes around the unique id for all the REST sensor, but there are many other unique id entries.

Do they all need quotes?

Is this a version thing, because it was working fine without the quotes.

Here is an example:

  - sensor:
      - name: "Propane Tank Neevo 630 Gallons Raw"
        unique_id: propane_tank_630_gallons_raw
        state: >
          {% if states('sensor.propane_tank_neevo_raw_630') != 'unavailable' and states('sensor.propane_tank_neevo_raw_630') != 'unknown' and states('sensor.propane_tank_neevo_raw_630')|float(0) > 0 %}
            {{ states('sensor.propane_tank_neevo_raw_630') }}
          {% else %}
            {{ this.state }}
          {% endif %}
        state_class: measurement
        unit_of_measurement: "gal"
        restore_state: true
17

I tried restarting in safe mode again and upgrading, but it doesn’t work.

Same log entries.

18

Judging by the previous error of The entry unique id {unique_id} is not a string.", I’d say yes.

I doubt it. It would depend when you added those entries with the unique_id in yaml. Given that you hadn’t updated since last October, if you added those afterwards then you might not have noticed the error, even after a restart.

Honestly, at this point you would be better off commenting out all those sensors (or at least the unique_id line in each of them).
It wouldn’t be a bad idea to share your configuration yaml file for us to see what exactly is going on. Just make sure you hide all personal info like emails or passwords, if they’re in that file.

19

Thank you so very much for the offer to take a look at my config. I believe I sanitized it (sure hope so).

I have no doubt there are lots of mistakes, errors, and absurdities in this. This config has been a work in progress for quite a few years, from when I knew absolutely nothing about HA to now when I know only a little bit.

groups.yaml and scripts.yaml are empty.

I tried pasting, but the post became too long. I don’t see a way to attach a file. How can I share the yaml files?

Thank you!

20

I found a thread about creating a github, so I did that and uploaded the yaml files.

Sure hope it works, and sure hope it’s sanitized.

Here is the link:

https://github.com/josephny/HA-config-files