Good to know
The small code under Offline tells support exactly what failed. If you write to us, a photo of the watch helps.
Tutorial 100:47
When something's wrong
When something doesn't work, the watch says what it is. Here is what each message means, and the fix for it.
Step by step
-
No devices selected
Every device starts hidden: switch on the ones you want in Devices, in the AmazHA settings.
-
Offline · No answer from the phone
The watch can't reach your phone. Keep the phone nearby, with Bluetooth on and the Zepp app running.
-
Offline · Home Assistant unreachable
Your phone can't reach Home Assistant. Open your address in the phone's browser: it must work from where the phone is, and away from home it needs https with a valid certificate.
-
Wrong address
The address answers, but it isn't the Home Assistant API. Use only the server address, with nothing after it (no /lovelace).
-
Admin token needed
The token belongs to a user without administrator rights. Create a new long-lived token as an administrator and paste it in.
-
Check the token
The token has a character no token has, usually from a shortened copy (…). Copy it again, all of it, and paste it.
-
The watch is slow or restarts
Too many devices. Keep the selection small: a few dozen stay fast, and 100 is the limit.
-
Still stuck? Reset cache & local data
In Preferences, tap Reset cache, then Tap again to confirm. It clears the cached data on the watch and the phone, and keeps your connection, devices and license. Then reopen AmazHA on the watch.