YoLink resources
YoLink with Home Assistant
Connect supported YoLink devices to Home Assistant, check the entities and actions you need, then test a complete automation.
Before you start
Check YoLink first
Add your devices in the YoLink app. Confirm the required hub is online and that a device reports or responds there.
Have Home Assistant ready
Use your running Home Assistant instance. Find your exact model in the maintained YoLink device list ↗.
Use your app account
Link the YoLink account that owns the devices. Your store or support-portal login may be different.
Add the built-in YoLink integration
Open Devices & services
In Home Assistant, open Settings → Devices & services, then choose Add Integration.
Select YoLink
Search for YoLink and start the account-linking flow.
Sign in and authorize
Use your YoLink app account and complete the prompts. The default linking service is provided by Nabu Casa without requiring its subscription.
Check one device, then one automation
Find a supported device and confirm its entity state changes. Build a simple automation with a harmless test action, such as a notification, before expanding it.
Custom credentials are optional. Start with normal account linking. YoLink User Access Credentials (UAC) are not the application credentials for this integration. See Home Assistant’s application-credential guidance ↗ if support directs you to a custom setup.
Cloud integration and local control are different
Home Assistant classifies the built-in YoLink integration as Cloud Push. Connecting an account does not turn that integration into an offline local connection.
Check the model
A device family name is not enough. Verify the exact model and the functions exposed by your installed integration.
Check where the rule runs
Home Assistant automations, YoLink app automations, Control-D2D pairing and Local Hub setups are separate paths. Do not assume rules transfer between them.
Check outage behavior
Before relying on a response during an outage, confirm which hub, device power, internet connection and automation host it needs.
Official YoLink integration: models, actions and connection notes ↗ · Find your model’s manual →
Check the model and the function
| Product | What you can use | Requirements and limits |
|---|---|---|
| SpeakerHub (YS1604) | Use the built-in integration’s Play on SpeakerHub action for text-to-speech. | Requires the cloud connection and powered, online SpeakerHub. It does not turn SpeakerHub into an offline local speaker. |
| FlexFob (YS3604F) | Use device triggers for short and long presses on buttons 1–4. | Reviewed in Home Assistant 2026.10.2. Select the available device trigger; do not look for an on/off control for a physical button. Older releases may differ. |
| Local Hub (YS1606) | Use configured local automations and the separate Local API/Matter paths described by YoSmart. | The built-in YoLink integration remains Cloud Push. This guide does not certify an alternative local adapter or every Matter device/function. |
FlexFob manual ↗ · Local Hub manual ↗ · Home Assistant integration ↗
Troubleshooting
Which login or credentials should I use?
Use the normal YoLink sign-in flow first. Confirm you can access the devices in the YoLink app using that account. Do not enter a UAC in place of an application client ID and secret.
If you have lost access to the app account or its email address, contact support for account recovery. Repeatedly creating credentials will not recover account ownership.
Authorization stalls or shows “Coming Soon”
Record the exact page and error, plus your Home Assistant version. Check whether you started normal account linking or entered custom credentials. Return to the built-in flow if you used UAC.
If normal linking still fails, contact support with those details. Optional custom application credentials require the correct issued client ID and secret; do not substitute an unrelated key or publish credentials in a forum.
Will a Local Hub make this work without internet?
Not automatically. This guide covers the built-in cloud integration. A Local Hub’s separate capabilities do not establish that the connection you configured in Home Assistant is local.
Confirm the exact integration path and supported model/function before planning an outage response. Keep existing YoLink rules and direct device pairing separate when checking where an automation runs.
A device appears, but a reading or action is missing
Check the exact model and installed Home Assistant release. Inspect the entities and actions actually available for that device, rather than assuming everything in the YoLink app is exposed.
If a required function is absent, send support the model, version and intended task. Account linking alone does not confirm feature support.
Devices are present, but their states stop updating
First compare the same device in the YoLink app. If it is stale there too, begin with the device/hub connection. If only Home Assistant is stale, check its integration errors and the documented network requirements ↗, especially on networks using a firewall, proxy or VPN.
Note when updates last worked and what changed before the problem began.
Running actions works, but the automation does not trigger
Run actions is not a complete trigger test. Confirm the automation is enabled, cause the real event it watches, then inspect its trace for the trigger, conditions and actions. A time window or condition is not itself the device event.
Use Home Assistant’s automation testing and traces guide ↗ to see where the sequence stops.
Still need help?
Send the details that separate a connection issue from an automation issue:
- Device and hub models; whether they work in the YoLink app.
- Home Assistant version and whether you used normal or custom account linking.
- The missing entity/action, exact error and time of the problem, including time zone.
- Whether you expect cloud access or an offline local response.
Remove tokens and secret keys from logs or screenshots before sharing them.