I'd like to share a project I've been working on: AmazHA, a native companion app that lets you control Home Assistant from an Amazfit watch.
The goal was a watch app that feels like part of Home Assistant rather than a bolt-on: your home is organised by area, and each entity gets a proper control screen.
What it does today
Control screens for lights, switches, climate, covers, vacuums, locks, media players, fans and alarm panels
Run scenes, scripts and buttons
Camera snapshots on the watch
A user-defined Favorites area
Local + remote URLs with automatic LAN-first failover
Optionally push watch health/activity data into HA as sensors (heart rate, SpO2, steps, calories, sleep, stress, etc.) to use in automations
Translated in 12 languages
Design notes
I leaned on the action-centric, per-entity icon+colour style so it's quick to read and operate on a small screen, and I put effort into launch speed and smooth scrolling.
Love the UI layout but ive noticed a few things compared with Tito Aguacatec version.
1-Theres no way to add the external HA address to be able to work away from home.
2- The switches toogles dont update, i.e. if i turn it on on the watch and then in home assistant i turn them back off the the state in the watch doesnt reflect that change. I didnt tested the AC units for example but i believe the behavior should be the same at this point?
3-Where do i find the sensors created in home assistant?
Thank you for this wonderfull app, im sure you will make it even better.
The external HA address option is already implemented in the update I released about four days ago. It's currently in the approval phase, so it should be available very soon.
Good catch on the toggle states. I'll double-check the syncing and make sure it's properly addressed in the next version.
The sensors show up in Home Assistant once the watch is connected and sensors are enabled in the app settings. You'll find them as entities in HA (search by the AmazHA device or the sensor names). If they don't appear, let me know and we'll dig into it together.
@Kokesh, about the Demo mode showing up on launch: this happens because the license check needs a moment to sync when the app starts, and tapping the banner forces that refresh. I'm looking into making the licensed state persist properly on startup so you won't see the demo screen at all. It'll be smoother in an upcoming update.
Thanks again to both of you, feedback like this is exactly what helps me improve AmazHA!
Thank you for really awesome app! I had already other apps, one for reporting my watch data to my HomeAssistant and another one for controlling it. But this one combines both
My problem with the demo mode is it is there practically every time I open the app. Can't you store some variable like paid=1 on the watch, so it doesn't have to sync the app license state every time?
You nailed exactly what was happening: the app was re-syncing the license state on every launch. I've already fixed this by storing the licensed state locally on the watch, so it won't fall back to demo mode anymore.
The fix won't make it into the update landing in the next few days (that one is already in review), so it'll come in the one right after.
I think the SPO2 sensor name is mangled, doesn't show up in HA. I think it tries to attach percent symbol in the end of the sensor name.
My device is BIP6.
Thanks for reporting this! I'll investigate it and make sure the sensor name is sanitized properly so it shows up correctly. I'll keep you posted once I have a fix.
Haha I really hope so too! Because the version currently in approval is 0.11.48, which sadly doesn't include these fixes yet. They'll land in the next release (0.11.6X), which I already have ready to go on my side.
The little catch is that I can't submit 0.11.6X until 0.11.48 gets approved first, so that part is unfortunately out of my hands. But the moment .48 clears, I'll push the next one right away. Thanks so much for your patience and for sticking with it!
If you want, you can send me the QR code for developer options install in Zepp App, it worked with ZeppHA developer, I've been testing some sync issues for him.
AmazHA 0.11.48 — big update is live (cameras, Favorites, local+remote, health→HA)
A major AmazHA update just landed on the Zepp App Store. Quick rundown of what's new since the first release:
New
Camera snapshots on the watch — enable a camera and tap to view; the phone fetches the image and sends it over BLE
Favorites area — pin any entities to the top of the home screen, regardless of their real room, with live search when picking them
Push watch health/activity into HA as sensor.* entities (heart rate, SpO₂, steps, calories, distance, sleep, stress, body temp, battery…) for your automations — fully opt-in.
Two HA URLs (local + remote) with automatic LAN-first failover on a single token
Improved / fixed
Alarm panel improved
Noticeably faster launch and smoother scrolling; per-tile repaint on toggle
Granting the background permission no longer freezes/reboots the watch
Still: free live demo on sample data, one-time unlock for the real HA connection (no subscription), 12 languages, wide square + round Zepp OS coverage (GTS 4, GTR 4, T-Rex 3 / Ultra, Balance, Cheetah, Active, Bip 6, and more).
As always, feedback on what to prioritise next is very welcome — thanks!
Hey, i have a little problem here, paid for the app and connected to my local home assistant server, also created long live token, everything goes normal before i try to open room (with server and all) but display just turns black and nothing happens, my device is amazfit active 2, would appreciate fixing! Already sent a report, but dont know where to find email to send a more inormative video.
Good news: this exact issue (Amazfit Active 2, everything fine until you open a room, then the screen goes black) has come up before, and it was solved without much trouble. Please try these steps in order:
Restart the watch (power it off and back on). This alone fixed it for another user with the identical symptom on the Active 2. It clears the system-level rendering state that causes the black screen, so try this first.
If it still happens, uninstall and reinstall AmazHA. This clears any corrupted local data.
I have exactly the same issue. it keeps crashing out when ever i try to tap an area. if i reboot watch it works for little while then it just goes back. i only want it mainly to be able to unlock front door when i arrive home, so i only have 2 things enabled.
Thanks for reporting this. The good news is I’ve been working specifically on fixing crashes like this in the most recent updates, so it’s very much on my radar.
To help you properly, could you send a report through the in-app support form? Open the AmazHA settings in the Zepp app on your phone and use the “Support” option there. It automatically attaches diagnostic info (app version, watch model, which entities are enabled, connection status, etc.) that shows me exactly what’s happening when the area screen crashes. That tells me far more than I can guess from the outside.
A couple of quick things in the meantime:
Make sure you’re on the latest version (check it at the top of the AmazHA settings, next to the logo), since recent builds include stability fixes aimed at this exact behaviour.
Since you only have 2 entities enabled, it’d help to know which types they are (e.g. the lock and one other): if the crash is tied to a specific entity type on the area screen, that narrows it down a lot.
Send the in-app report and I’ll dig into it. We’ll get your front-door unlock working reliably.
Because the version currently in approval is 0.11.48, which sadly doesn't include these fixes yet. They'll land in the next release (0.11.6X), which I already have ready to go on my side.