Thanks for the reply!
Recently I had to re-install > my DB blew up and my SD card just gave up.
After that, without reset of my Conbee II, no more duplicate groups. So yeah imho the issue is in the HA DB…
Plan for this weekend is to install on a NUC, to get rid of the SD card dependency. I’m still on my first steps into HA so the number of lights/switches/outlets is still doable (16 lights, 3 outlets, 3 switches)
I deleted the group in deconz also, still in HA visible
Then I deleted the group that hidden registry file… afterwards it’s also gone from HA
Hi Fabio,
Could you be more specific? What hidden file are you referring to?
I don’t have this issue anymore, but I would like to know how exactly you got rid of the groups.
KR,
Kurt
removed it from this file : core.device_registry , located in that hidden folder .storage
That is great info for me, unfortunately I cannot test it since after reinstall my ‘ghost’ groups are no longer present.
But if someone else can verify/acknowledge? I will mark this answer as a solution for this issue
Tnx Fabio!
@kurtj - I had the same problem (groups deleted from deConz but not HA) and was able to use @pergola.fabio’s solution.
File editor add-on, go to the add-on configuration, and remove .storage from the filterdirsfirst: false
enforce_basepath: true
ignore_pattern:
- __pycache__
- .cloud
- .storage <--------delete this
- deps
ssh_keys: []
.storage/core.device_registry, then delete the two JSON entries (mine looked like this), then save {
"config_entries": [
"d83c56d69aac4a64936d2ff80818aac7"
],
"connections": [],
"identifiers": [
[
"deconz",
"00212EFFFF04FBBC-/groups/2"
]
],
"manufacturer": "Dresden Elektronik",
"model": "deCONZ group",
"name": "Attic",
"sw_version": null,
"entry_type": null,
"id": "2f35f41bff9111ea91cdd916a8cc16eb",
"via_device_id": "d370dfc287ec471a94df24d6ee469124",
"area_id": null,
"name_by_user": null
},
{
"config_entries": [
"d83c56d69aac4a64936d2ff80818aac7"
],
"connections": [],
"identifiers": [
[
"deconz",
"00212EFFFF04FBBC-/groups/3"
]
],
"manufacturer": "Dresden Elektronik",
"model": "deCONZ group",
"name": "Master Bedroom",
"sw_version": null,
"entry_type": null,
"id": "2f36733aff9111ea862d23881acd2b9a",
"via_device_id": "d370dfc287ec471a94df24d6ee469124",
"area_id": null,
"name_by_user": null
},
Hi @lmm7425
Thanks for the info, to be honest it has been a while since I visited. After a while you stop playing and just expect these things to work (almost like housemates)
Thing is one of my sensors battery got empty and I had to replace them. Of course after adding it again in deconz I’m stuck with 'entity ID already exists so I got on the forums again and as such I just saw your post 
I haven’t tried your suggestion yet, but I found some documentation of a ‘new’ service in deconz called deconz.remove_orphaned_entries https://www.home-assistant.io/integrations/deconz
I cannot find it in my services, but like I said it must be 6 months since I updated. So I’m going to give that one a try this weekend… The sensor works since I configured deconz to do the dimming, not HA but the sensor is no longer visible in HA.
I’m hoping by removing orphanded entries, this unused entry would be gone as well but if it does not I’m going to look into the device registry.
I’m hoping the new service will make it a lot easier for people re-adding devices as I see a lot of questions from people when I googled ‘entity id already exists’ It is a similar problem then the groups one as in having same cause.
Thx @kurtj the service call deconz.remove_orphaned_entries saved me. I was also stuck with a deconz device in HA that I had already removed from deconz and this caused my symfonisk controller to be not recognized properly (zigbee pairing failed). Removing the device from HA with the service call deconz.remove_orphaned_entries and re-doing the pairing process in deconz solved my issue. Another great tip that I came across (don’t remember where) is to disable as much as possible zigbee router nodes that are nearby. In my case I have quite some Hue lights close to my Conbee II stick. The first few attempts resulted in my lights flashing in the whole house to signal the wrong kind of zigbee pairing. Switching off those nearby lights resulted in a successful zigbee pairing.
Hi @SarumaN
Great to hear this works fine for you, I haven’t found the time to get my setup updated yet so confirmation from you is very helpful indeed
Hi @SarumaN,
Can you please explain me where and how I can use the service ’ deconz.remove_orphaned_entries; ?
Thank you.
Welcome to the HA forums.
In the developer_tools menu there is a tab called service_calls. Enter deconz.remove_orphaned_entries and click call_service. I added a screenshot to make it even more clear.
Hi @SarumaN, That service does not show up in my list - do you need to install anything special?
Are you using deconz? Are you on a new enough home assistant?
Running all newest versions:
deCONZ - : 6.7.2
HA core-2021.2.3 & supervisor-2021.02.11
are you sure you are on the services tab and not the states tab? by typing deconz on the services tab it should immediately show several deconz services.
Wasn’t in the services tab - However, after a restart it’s there now - wired 
Good to hear you were able to find it.
Might be of interest, even it´s related to sensors instead of groups. Seems like there´s no clean deletion/cleanup done in deCONZ itself…
After removing 2 Ikea lights from Deconz they were still available in the Integration. Calling the service deconz.remove_orphaned_entries directly from the services tab removed them finally.
Thanks.
Reading this thread from bottom to top could have saved me a lot of time 
“deconz.remove_orphaned_entries”
Fantastic
