WTH why don't we get migration guides when a new integration is added to core HA and there's a popular HACS version?

Recently RTC webcam support was added to the dashboard, but as far as I can tell, there’s not been any documentation on what people using the HACS version should do to migrate (if anything is required.)
Similarly, there’s now an official LG SmartThinq integration, though there’s also a very popular HACS integration (in this case maybe the answer is to use both, since the official one is not as full-featured yet and they don’t seem to create overlapping entities for now.)

But as a user, I’m often left at a loss- how do I transition to the core integration in more complex cases.
Some times, the answer will likely be as simple as “uninstall the HACS version, and add the core one from the GUI, then adjust dash/automations/etc to use the new entities.” Even that level of information should be good enough, with more as appropriate for more complex migrations.

There wasn’t anything required by the end user.

Backward incompatible changes or YAML changes do (usually) have a migration guide in the the release notes.

In many cases, officially supported integrations don’t have all the features that HACS ones do, so keeping them is probably the best option. In the case of the Music Assistant integration, the HACS version actually did have a migration guide for switching to the official one, written by those developers, and sometimes having them (the HACS integration developers) do it is the best option.

1 Like