Release notes are your friend:
home-assistant:dev
← home-assistant:device-tracker-prepare
opened 09:56AM - 14 May 19 UTC
## Description:
Restructure the device tracker to make it easier to add EntityP… latform support.
This PR is a first step in an overhaul that will supersede the overhaul in #21151. The plan is to do #21151 but in smaller steps + make it that instead of overhauling everything at once, we will introduce it in a way that new platforms will use EntityPlatform, while the old ones remain using the legacy code.
Once the overhaul is complete, we will no longer accept contributions using the old style. Important platforms will be migrated to use the EntityPlatform.
**Related issue (if applicable):** https://github.com/home-assistant/architecture/issues/151
## Checklist:
- [x] The code change is tested and works locally.
- [x] Local tests pass with `tox`. **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]
If the code does not interact with devices:
- [x] Tests have been added to verify that the new code works.
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
Comment from the release page that might be relevant:
The new way is how you manage any other entity in Home Assistant: via the entity registry. Access it either via config panel, customize or the settings icon in the more info dialog.
They are overhauling how the device trackers work. If you upgraded to 94.0, I would just move forward and convert to the new way of doing things since the legacy way is going away. Yes, this was a pain as I had to change several of my node-red flows, but once done it’s done and there shouldn’t be too many more “growing pains”. My $.02
1 Like