alexdelprete
(Alessandro Del Prete)
January 5, 2024, 3:06pm
41
That works only if you have a single device, when you have an integration that creates a Hub with multiple devices, and one of the devices is the one you want to delete it doesn’t work.
The only way I found is messing with the config storage, but that’s not for basic users…you risk of damaging HA configuration.
1 Like
Tamooj
(Michael Steele)
January 11, 2024, 12:40am
42
Only a few integrations offer that.
HAEdwin
February 3, 2024, 11:05pm
43
Yes, it’s often forgotten, but possible to add the function.
I use this snippet in an integration, it enables users to delete a device from the hub at the Device info dialog using the overflow menu (three dots on top of eachother):
The device registry is a registry where Home Assistant keeps track of devices. A device is represented in Home Assistant via one or more entities. For example, a battery-powered temperature and humidity sensor might expose entities for temperature,...
3 Likes
I created a PR to add this possibility for stale Unifi devices:
home-assistant:dev
← wittypluck:unifi-remove-device
opened 08:02AM - 09 Apr 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
The aim of this PR is to enable the manual device delete button in UI for Unifi devices.
The delete is only allowed if the device is not present in the Unifi API any more (stale device).
![Screenshot from 2024-04-09 09-28-36 2](https://github.com/home-assistant/core/assets/21991867/4d4ca937-17bb-4902-9949-2ea83e3c2c0c)
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue: https://github.com/home-assistant/core/issues/104475#issuecomment-1936743455
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
2 Likes
jkeltonga
(Jkeltonga)
September 17, 2024, 8:41am
45
Deleting the integration and adding back in got rid of the devices I no longer use and were deleted in Smartthings.
There is the service recorder.purge_entities than can be called in Developer tools, in case of more entities switch to YAML and paste the list.
Tested on 154 orphaned entities and worked smoothly, got rid of them.
Running latest HASS@RPI5
But it can not solve my issue with tp-link router, handled by integrations “tp-link router” a “UPnP/IGD”. I replaced old VR2100 by AX55 Pro but old one is still in “tp-link router” integration. I can delete also this integration but I don’t want to loose all devices and related entities of “device_tracker” domain, including history.
nikakoy131
(Ruslan Beliy)
October 30, 2024, 8:33pm
47
Thank you!
This code helps me with hass-victron integration. I just placed this code in __init__.py
in the integration folder
Code not in image format
async def async_remove_config_entry_device(hass, config, device_entry) -> bool:
if device_entry is not None:
# Notify the user that the device has been removed
hass.components.persistent_notification.async_create(
f"The following device was removed from the system: {device_entry}",
title="Device Removed",
)
return True
else:
return False