REOLINK Integration: Can not delete a camera previously (wrongly) installed

[RoSche2001]

The problem

Hi, this is for the Reolink integration:
I have added 2 cameras (CX810) of which one worked perfectly fine but the other is "disabled by configuration entry". (I can see all entities correctly but all except the device_tracker are disabled.
I can not see a configuration entry that is dialing it so I have repeatedly de-installed this camera from the Reolink integration sometimes with errors (can not be deleted). I also restarted the integration as well as Home Assistant after the deinstall.
In all cases without effect: it seems that the camera configuration is somewhere stored in the system and as such a new installation is always retrieving the previous data set. I also tried to give the camera a different IP address, used a different camera user account but that did not help either, it was recognized as previously installed as well.

Question: What is the correct way to delete all information on that particular camera so that I can try a completely new install? Or even better how to get rid of the disabling in the configuration file?

What version of Home Assistant Core has the issue?

2025.4.3

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

Reolink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/reolink#configuration

Diagnostics information

config_entry-reolink-01JSH912TSB76JCT0RSFAZCD49.json

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of reolink 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 reolink 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)}}

---

reolink documentation
reolink source
_{^{(message by IssueLinks)}}

[RoSche2001]

I solved it myself (but believe there is still a bug that led to my case).
For this I went into the files

• core.config_entries
• core_device_registry

and manually deleted all lines with cameras with the same IP address.

I did find some old entries from previous cameras using the same IP address, which have been replaced. It seems that the function for deleting those old devices vie UI do not work completely. Once you replace a camera and use the same IP for the replacement you run into this problem.

Although solved in my case I still think it is worthwhile checking this delete routine or introduce an error handling procedure if old entries with the same IP address are being found. Instead of blocking the new camera it might be good to propose that the integration deletes old entries in case of double IPs.