Skip to content

Duplicate IDs error #5461

Closed
Closed
Duplicate IDs error#5461
Labels
issue:backendFor issues with the backend/integration

Description

@FoxP
FoxP
opened on Aug 7, 2026

System Health details

System Information

version core-2026.8.0
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch amd64
user root
virtualenv false
python_version 3.14.6
os_name Linux
os_version 6.18.39-haos
arch x86_64
timezone Europe/Paris
config_dir /config
Home Assistant Cloud
logged_in true
subscription_expiration 16 mai 2027 à 02:00
relayer_connected true
relayer_region eu-central-1
remote_enabled true
remote_connected true
remote_server eu-central-1-34.ui.nabu.casa
alexa_enabled true
google_enabled true
cloud_ice_servers_enabled true
certificate_status ready
instance_id c335ce38e5564ea99e2fb48abba49a0c
iot_state connected
iot_tries 0
certificate_expire_date 16 septembre 2026 à 23:24
certificate_fingerprint 38cc557da731f448be3605ebb9f96a170f93c1b1
certificate_alternative_names undefined
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
HACS
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 4997
Installed Version 2.0.5
Stage running
Available Repositories 3935
Downloaded Repositories 27
Home Assistant Supervisor
host_os Home Assistant OS 18.2
update_channel stable
supervisor_version supervisor-2026.07.5
agent_version 1.10.0
docker_version 29.6.2
disk_total 62.3 GB
disk_used 9.9 GB
nameservers fd0f:ee:b0::1, 192.168.1.254
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons Studio Code Server (6.0.1), Speedtest (1.6.2), Linky (1.7.0)
Dashboards
dashboards 3
resources 11
views 15
mode storage
Network Configuration
adapters lo (disabled), enp6s18 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth0bb65d1 (disabled), veth715f68d (disabled), veth8a9300b (disabled), vethbc811c0 (disabled), veth9e3ba28 (disabled), vethf0258fe (disabled), veth7098814 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp6s18 (192.168.1.84/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth0bb65d1 (), veth715f68d (), veth8a9300b (), vethbc811c0 (), veth9e3ba28 (), vethf0258fe (), veth7098814 ()
ipv6_addresses lo (::1/128), enp6s18 (2a01:e0a:f34:4d0:bc75:651a:af15:f7c9/64, fe80::65d3:9aa0:8f79:167/64), hassio (fd0c:ac1e:2100::1/48, fe80::8ca2:87ff:fe8e:9138/64), docker0 (fd8b:837b:716c::1/64, fe80::fc24:b7ff:fe6c:94b8/64), veth0bb65d1 (fe80::2493:5fff:fe5e:6533/64), veth715f68d (fe80::ccd6:3aff:fee9:457e/64), veth8a9300b (fe80::18f2:e3ff:fe13:cdfa/64), vethbc811c0 (fe80::ac8d:ceff:fec4:4ee3/64), veth9e3ba28 (fe80::709b:52ff:fe94:fb3c/64), vethf0258fe (fe80::1821:45ff:fe85:48c2/64), veth7098814 (fe80::c44f:3eff:fe76:d4d5/64)
announce_addresses 192.168.1.84, 2a01:e0a:f34:4d0:bc75:651a:af15:f7c9, fe80::65d3:9aa0:8f79:167
Recorder
oldest_recorder_run 26 juillet 2026 à 12:34
current_recorder_run 7 août 2026 à 08:55
estimated_db_size 528.24 MiB
database_engine sqlite
database_version 3.53.2

Checklist

  • I'm running the newest version of HACS https://github.com/hacs/integration/releases/latest
  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • I have read https://hacs.xyz/docs/help/issues/
  • This issue is related to the backend (integration part) of HACS.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This is a bug and not a feature request.
  • This issue is not a duplicate issue of currently open or issues pending release.

Describe the issue

I got this error message this morning after upgrading Home Assistant to the latest version :

Cette erreur provient d'une intégration personnalisée.

Logger: custom_components.hacs
Source: custom_components/hacs/utils/data.py:272
Intégration: HACS (Documentation, Problèmes)
Première occurrence: 08:55:44 (1 occurrence)
Dernier enregistrement: 08:55:44

<HacsData async_restore_repository> duplicate IDs The repo id for hugo-brito/ha-minvandforsyning is already set to 1325795051

Reproduction steps

--

Debug logs

--

Diagnostics dump

--

Activity

  1. FoxP
    added
    issue:backendFor issues with the backend/integration
    on Aug 7, 2026

  2. hacs-bot commented on Aug 7, 2026

    @hacs-bot
    hacs-botbot
    on Aug 7, 2026

    Thank you for opening an issue in the HACS.

    Before proceeding, please verify the following:

    Select the correct issue template:
    HACS provides different templates for different types of bugs. Choosing the right template ensures you're asked the right questions and helps route your bug appropriately.

    Complete the ENTIRE issue template:
    Make sure you've read the issue guidelines and filled out every single field in the issue template, even if some fields seem unrelated to your specific situation.

    Fill out everything, even if it seems unnecessary:
    Don't skip fields because they "don't seem relevant" to your bug. The template asks for specific information because:

    • Problems often have unexpected causes that surface through "unrelated" details
    • What seems unrelated to you might be the key to solving your bug
    • Incomplete information requires follow-up questions, delaying resolution
    • The template is designed based on years of troubleshooting experience
    • Missing information forces those helping to make assumptions, which can lead to wrong solutions

    Issues with incomplete templates take significantly longer to resolve or may be closed without resolution.

    If you're experiencing a similar bug:
    If your bug is identical to an existing one, please:

    • Add a 👍 reaction to the original issue description
    • Subscribe to notifications on that issue to stay updated
    • Do not add comments like "same here", "I have this too", or "+1"

    Adding duplicate comments creates noise and makes it harder to track and resolve issues. Reactions help prioritize issues based on how many users are affected.

    Getting help:
    If you need assistance filling out the template or understanding your issue:

    What happens next:
    Maintainers and community members will review your issue and may:

    • Ask for additional information if the template is incomplete
    • Provide a solution or workaround
    • Label the issue appropriately for tracking
    • Link it to related issues or pull requests

  3. StuartC84 commented on Aug 7, 2026

    @StuartC84
    StuartC84
    on Aug 7, 2026

    I got the same Warning in my HA logs about 'The repo id for hugo-brito/ha-minvandforsyning is already set to ...' except mine had id '1208161604' which is different from @FoxP 's above.

    I also got an Error message in the logs as well as the Warning, but with a little bit more detail. Error text pasted below in case it helps to track down this issue.

    Logger: homeassistant
    Source: custom_components/hacs/base.py:290
    Integration: HACS (documentation, issues)
    First occurred: 14:36:02 (1 occurrence)
    Last logged: 14:36:02
    Error doing job: Task exception was never retrieved (task: None)
    Traceback (most recent call last):
    File "/config/custom_components/hacs/base.py", line 667, in startup_tasks
    await self.async_get_all_category_repositories()
    File "/config/custom_components/hacs/base.py", line 832, in async_get_all_category_repositories
    await asyncio.gather(
    ...<4 lines>...
    )
    File "/config/custom_components/hacs/base.py", line 862, in async_get_category_repositories_experimental
    self.repositories.set_repository_id(repository, repo_id)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
    File "/config/custom_components/hacs/base.py", line 290, in set_repository_id
    raise ValueError(
    ...<2 lines>...
    )
    ValueError: The repo id for hugo-brito/ha-minvandforsyning is already set to 1208161604

    Hope that helps. If you need anything else, just ask.

  4. Jam3s97 commented on Aug 8, 2026

    @Jam3s97
    Jam3s97
    on Aug 8, 2026

    Also seeing this after updating to 2026.8.1 from 2026.7.x
    Interestingly repo ID in my log is different number from OP.

    <HacsData async_restore_repository> duplicate IDs The repo id for hugo-brito/ha-minvandforsyning is already set to 1208161604

    Edit
    On my test HASS instance still on core 2026.7.1
    Both instances are running HACs 2.0.5
    Reboot causes the same to be logged but with the other ID mentioned in this thread.
    <HacsData async_restore_repository> duplicate IDs The repo id for hugo-brito/ha-minvandforsyning is already set to 1325795051

  5. Gronaldo1 commented on Aug 8, 2026

    @Gronaldo1
    Gronaldo1
    on Aug 8, 2026

    Same here

  6. erkr commented on Aug 8, 2026

    @erkr
    erkr
    on Aug 8, 2026

    Same logs while still on core 2026.7.4. Different number as well

  7. Jam3s97 commented on Aug 8, 2026

    @Jam3s97
    Jam3s97
    on Aug 8, 2026

    Could it be a bug on
    https://github.com/hugo-brito/ha-minvandforsyning
    Which had updates yesterday.
    I don't use this HACs integration but I guess because it is in the default store it flags the error.

    I raised issue over there
    hugo-brito/ha-minvandforsyning#2

  8. hugo-brito commented on Aug 8, 2026

    @hugo-brito
    hugo-brito
    on Aug 8, 2026

    Thanks for the logs. The repository was deleted and recreated, so GitHub assigned it a new ID. HACS restored the old ID from local storage and then failed when the catalog returned the new one. This also explains why different IDs appeared in the logs; it is not tied to a Home Assistant update.

    #5463 updates the stored entry to the catalog ID, keeps its installed settings, and removes the old ID on the next HACS write.

  9. erkr commented on Aug 10, 2026

    @erkr
    erkr
    on Aug 10, 2026

    Still get them. Any idea how long 'a next HACS write' can take?

  10. KentEkl commented on Aug 10, 2026

    @KentEkl
    KentEkl
    on Aug 10, 2026

    Meto.
    ValueError: The repo id for hugo-brito/ha-minvandforsyning is already set to [1208161604]

  11. hugo-brito commented on Aug 10, 2026

    @hugo-brito
    hugo-brito
    on Aug 10, 2026

    @erkr
    The PR needs to be merged before the issue is gone.

  12. DariukaB commented on Aug 12, 2026

    @DariukaB
    DariukaB
    on Aug 12, 2026

    This error originated from a custom integration.

    Logger: homeassistant
    Source: custom_components/hacs/base.py:290
    Integration: HACS (documentation, issues)
    First occurred: 13:33:23 (1 occurrence)
    Last logged: 13:33:23

    Error doing job: Task exception was never retrieved (task: None)
    Traceback (most recent call last):
    File "/config/custom_components/hacs/base.py", line 832, in async_get_all_category_repositories
    await asyncio.gather(
    ...<4 lines>...
    )
    File "/config/custom_components/hacs/base.py", line 862, in async_get_category_repositories_experimental
    self.repositories.set_repository_id(repository, repo_id)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
    File "/config/custom_components/hacs/base.py", line 290, in set_repository_id
    raise ValueError(
    ...<2 lines>...
    )
    ValueError: The repo id for hugo-brito/ha-minvandforsyning is already set to 1208161604

  13. erkr commented on Aug 27, 2026

    @erkr
    erkr
    on Aug 27, 2026

    I think it's solved, haven't seen it the last week

  14. Warsenius commented on Sep 1, 2026

    @Warsenius
    Warsenius
    on Sep 1, 2026

    I think it's solved, haven't seen it the last week

    im still having the issue. waiting for hugo's merge-request

  15. CircleLiu commented on Oct 1, 2026

    @CircleLiu
    CircleLiu
    on Oct 1, 2026

    Also seeing this after updating to 2026.8.1 from 2026.7.x Interestingly repo ID in my log is different number from OP.

    <HacsData async_restore_repository> duplicate IDs The repo id for hugo-brito/ha-minvandforsyning is already set to 1208161604

    Edit On my test HASS instance still on core 2026.7.1 Both instances are running HACs 2.0.5 Reboot causes the same to be logged but with the other ID mentioned in this thread. <HacsData async_restore_repository> duplicate IDs The repo id for hugo-brito/ha-minvandforsyning is already set to 1325795051

    I found a temporary solution.
    Open /config/.storage/hacs.repositories file, search for hugo-brito/ha-minvandforsyning and there should be two records to be found.
    Delete one of the records, save and restart, then HACS can successfully start

  16. edif30 commented on Oct 5, 2026

    @edif30
    edif30
    on Oct 5, 2026

    Same warning here, and it went away after a UI action. Sharing in case it helps.

    Setup: HACS 2.0.5, HA Core 2026.9.4 (Container).

    Symptom: on every startup, a few seconds in:
    WARNING [custom_components.hacs] duplicate IDs The repo id for hugo-brito/ha-minvandforsyning is already set to 1325795051
    It persisted across many restarts and a full container rebuild with .storage untouched.

    What I checked: the repo isn't downloaded. In .storage/hacs.repositories and hacs.data it appears exactly once, under 1325795051, with no second ID for that slug anywhere in the stored files (hacs.hacs and hacs.removed too). That
    entry had "new": true.

    What fixed it: in the HACS UI I clicked "Dismiss new", then restarted HA. The warning was gone on that restart and on a second one afterward.

  17. frenck commented on Oct 16, 2026

    @frenck
    frenck
    on Oct 16, 2026
    Member

    Thanks for reporting this.

    HACS is moving into Home Assistant as the Marketplace integration (see #5590). This is fixed in Marketplace, which ships with Home Assistant 2026.11. If you still run into it after upgrading, check the open Marketplace issues and open a new one in home-assistant/core.

    Closing this one.

    ../Frenck

                           

    Blogging my personal ramblings at frenck.dev

  18. frenck
    closed this as completedon Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue:backendFor issues with the backend/integration

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions