Add UI config flow, remove time zone features & legacy tracker support

[pnbruckner]

• Integrate code from CompositeScanner class into CompositeDeviceTracker class.
• Add reload service.
• Add UI-based config flow.
• Add support for sensors with lat/lon attributes.
• Add translations.
  - [ ] Add device info.
• Remove time zone related features.
• Remove legacy tracker support.
• Remove imported configs no longer in YAML.
• Handle frozen EntityDescription.
• Update docs.

Closes #55.

[bcutter]

I'm urgently looking for this feature. Thanks a loooooooot for adding it!

I want to start using this integration, but using old .yaml is really not an option (anymore, we have 2024 - UI is king 👑! 😄 ).

When can we expect this UI config flow to ship with a (stable) release?
(Update: found this is part of beta release 3.0.0.b0 https://github.com/pnbruckner/ha-composite-tracker/releases/tag/3.0.0b0 --> but beta is never a great idea to use with a production system...)

Unfortunately I can't use the beta versions as my HA does not meet the dependency requirements. Seems like there's something in this integration which needs 2023.7... 🙄 What a pity.

[pnbruckner]

@bcutter I was planning on releasing this as 3.0.0 very soon.

Regarding HA versions, yes, it does currently require at least 2023.7. That is already over a half year old. With all the changes that happen in the core system, and at such a fast rate, it gets really hard to support versions much older than that.

[bcutter]

Yeah I see. 👍 for releasing the stable 3.0 soon.
Indeed it gets. Sometimes developers are not paying specific attention to the hacs.json and simply enter the version used by their own like "this is the HA version I tested it with, so now this is required" which is why I - currently a bit behind with HA updates... - ask if there's an actual technical dependency.

But to be honest... this integration motivates me A LOT to update my HA asap (because as mentioned: UI > YAML) 😃

[pnbruckner]

Sometimes developers are not paying specific attention to the hacs.json and simply enter the version used by their own like "this is the HA version I tested it with, so now this is required" which is why I - currently a bit behind with HA updates... - ask if there's an actual technical dependency.

I do try to test with older versions to verify what the cutoff really is. Although I have been known to miss stuff if I try to do things too fast! 🤣

I started writing some of the integrations quite long ago, and often have to add code to deal with new changes while trying to maintain backwards compatibility. Normally I comment the code where this happens as to what version required the changes. At some point I go back and rip out support for really old stuff, otherwise it gets a bit ridiculous.

In this case, I'm pretty sure it was 2023.7. I don't recall the details off the top of my head, but I'm pretty sure there was a significant change in that release such that supporting older versions became difficult, so many of my custom integrations use this version as the cutoff.