Allow more than one Home Assistant Cloud (Home Assistant Link) subscription per Nabu Casa account?

[Hedda]

Describe your request

Please allow a single Nabu Casa account account to hold multiple Home Assistant Cloud / Home Assistant Link subscriptions (and installations).

• https://support.nabucasa.com/hc/en-us/articles/26178633145885-Can-I-use-a-single-account-for-multiple-Home-Assistant-installations

The problem is that today a Nabu Casa account can currently only holds one Home Assistant Cloud subscription (soon Home Assistant Link), and that subscription can only connects to a single Home Assistant instance. As I see this limitation gets in the way of primarly two things:

1. Several homes, one person. Anyone who looks after more than one instance (a summer house, a parent's home, a small office/business) will in practice need to setup several separate Nabu Casa accounts, email addresses, passwords, payment method and renewal date for each.

2. Paying for more subscriptions on purpose. The subscription is the main recurring way for an individual to help fund the Open Home Foundation. There are however many in the community that expressed an interest to pay a little more each month as a way to donate money towards the Home Assistant project. If the OHF and Nabu Casa could offer more than one subscription per account than what might actually be utilized then those extra "donation" subscription would be an extra recurring income to the Open Home Foundation.

Both ideas and reasoning came up in the replies on the recent rename announcement blog post which mentioned improvements to the service:

• https://community.home-assistant.io/t/big-tech-ruined-the-cloud-so-we-re-renaming-ours/1027150

  "We’re also constantly improving the service and are now working to add new features. You may have noticed the new, easier-to-use account page, the speech-to-text Labs test, or the new settings page in Home Assistant with a setup wizard. What you probably won’t notice is the massive backend update to improve the responsiveness of your remote access (we’ve migrated to a new bare-metal setup that always tries to get you on the closest server, and it’s fast 🏎️). Most importantly, these updates let us add new security features, account management tools, and more."

Remember that subscribing should be made easy since this mainly exists to fund the Open Home Foundation and development of all its projects, (which are not limited to Home Assistant but also also include Music Assistant, ESPHome, Matter.js, Z-Wave JS, and ZHA + more many projects).

Why the uncertainty?

I guess that this is more of a feature request to the partnership between Nabu Casa and the Open Home Foundation than for Home Assistant?

Billing and maintaining the server-side cloud service is all done by Nabu Casa, not the OHF, so perhaps they can be redirected to this request?

Anyway, the issue is not really with Home Assistant's core or hass-nabucasa but in Nabu Casa's "Home Assistant Link" back-end cloud services.

Use cases and possible solution

Let one account hold several subscriptions, set as a quantity on the account page.

• Each subscription is a slot for one instance, with its own remote URL and backup storage, working as a single subscription does today.
• The account page lists the slots, shows which instance uses each, and lets me name them ("Home", "Summer house", "Parents").
• One payment method, one invoice and one renewal date cover all of them.
• A slot with no instance connected is fine. It is simply extra support for the project.
• When signing in from Home Assistant on an account with several slots, the user who logs in there picks which one this instance uses.

Nothing changes for people with a single subscription, and nothing changes in how Home Assistant runs locally.

What areas might this affect?

• The recent rename blog post says the majority of subscription profit goes to the Open Home Foundation, and that the service was built so funding would not depend on asking for donations. A quantity field stays within that model: people who want to give more buy more of the same thing, and no separate donation system is needed.
• Multi-home setups are common among people who act as family tech support, which is where easy remote access, off-site backups and human support matter most.
• The companion apps (or at least the Home Assistant companion app and the Music Assistant companion app) can already handle multiple servers, so from an end-users point-of-view just allowing multiple subscriptions from a single account is the only missing piece.

Anything else?

Alternatives and workarounds:

• One account per instance, using email aliases. Works, but spreads logins, cards, invoices and renewal dates across accounts, and gets worse with each home.
• Self-managed remote access (VPN or reverse proxy) for the extra homes. Works, but adds maintenance at a site I am not at, and does not support the project.
• Merch and official hardware. One-off purchases, not recurring support.
• A "supporter" top-up on the existing subscription. Would cover the funding case but not the multi-home case.

Notes:

• Open question: Alexa and Google Home account linking would need a way to choose which instance a linked account talks to.
• I realise accounts and billing are Nabu Casa's side, not Home Assistant Core, so please move this if there is a better place. I am posting now because feedback on Link was invited before the 2026.12 release.

References:

• https://www.home-assistant.io/cloud/
• https://www.nabucasa.com/link/

[beenish-majeed]

This is a valid Nabu Casa feature request, but it belongs on the Nabu Casa account/backend side, not in Home Assistant Core.

There is already an existing issue for essentially this request: Nabu Casa single account to manage multiple instances (#235). It was opened in 2021 and closed in September 2023. As I read it, the reason given was that supporting this would need a large refactor on the cloud side and wasn't feasible at the time.

The current support documentation still describes the same limitation: each Home Assistant installation needs its own Nabu Casa account and subscription, and using one account on several installations can leave all but one without active service.

This is not just a billing or UI limitation. As far as I can tell from the hass-nabucasa code, the current model ties one account to one authenticated cloud identity, one instance connection and one subscription state. The feature therefore needs an account model more like this:

text
Nabu Casa account
├── Link subscription / slot 1 → Home Assistant instance A
├── Link subscription / slot 2 → Home Assistant instance B
└── Link subscription / slot 3 → unassigned

Billing could aggregate the slots under one payment method and renewal date, while each slot keeps its own remote URL, backups and cloud connection, exactly as a single subscription does today.

So the real request is:

Allow one Nabu Casa account to own multiple independent Home Assistant Link subscriptions/instance entitlements, while preserving the current one-instance-per-subscription behavior.

A quantity field on the account page is the UX/billing way to deliver that, not the feature itself.

The multi-home use case is the core of this. Anyone looking after several instances (a second home, a parent's house, an office) would need only one login, one payment method and one renewal date.

The "pay more to support the project" use case is a separate goal. Unused slots could serve it, but it raises its own questions about how they are described and accounted for. A separate supporter add-on would cover it without depending on multi-instance support, so I'd treat it as optional here and not as a reason for the feature.

Design questions to settle if this is revisited:

Slot reassignment: what happens to the remote URL and backups when a slot moves to a different instance.
Alexa and Google Home: linking currently assumes one instance per account, so it would need a way to choose which instance is linked.
Sharing limits: whether slots are meant for one person's or household's instances, to avoid accounts being shared out.

Suggested next step: since Link is being reworked ahead of 2026.12, it may be worth asking Nabu Casa whether the 2023 conclusion still holds, and whether #235 should be reopened or a new issue opened. That is the better place to track this, since the limitation sits in Nabu Casa's account, subscription and cloud-service architecture.

References

Nabu Casa Support: Can I use a single account for multiple Home Assistant installations?
Issue #235
Home Assistant Link
Rename announcement thread