Home Assistant Cloud Is Now Link: What the Rename Means

Home Assistant has renamed its Home Assistant Cloud service to Home Assistant Link. The change gives the cloud-connected service a new identity, but current reporting does not confirm every practical detail about pricing, accounts, subscriptions, migration, or technical architecture.

The rename matters because Home Assistant Cloud has been associated with remote access, push notifications, voice integrations, and other services that connect a local Home Assistant installation to the outside world. The word “Cloud” describes the infrastructure involved. “Link” may better describe the service’s purpose: connecting a Home Assistant system with users, devices, and external services.

Existing users should separate confirmed information from assumptions. Home Assistant Link is the reported new name for Home Assistant Cloud, but the name alone does not prove that every feature, account process, or network behavior has changed. Consult current Home Assistant documentation before changing a stable installation.

What Is Home Assistant Link?

Link Replaces the Home Assistant Cloud Name

The central change is straightforward:

• Former name: Home Assistant Cloud
• New name: Home Assistant Link

The Verge reported that Home Assistant renamed its Cloud service to Link, although the report provided limited additional information about the rebranding. Source 1

Users may continue to see the old name in tutorials, forum posts, screenshots, configuration guides, and search results. Those references may remain useful if they describe the same service and an older interface.

A name change can create short-term confusion without requiring a technical migration. Settings may receive new labels, documentation may be updated, and account pages may begin using “Link.” None of these changes automatically means that users must rebuild their Home Assistant configuration.

What Current Reports Confirm

The available reporting supports three main points:

1. Home Assistant Cloud has been renamed Home Assistant Link. Source 1
2. Another report connects Link with cloud-based connectivity for mainstream push notifications and describes the change as potentially supporting local control and privacy. Source 2
3. The rename appears alongside broader efforts to make Home Assistant easier for newcomers. MakeUseOf reported on changes intended to reduce the platform’s setup complexity and intimidation factor. Source 3

These reports do not provide a complete technical specification for Link.

What Has Not Been Confirmed

The available information does not confirm:

• A new subscription price
• A new account system
• A mandatory migration process
• A complete move away from cloud infrastructure
• A universal replacement for every remote-access method
• Changes to all notification types
• Changes to regional availability
• A requirement to upgrade every Home Assistant installation

Check current Home Assistant release notes, account pages, and Link documentation for exact implementation details.

Why Did Home Assistant Change the Name?

“Link” Better Describes the Service’s Role

“Cloud” emphasizes hosted infrastructure. “Link” emphasizes the connection between a Home Assistant installation and the people or services using it.

That wording may be easier for new users to understand. Someone configuring remote access may not need to think about cloud architecture; they need a reliable link to their home. The name also describes a broader role that can include remote access, notifications, account services, and integrations.

This is strategic context rather than a confirmed explanation from Home Assistant. The available reports establish the rebrand but do not publish a detailed official rationale.

The Rename Fits a Usability Push

Home Assistant is powerful, but its flexibility can make setup difficult. New users may need to choose hardware, install the software, add integrations, understand entities and services, configure backups, manage users, and troubleshoot automations.

Remote access adds another layer. Users may choose between a managed service, a virtual private network, a reverse proxy, or another self-managed method. Notifications can introduce additional account, mobile-app, and internet dependencies.

A clearer name may reduce confusion during onboarding. It can help users answer practical questions:

• How do I access Home Assistant away from home?
• How do I receive notifications?
• Do I need to expose my home network?
• Which automations work locally?
• Which features depend on an internet connection?

The change therefore fits the usability concerns described by MakeUseOf. Source 3

Local-First Smart Homes

The Link name also appears during wider interest in reducing dependence on cloud-connected smart-home products. WIRED described replacing cloud-dependent smart-home systems with locally managed setups, reflecting demand for greater control, reliability, and privacy. Source 7

Local control and remote connectivity are separate goals. A service can provide a secure remote connection while local automations continue running on the Home Assistant system. Conversely, a device can use local control while remote access still requires an internet connection.

Link’s name does not prove that all processing occurs locally. Evaluate its documented behavior rather than inferring architecture from branding.

What Changes for Existing Users?

Existing users may see “Link” in Home Assistant settings, onboarding screens, account pages, subscription management, remote-access settings, notification documentation, and mobile-app instructions.

Older references to Home Assistant Cloud may remain valid during the transition. Compare the listed features and settings instead of assuming that the renamed service is an entirely new product.

The available reports do not confirm whether users must create new accounts, resubscribe, or update billing information. Before making changes, verify:

• Whether an existing subscription continues automatically
• Whether payment details remain unchanged
• Whether account credentials transfer
• Whether renewal dates change
• Whether trial periods continue
• Whether regional availability differs
• Whether new consent or terms-of-service steps appear

Do not cancel an existing subscription solely because the service name changed. Wait for explicit migration instructions from Home Assistant or a clear notice in the account portal.

Remote Access

A rename may not require users to rebuild remote access, but current documentation should determine that. Before changing settings:

1. Review release notes and confirm that a current backup exists.
2. Open the relevant Link settings page.
3. Test access from a mobile network rather than the home Wi-Fi network.
4. Confirm that household users can still sign in.
5. Check automations that depend on remote connectivity.
6. Review logs for authentication or connection errors.

Create a full backup before changing network or access settings. Store a copy outside the Home Assistant host and confirm that the backup is usable.

Notifications and Automations

Notification reliability matters for security alerts, door and window sensors, smoke detectors, leak sensors, presence automations, and system warnings.

After an update or service transition, test:

• Standard push notifications
• Notifications received away from home
• Notification actions
• Critical alerts
• Messages sent to multiple users
• Automations during an internet outage
• Delayed notifications after connectivity returns

Reports connect Link with cloud-based connectivity for mainstream push notifications, but they do not establish identical behavior for every installation or notification method. Source 2

Link, Local Control, and Privacy

Local control means that devices, automations, and commands operate within the home network or on the Home Assistant host. Remote connectivity means that a user accesses the system from outside the home.

Users may want both. Local control can improve speed, resilience, and privacy. Remote connectivity allows access while traveling and supports remote notifications or household management.

A Link connection does not necessarily move every device command into the cloud. Actual behavior depends on the integration, automation, device, network, and feature being used.

Important privacy questions include:

• What data leaves the home?
• Which features require an internet connection?
• Are device commands processed locally?
• What account information does the service store?
• How are remote sessions authenticated?
• What happens if the internet connection fails?
• Which third-party integrations have separate data policies?

Consult Home Assistant’s current privacy policy and technical documentation for definitive answers.

Internet Outages

Local automations may continue operating when the internet fails, provided they do not depend on external services. A lighting automation using local sensors may continue, while remote notifications, voice assistants, cloud integrations, or third-party APIs may stop working.

Run a controlled outage test when household members can respond manually:

1. Disconnect the internet while keeping the local network active.
2. Test lights, sensors, dashboards, and local automations.
3. Check which notifications fail.
4. Restore connectivity.
5. Review logs for errors and delayed events.

Do not perform this test during a safety-critical situation.

Is Home Assistant Link Easier for Beginners?

Home Assistant can become difficult when users combine multiple devices, integrations, dashboards, scripts, automations, and notification targets. Android Authority described an audit of a messy Home Assistant setup that revealed enough problems to prompt a major reassessment. Source 4

A managed connectivity service may reduce one part of that complexity, but it cannot solve every configuration problem.

Link may simplify remote access, secure connection setup, push notifications, account-based onboarding, and access for multiple household users.

Self-managed alternatives include port forwarding, a virtual private network, reverse proxies, and dynamic DNS. These options may provide more control but require maintenance, updates, authentication management, certificates, and security monitoring.

Self-managed access is not automatically safer. Security depends on configuration quality and maintenance discipline.

Users may still need to understand Home Assistant updates, restorable backups, integration permissions, device compatibility, network reliability, user roles, and automation troubleshooting.

AI-assisted configuration audits may help identify unused integrations, broken automations, or inconsistent naming. Review recommendations manually before implementation. The report about using Claude does not establish that Claude or another AI tool is an official component of Home Assistant Link. Source 4

Should You Use Home Assistant Link?

Link may suit users who want simpler remote access, less network configuration, managed connectivity, easier access for family members, and fewer publicly exposed network services.

Self-managed access may suit advanced users who already operate a virtual private network or reverse proxy. Reasons include greater infrastructure control, custom security policies, reduced dependence on a managed service, existing monitoring practices, and integration with an established home-lab network.

The choice depends on technical skill, privacy priorities, reliability requirements, and required features. A managed service can be secure, while a poorly configured self-managed system can create serious exposure.

How to Prepare for the Transition

Review current Home Assistant release notes, Link documentation, account and subscription pages, remote-access guidance, notification documentation, and privacy information. Secondary reports provide context but may omit account, version, or regional details.

Before changing connectivity settings:

• Create a full Home Assistant backup.
• Confirm that the backup completed.
• Store a copy separately from the Home Assistant host.
• Record user accounts and permissions.
• Document network settings.
• Note automation dependencies.
• Record notification targets.
• Securely preserve integration credentials.

A backup is useful only if it can be restored. Confirm the restoration process before relying on it during a migration.

Test local dashboard access, remote access, push notifications, notification actions, user permissions, and critical automations. Test an internet outage separately if local resilience matters. Review logs after each test and correct failures before relying on the system.

Update household instructions from “Home Assistant Cloud” to “Home Assistant Link,” keeping the old name in parentheses temporarily so users can recognize legacy tutorials. Avoid outdated instructions that expose Home Assistant directly to the public internet without current security guidance.

Conclusion

Home Assistant Cloud has been renamed Home Assistant Link. That is the confirmed central change.

Reports also connect Link with remote connectivity, push notifications, local control, privacy, and efforts to make Home Assistant easier for newcomers. They do not confirm every detail about pricing, accounts, subscriptions, migration, or technical architecture.

Keep the installation backed up. Review current Link guidance. Test remote access, notifications, user permissions, and local automations. Avoid changing a stable setup until official documentation explains whether a manual migration or software update is required.

Frequently Asked Questions

Is Home Assistant Cloud now called Home Assistant Link?

Yes. The available reporting identifies Link as the new name for Home Assistant Cloud. Verify current features and account details through Home Assistant’s official documentation. Source 1

Do existing users need to migrate to Link?

The available sources do not confirm whether a manual migration is required. Check the Home Assistant account page, release notes, and Link setup instructions before changing subscriptions or configurations.

Does Link make Home Assistant completely local?

Not necessarily. Link may support local-control and privacy goals, but its name does not prove that every feature operates locally. Remote access, notifications, voice services, and third-party integrations may still require internet connectivity.

Will Link change push notifications?

Reports connect Link with changes to cloud-based connectivity for mainstream push notifications. Test notifications after any update and consult current documentation for supported delivery methods. Source 2

Is Link required for remote access?

The available information does not establish that Link is mandatory for every remote-access configuration. Users may also use a virtual private network or reverse proxy, provided they understand the security and maintenance requirements.

Is Home Assistant Link worth using?

Link may suit users who want simpler remote access and less network configuration. Advanced users may prefer self-managed access for greater control. The right choice depends on privacy preferences, technical skill, reliability needs, and required features.