v2.0.0 — domain renamed to mixergy_tank

Breaking change — the integration domain is now mixergy_tank

The previous domain, mixergy, was already registered in the Home Assistant
brands repository by a different, unrelated project of the same name. A domain
is the key both Home Assistant and the brands CDN use for identity, and two
projects cannot share one — so this integration's HACS listing showed that
project's icon, and any user with both installed risked colliding config
entries.

Moving to a domain of its own ends that misattribution and removes the
collision.

Note on the icon. HACS builds its listing icons from the brands CDN and
does not use an integration's packaged brand/ images, so the HACS listing
now shows an "icon not available" placeholder instead. Home Assistant
2026.3+ uses the packaged Mixergy artwork on its own Integrations page,
device pages, and elsewhere in the UI.

Upgrading from 1.x — manual steps required

Home Assistant ties a config entry to its domain, so the entry cannot migrate
itself. Step 4 matters: HACS installs the renamed integration into
custom_components/mixergy_tank/, but it derives its install path from the
current manifest domain and therefore cannot remove the directory belonging to
the previous one. Skipping it leaves the retired integration installed and can
show two integrations named Mixergy after the restart.

1. Take a full Home Assistant backup.
2. Note your tank's serial number (Settings → Devices & Services →
   Mixergy → Configure).
3. Delete the existing Mixergy integration entry. This frees its entity IDs
   for the replacement entry.
4. Update to 2.0.0 in HACS — but do not restart yet.
5. Delete the old /config/custom_components/mixergy/ directory, using the
   File editor, Studio Code Server, Samba, or a terminal. Keep
   /config/custom_components/mixergy_tank/.
6. Restart Home Assistant.
7. Re-add via Settings → Devices & Services → Add Integration → Mixergy,
   selecting the same tank and experience mode.
8. Update automations that call the services — mixergy.boost_charge,
   mixergy.set_holiday_dates and mixergy.clear_holiday_dates are now
   mixergy_tank.*. Device triggers using domain: mixergy become
   domain: mixergy_tank.

The recreated entities normally reclaim their previous entity IDs because
step 3 removes the old registry entries first. If an ID gains a numeric suffix,
rename it back to the original to keep dashboards, automations and recorder
history aligned.

Full walkthrough: 1.x → 2.x migration.

Unchanged

The Mixergy company name and the mixergy.io API host are untouched. Only
domain-bearing identifiers moved; there are no functional changes to polling,
entities, or the API client in this release.