Hey everyone,

Quick update on the Control D Manager integration for Home Assistant. I realized I never posted the announcement for the 1.3.0 release, so let me cover that and bundle in the just released 1.3.1 all at once.

✅ Version 1.3.0 — Smarter entities & Easier setup

A while back, 1.3.0 rolled out with two big themes: making entities more reliable to build on, and making setup problems actually diagnosable.

Structured entity metadata Every Control D entity now carries consistent metadata — integration, profile, purpose, item type, taxonomy path, and item name. In practical terms, dashboards, templates, and automations no longer have to hack their way around entity names; you can select and build on entities programmatically in a consistent way.

Much better setup diagnostics Startup and refresh now log far more detail — which stage is running, what normalization is happening, and exactly where an upstream payload mismatch breaks. If you ever hit a setup failure, the log now points at the real cause instead of leaving you guessing.

A compatibility fix Some Control D accounts return live service IDs as numbers instead of strings, which could break setup. 1.3.0 now handles both, so those accounts set up cleanly.

🎉 Version 1.3.1 — No more entity state flickering

If you toggled a few options, filters, or services at once — or ran a script that flips 5-10 settings in a loop — you'd sometimes see the UI and the the underlying entity state briefly "bounce back" to an older value before correcting.

What was happening Every change was triggering its own full inventory refresh, and if a refresh was already running when you made a change, that stale result could land afterward and momentarily flip the UI back to the old state.

What's fixed

• Writes now apply instantly, and the integration waits a short moment before re-checking the cloud state.
• If a refresh was already in flight when you made a change, that stale result is now thrown away instead of overriding your newer change.
• Rapid batches of changes get coalesced into a single refresh instead of one refresh per setting — so bulk scripts are much lighter on the API.

The result: no flicker, whether you change one thing or a whole batch.

📝 Upgrade Notes

• No breaking changes or configuration needed — update via HACS as usual and you're done.
• Both 1.3.0 and 1.3.1 are included in this single update.

GitHub Repository & Documentation: https://github.com/ccpk1/controld-manager-ha

Home Assistant Community Thread: https://community.home-assistant.io/t/controld-manager-dns-orchestration/1002714/7

❤️ Support the Project

If Control D Manager is making your home better, I'd genuinely appreciate the support:

• ⭐ Star the repository to help others find it: https://github.com/ccpk1/controld-manager-ha
• ❤️ Sponsor on GitHub: https://github.com/sponsors/ccpk1
• ☕ Buy me a coffee: https://buymeacoffee.com/ccpk1

Enjoy — and let me know how Control D is working for you!