search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.02k stars 31.05k forks source link

Multiple hue config entries with same unique ID #130020

Open glain42 opened 2 weeks ago

glain42 commented 2 weeks ago

The problem

Starting with the update to the latest HA version (see info above) I get the message about muliple configured config entries:

The config entries are named 'Philips Hue', 'Hue Bridge ecb5fa028c15'

The 2nd entry is my configured Hue bridge, I have no idea where the first entry is coming from. Reconfiguriung the intergration changes nothing. I haven't configured anything regarding the Hue integration in my maual yml files btw.

What version of Home Assistant Core has the issue?

core-2024.11.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

hue

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Andy1910 commented 2 weeks ago

Same here but with samsung rolled back to 2024.10.4 everything fine again Screenshot 2024-11-07 120258

joostlek commented 2 weeks ago

Please open a separate issue for samsungtv @Andy1910

joostlek commented 2 weeks ago

@glain42 Can you check your ignored config entries? Do you see hue there?

Andy1910 commented 2 weeks ago

Please open a separate issue for samsungtv @Andy1910

is it not the same issue just different intergration

glain42 commented 2 weeks ago

If you mean ignored integration entries, then no, there aren't any Hue entries there. I also don't see any entries named "Philips Hue" anywhere in my system (i.e. no such entity)

glain42 commented 2 weeks ago

I see this mention in the core.config_entries file tho: core.config_entries: {"created_at":"1970-01-01T00:00:00+00:00","data":{"host":"192.168.42.179"},"disabled_by":null,"discovery_keys":{"zeroconf":[{"domain":"zeroconf","key":["_hue._tcp.local.","Hue Bridge - 028C15._hue._tcp.local."],"version":1}]},"domain":"hue","entry_id":"6dcb090bceb31575c8eec5387b296922","minor_version":1,"modified_at":"2024-10-05T08:27:56.396185+00:00","options":{},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"ignore","title":"Philips Hue","unique_id":"ecb5fa028c15","version":1},

joostlek commented 2 weeks ago

@Andy1910 I know, but it can have different reasons why it happened, and I'd rather have multiple conversations about this than 1 massive one, since if the hue one is fixed, this one will be closed :)

mt104 commented 2 weeks ago

I'm seeing the same error with the Hue integration after updating to 2024.11. I'm happy to help debug if I can be useful. Hue devices seem to still be working as expected, but I haven't checked all 30 of them.

joostlek commented 2 weeks ago 
jq '.data.entries[] | select(.domain == "hue")' /config/.storage/core.config_entries >> hue_entries.txt

If you execute this, it will get every hue entry and add it to the hue_entries.txt file. If you could execute this and send the file (maybe redact the api key if you wish). That would be very helpful.

glain42 commented 2 weeks ago

(change the backtick to a nomal '). Heres the file without the api key hue_entries.txt

joostlek commented 2 weeks ago 
  "source": "ignore",
  "title": "Philips Hue",

It does seem like you once ignored it. Can you add a screenshot where you show the ignored config entries? Just to make the whole situation complete

mt104 commented 2 weeks ago

Here's mine... hue_entries.txt

joostlek commented 2 weeks ago

You also seem to have one ignored as well

home-assistant[bot] commented 2 weeks ago

Hey there @balloob, @marcelveldt, mind taking a look at this issue as it has been labeled with an integration (hue) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `hue` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hue` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

hue documentation hue source (message by IssueLinks)

glain42 commented 2 weeks ago 
  "source": "ignore",
  "title": "Philips Hue",

It does seem like you once ignored it. Can you add a screenshot where you show the ignored config entries? Just to make the whole situation complete

Sure, but I'm not exactly sure where I can see the ignored config entries. If I enable disabled integration I see one Hue entry that is ignored. Are you talking about that ?

joostlek commented 2 weeks ago

image

glain42 commented 2 weeks ago

There is one entry, but ignored. Untitled

joostlek commented 2 weeks ago

You can click stop ignoring and it would work iirc

glain42 commented 2 weeks ago

Wouldn't that interfere with my already setup bridge integration ?

joostlek commented 2 weeks ago

nope

glain42 commented 2 weeks ago

Weird, but seems to work. Thx for the fast help

joostlek commented 2 weeks ago

I have no clue how it could happen that it both got set up and got ignored at the same time

glain42 commented 2 weeks ago

I had some issues with removing and later re-adding the integration some time ago. It might have happened then. Worked so far, so I didn't looked into ignored intergrations (there's a lot of auto-detected stuff there that I don't want in my HA instance)

mt104 commented 2 weeks ago

Stop ignoring worked for me too, thanks @joostlek .

joostlek commented 2 weeks ago

(oh lol, I read it as "stop ignoring me" and I was like you what. But then I reread and it made way more sense lololol)

RMMTSLLP commented 2 weeks ago

Please open a separate issue for samsungtv @Andy1910

is it not the same issue just different intergration

After the upgrade to 2024.11.0 I see a similar issue however mine involves esphome integration

Multiple esphome config entries with same unique ID Error ⸱ Reported by Home Assistant Core Integration This stops working in version 2025.11.0. Please address before upgrading. There are multiple esphome config entries with the same unique ID. The config entries are named 'Bathroom (LD2410C)', 'Bathroom (LD2410C)'.

To fix this error, configure the integration and remove all except one of the duplicates.

Note: Another group of duplicates may be revealed after removing these duplicates.

Regards

Roger Morris

RMMTSLLP commented 2 weeks ago

I'm not to sure where to go and remove these duplicates or even where to find them. Any help greatly received. If I go back to core 2024.10.4 there are no issues. Not to sure why it references core 2025.11.0 ??

joostlek commented 2 weeks ago

Most likely the same case, you have ignored entities. We are looking to automatically eliminate ignored ones if they have been set up