AmazHA, a Home Assistant app for Amazfit watches, runs on a fixed list of Zepp OS models. That list is not a guess or a marketing claim: it is the list of watches the app’s package is built for, the same one the Zepp App Store uses to decide who can install it. This page goes through it model by model.
The short answer
AmazHA works on 25 Amazfit models with Zepp OS, square and round: the GTS 4 and GTR 4, the Bip 6 and Bip Max, the Falcon, and models from the Active, Balance, Cheetah and T-Rex lines. Every one gets the same app and the same screens. The Active Edge, Bip 5 and T-Rex 2 are not supported, and neither are watches below Zepp OS API level 3.0.
If you only want to know about your own watch, find it in the table below, or skip to how to check your watch in two minutes.
The full list
All 25 supported models, with their shape and the screen size AmazHA draws for. Every row is a yes.
| Model | Shape | Screen (pixels) | AmazHA |
|---|---|---|---|
| Active | Square | 390×450 | Yes |
| Active 2 | Square and round | 390×450 (square), 466×466 (round) | Yes |
| Active 2 Golf | Round | 466×466 | Yes |
| Active 3 Premium | Round | 466×466 | Yes |
| Active Max | Round | 480×480 | Yes |
| Balance | Round | 480×480 | Yes |
| Balance 2 | Round | 480×480 | Yes |
| Balance 2 XT | Round | 480×480 | Yes |
| Balance 3 | Round | 480×480 | Yes |
| Balance 3 Ti | Round | 480×480 | Yes |
| Balance Ultra | Round | 480×480 | Yes |
| Bip 6 | Square | 390×450 | Yes |
| Bip Max | Square | 432×514 panel, apps see 390×450 | Yes |
| Cheetah 2 Pro | Round | 466×466 | Yes |
| Cheetah 2 Ultra | Round | 480×480 | Yes |
| Cheetah Pro | Round | 480×480 | Yes |
| Cheetah Round | Round | 454×454 | Yes |
| Cheetah Square | Square | 390×450 | Yes |
| Falcon | Round | 416×416 | Yes |
| GTR 4 (and GTR 4 LE) | Round | 466×466 | Yes |
| GTS 4 | Square | 390×450 | Yes |
| T-Rex 3 | Round | 480×480 | Yes |
| T-Rex 3 Pro | Round | 466×466 (44 mm), 480×480 (48 mm) | Yes |
| T-Rex Ultra | Round | 454×454 | Yes |
| T-Rex Ultra 2 | Round | 480×480 | Yes |
Variants count as the same watch
The manifest behind this list names many more entries than 25, because Amazfit sells the same watch under several firmware identities. They are all covered:
- Regional editions, the ones marked (W), (WN) or (W64) in the app’s manifest, are the same watch as the model they belong to.
- NFC editions: the Active 2 NFC (square and round) is the Active 2.
- The GTR 4 LE is listed with the GTR 4, and the Cheetah Pro KK with the Cheetah Pro.
- Case sizes: the T-Rex 3 Pro comes in 44 mm and 48 mm with different screens, and both are supported.
The same list is on the home page, under Supported watches. It is read from the app’s own manifest every time the site is built, so the two cannot disagree.
Where the list comes from
The list is every Amazfit watch that Zepp’s developer tools register with API level 3.0 or newer, minus three models left out on purpose (more on those below). AmazHA declares API level 3.0 as its minimum, which is why older watches are not on it at all.
A watch Amazfit releases later is not supported automatically. It has to be added to the list and a new version of AmazHA published; until then the Zepp App Store will not offer the app on it.
Family by family
The answer for each line, with the details that differ between models. If your model is here, AmazHA runs on it.
Active
All the Zepp OS Active watches are supported except the Active Edge.
- Amazfit Active: yes. Square, 390×450.
- Amazfit Active 2: yes, in both shapes. The square Active 2 and Active 2 NFC Square use the 390×450 layout; the round Active 2 uses the 466×466 one.
- Amazfit Active 2 Golf: yes. Round, 466×466.
- Amazfit Active 3 Premium: yes. Round, 466×466.
- Amazfit Active Max: yes. Round, 480×480.
- Amazfit Active Edge: no. Its 360×360 screen is too small (see not supported, and why).
The Active 2 is the only model on the list sold in both a square and a round version. The two run the same app, drawn for their own screen, so what you see differs only in layout, not in features.
Balance
Every Balance model is supported, and all of them share the 480×480 round group.
- Amazfit Balance: yes.
- Amazfit Balance 2: yes.
- Amazfit Balance 2 XT: yes.
- Amazfit Balance 3: yes.
- Amazfit Balance 3 Ti: yes.
- Amazfit Balance Ultra: yes.
Because they share a screen size, every Balance gets the same build of the app. The Balance 3, Balance 3 Ti and Balance Ultra are newer than the others and receive exactly what the Balance 2 receives.
One note for the original Balance, and only if you use watch sensors in the background: on Balance firmware 2.0.0, background updates stop after a watch restart until the next restart. It is a fault in that firmware’s service timer, not something an app can fix, and newer Balance firmware no longer has it. Keep the watch up to date and it does not apply. Everything you do with the app open works either way.
Bip
Two Bip models are supported: the Bip 6 and the Bip Max. The Bip 5 is not.
- Amazfit Bip 6: yes. Square, 390×450, the same screen size AmazHA’s layout is designed on.
- Amazfit Bip Max: yes. Square, with a 432×514 panel.
- Amazfit Bip 5: no. Its 320×380 screen is too small.
The Bip Max deserves a word. It runs apps written for API level 3 on a virtual 390×450 canvas: on its 432×514 panel, the watch tells the app that its screen is 390×450. AmazHA measured this on a real Bip Max. In practice the Bip Max shows the same layout as a GTS 4 or a Bip 6.
That canvas once caused a real bug: the icon set was sized for the physical panel, the app drew at the virtual canvas’s sizes, and some icons came out blank. AmazHA now ships the Bip Max an icon set that covers both sizes, and checks that the file it is about to draw exists, falling back to a size it knows is there.
Cheetah
Every Zepp OS Cheetah model is supported, in three screen sizes.
- Amazfit Cheetah Square: yes. Square, 390×450.
- Amazfit Cheetah Round: yes. Round, 454×454.
- Amazfit Cheetah Pro: yes. Round, 480×480 (the Cheetah Pro KK too).
- Amazfit Cheetah 2 Pro: yes. Round, 466×466.
- Amazfit Cheetah 2 Ultra: yes. Round, 480×480.
The Cheetah 2 Ultra shares the 480×480 group with the Balance 2 and T-Rex 3; the Cheetah 2 Pro shares the 466×466 group with the GTR 4 and the round Active 2.
Falcon
The Falcon is supported. It is the only model in AmazHA’s 416×416 round group.
- Amazfit Falcon: yes. Round, 416×416.
- Falcon 2: no watch by that name is on AmazHA’s list. The list names only the Falcon. If you have a watch sold under another Falcon name, use the two-minute check below: the App Store is the final word.
At 416×416 the Falcon has the smallest round screen on the list. Everything fits; if you would like bigger text, see square or round for the Font size and Card size preferences.
GTR 4 and GTS 4
The GTR 4 and the GTS 4 are both supported, and the GTS 4 is the reference watch for the whole app.
- Amazfit GTS 4: yes. Square, 390×450.
- Amazfit GTR 4: yes. Round, 466×466. The GTR 4 LE is listed with it.
- Amazfit GTS 4 Mini: not on the list.
The GTS 4 is where AmazHA started. Its 390×450 screen is the design canvas every layout is drawn on and then scaled to the other screens, the interactive demo on the home page is a GTS 4, and it is the developer’s own watch: the current version was checked on it, item by item, before release.
Older GT models, such as the GTS 2, GTR 2, GTS 3 or GTR 3, are not on the list. If AmazHA does not appear in your watch’s App Store, your watch is not supported.
T-Rex
The T-Rex 3, T-Rex 3 Pro, T-Rex Ultra and T-Rex Ultra 2 are supported. The T-Rex 2 is not.
- Amazfit T-Rex 3: yes. Round, 480×480.
- Amazfit T-Rex 3 Pro: yes, in both sizes. The 44 mm model uses the 466×466 layout, the 48 mm model the 480×480 one.
- Amazfit T-Rex Ultra: yes. Round, 454×454.
- Amazfit T-Rex Ultra 2: yes. Round, 480×480.
- Amazfit T-Rex 2: no, for memory reasons (below).
If you search for “T-Rex” on its own: the current models work, the T-Rex 2 does not, and for anything older the App Store check below gives the answer.
What every supported watch gets
Every supported model runs the same app: the same screens, the same widget, the same watch sensors. The six screen groups differ only in layout and icon sizes, never in features.
That follows from how AmazHA is built. The watch never talks to Home Assistant itself: it talks to the Zepp app on your phone over Bluetooth, and the phone does all the networking. So nothing about the connection depends on the watch model, and the watch does not need Wi-Fi.
On any of the 25 models you get:
- Your home by room, or as a Favorites list, with a control screen for each kind of device: lights, switches, climate, covers, vacuums, alarm panels, sensors, media players, fans, locks, scenes, scripts, buttons, automations, cameras, trackers and dropdown helpers (
selectandinput_select). That is 17 device types. - The widget on the watch face: up to four devices on the watch’s shortcut cards, one tap away. The widget is declared for every one of the six screen groups.
- Watch sensors in Home Assistant: steps, heart rate, sleep, battery and more, sent through Home Assistant’s Mobile App integration. A reading a watch cannot give is simply left out; nothing breaks. The watch sensors article covers all 18.
- The same limits: the phone has to be nearby, and the device list is capped at 100. A few dozen devices stay fast on every model; keeping the selection small is the advice for all of them, not just the smaller screens (see the troubleshooting tutorial).
How it was checked
Before the current version was released, a tour of every kind of screen was run on the real firmware of 19 Amazfit models in Zepp’s simulator, which runs each watch’s own firmware rather than an imitation. It passed on all 19. Longer runs, about 130 screens in one session, were done on the GTS 4, Cheetah Square, T-Rex Ultra, Cheetah Pro, Falcon, GTR 4, Balance 2 and Active 2 Square, with no black screen. The models without a simulator image of their own, such as the newest Balance models, get the same package as the model they share a screen group with.
Square or round: what changes on the screen
AmazHA has one design, drawn on a 390×450 canvas and scaled to each screen. On square watches it fills the screen; on round ones the titles are centred and the lists use the whole glass.
Here is what that means in detail.
| Square watches | Round watches | |
|---|---|---|
| Layout | The 390×450 design, scaled to fit the screen | The same design, scaled into a centred band that keeps clear of the curved edge |
| Screen header | Back arrow left, title left-aligned | Back arrow moved in from the curve, title centred |
| A long title | Left-aligned after the arrow | Moves to the left after the arrow and uses the room up to the glass, instead of scrolling |
| Device tiles and room rows | Full width with a margin | Widened into the sides, to about 30 pixels from the edge of the glass |
| Sliders, chips, fixed controls | Full design width | Stay in the centred band |
| End of a list | Ends at the last row | A little extra space after the last row |
| Section labels | Left-aligned | Centred |
| Widget on the watch face | Drawn in the frame the watch gives it | Kept inside the round glass, also on watches whose frame spans the whole width |
The back gesture and the header
On both shapes, a right swipe goes back. On the control screens, a tap anywhere on the header goes back too, not only a tap on the small back arrow. The get around the watch tutorial shows it. On a round watch that matters more: the top of the circle is narrow, and the whole header band is a bigger target than the arrow.
Why round titles were changed
On a 480×480 round screen, the space between the back arrow and its mirror image on the other side is narrow. A room called “Bedroom” did not fit there, and Zepp OS scrolls text that does not fit as a marquee. Now a title that does not fit centred moves left and takes the space after the arrow, as on square watches. Short titles stay centred. The same update made room chips such as a temperature reading grow to fit their value, so “19.8°C” stays whole and still.
Icons drawn for each screen
Zepp OS draws images at their native size, with no scaling at run time. So AmazHA does not ship one set of icons for everyone: each of the six screen groups gets its own icon pack, drawn in advance at the exact pixel sizes that screen uses. That keeps icons sharp on a 416×416 Falcon and on a 480×480 Balance alike.
Bigger text and cards, on any shape
If the text feels small on your screen, two preferences help on every model, in the AmazHA settings under Preferences (tutorial):
- Font size makes every text on the watch bigger: 110%, 120% or 130%.
- Card size enlarges the home’s area cards and the device tiles: 115%, 130% or 145%.
Rows grow with the text, so bigger glyphs keep their spacing. A new size takes effect the next time you open AmazHA on the watch.
Not supported, and why
Three Zepp OS models are left out on purpose, and every watch below API level 3.0 is out of scope. Here are the reasons.
| Watch | AmazHA | Why |
|---|---|---|
| Active Edge | No | Screen too small: 360×360 |
| Bip 5 | No | Screen too small: 320×380 |
| T-Rex 2 | No | Not enough memory: 32 MB of RAM, against the 128 MB of the GTS 4 |
| Watches below Zepp OS API level 3.0 | No | AmazHA needs API level 3.0 or newer |
| Any model not in the list above | No | Not in the app’s manifest, so the store does not offer it |
Screen too small: Active Edge and Bip 5
AmazHA’s layout is designed on 390×450 and scaled to each screen, keeping its proportions. On a 360×360 or 320×380 screen it shrinks past the point where room names, tile states and buttons read comfortably. The choice was to leave those two out rather than ship something that reads badly.
Memory: T-Rex 2
The T-Rex 2 has 32 MB of RAM; AmazHA’s floor is the GTS 4’s 128 MB. It is not a platform restriction, since third-party apps do run on the T-Rex 2. It is a choice not to ship a degraded experience.
Why not a lighter version for it? On a Zepp OS watch, the system, the watch face and every app share one small memory space for their code, a few megabytes on the watches whose firmware AmazHA has examined. AmazHA’s load is not in the control screens, which a light version could trim: it is in keeping the watch in sync with Home Assistant and in the background layer. Trimming the screens would not make it fit, so a light version is not planned.
Older watches
Watches whose Zepp OS is older than API level 3.0 cannot run AmazHA, because the app declares 3.0 as its minimum. Models without Zepp OS cannot run Zepp OS apps at all. For any named older model, the reliable test is the store: if AmazHA does not appear in your watch’s App Store, your watch is not supported.
Wear OS
AmazHA is for Amazfit watches with Zepp OS. A Wear OS version is in development, with no date.
How to check your watch in two minutes
Search for AmazHA in the Zepp app’s App Store with your watch connected. If it is listed, your watch is supported; install it and the free demo shows how it runs on your screen before you pay anything.
Step by step:
- Open the Zepp app on your phone, with your watch paired and connected.
- Open the App Store, the store of apps for your watch inside the Zepp app.
- Tap the search icon and type AmazHA.
- If the result AmazHA — Home Assistant Companion App appears, your watch is supported.
- Tap Install. It is free.
- On the watch, open the list of apps and tap AmazHA.
The app opens on a demo home with rooms and devices. Every screen works on sample data: open a room, flip a switch, try a light’s brightness or a thermostat. This is the real app, on your real screen, so it answers the question “does it look right on my watch?” better than any table. The demo needs no Home Assistant and no payment.
If the demo looks good, the next step is a one-time unlock, with no subscription: tap the orange Demo mode · no license banner on the watch and follow the unlock tutorial. The site’s pricing section has the details.
If AmazHA does not show up in the store
| What you see | What it means | What to do |
|---|---|---|
| No result for AmazHA | Your watch is not on the list | Check the table above; if your model is missing, it is not supported |
| Install does not finish | The app travels from the phone to the watch over Bluetooth | Keep the phone nearby with Bluetooth on, and try again |
| AmazHA opens on sample rooms | That is the demo, as intended | Unlock it and connect your Home Assistant |
How to install an app on an Amazfit
Apps for Zepp OS watches are installed from the phone: open the Zepp app, open its App Store, find the app and tap Install. The app is sent to the watch over Bluetooth while the phone shows the progress. No computer and no cable are needed.
This works the same for every app and every Zepp OS watch. For AmazHA:
- Before you start: your watch is paired with the Zepp app on your phone, with Bluetooth on and the phone nearby.
- Open the Zepp app, the companion app of your watch (step 1).
- Open the App Store, inside the Zepp app (step 2).
- Search for AmazHA: tap the search icon and type the name (step 3).
- Open the result, AmazHA — Home Assistant Companion App (step 4).
- Tap Install and wait for the transfer to finish (step 5).
- Open it on the watch: press the button to open the list of apps, then tap AmazHA (step 6).
An app’s own settings live in the Zepp app too. For AmazHA they are at Profile › your watch › Apps › AmazHA › Settings: that is where you connect your Home Assistant, choose the devices the watch shows and set the preferences.
Updates arrive through the same store. After an update, restart your watch once.
After installing: from demo to your own home
Once the app is on your watch, connecting it to your Home Assistant takes three tutorials, whatever the model:
- Unlock the full version: a 5-digit code on the watch, paid once on kzl.io/code.
- Connect Home Assistant: in the AmazHA settings, tap Home Assistant, enter your Local URL (LAN) and, if you want it away from home, a Remote URL, paste a Long-lived access token and tap Connect.
- Choose your devices: every device starts hidden, so switch on the ones you want on the watch.
Two things trip people up at the connect step, and neither depends on the watch:
- The token must come from an administrator. AmazHA reads your areas through Home Assistant’s template API, which Home Assistant reserves for administrators. With a regular user’s token the connection test passes but the watch loads no devices, and it shows Admin token needed. The long-lived access token article explains it.
- At home, the local address is enough. AmazHA uses your local address while the phone is on your home network. A remote address is only needed for using the watch away from home; the remote access article compares the options.
Picking a watch for Home Assistant
If you are choosing a watch partly for Home Assistant, any of the 25 does the job, because the app and its features are the same on all of them. What differs is the screen, and that comes down to taste.
A few points from the list itself:
- Square or round. The square watches (390×450, and the Bip Max) show AmazHA at the size it was designed for. The round ones show the same screens with centred titles and lists that run to the edge of the glass. Neither shape loses a feature.
- Screen size. The round screens on the list run from 416×416 (Falcon) to 480×480 (Balance, Cheetah Pro, T-Rex 3 and others). Every screen shows the same layout, scaled to its size; Font size and Card size make any of them easier to read.
- Newer and older generations. The list spans older watches like the GTS 4 and GTR 4 and the newest Balance 3 and Balance Ultra. AmazHA runs on both firmware generations; the minimum is Zepp OS API level 3.0.
- Avoid the three exclusions if Home Assistant matters to you: Active Edge, Bip 5 and T-Rex 2.
This page compares watches only as far as AmazHA is concerned. Battery life, sensors, buttons and materials are Amazfit’s to describe, and they are not covered here.