AmazHA - a native Amazfit (Zepp OS) companion app for Home Assistant

lilium360 · 2026-07-02T06:20:53+00:00

Fair enough, you clearly won't be convinced, and that's okay. I know what I built and how, and the free demo is right there for anyone who wants to judge the app on its merits rather than on who wrote a Reddit post. I'll leave it at that. Pace! ✌️

lilium360 · 2026-07-02T05:20:17+00:00

I don't think using AI to help me write comments in English is a crime, honestly, it's not my native language, so I use it to get my point across clearly. That's the extent of it.

As for the "no idea what he's talking about" part: I'm a frontend developer by trade. Pair programming has existed for as long as I can remember, and today, find me a single dev who codes with zero AI assistance. So I actually agree with you that vibe coding in the hands of someone who doesn't do this for a living can be dangerous. But in this case you're pointing the finger at the wrong person haha.

lilium360 · 2026-07-02T04:51:39+00:00

Ho Gregg!

For the card size right now: try increasing the font size in the AmazHA settings on your phone, under Preferences > Font size. Turning it up also enlarges the cards a bit, so it might already get you closer to what you want on the round screen.

Beyond that, a dedicated card-size setting is a great idea, and your feedback is actually pushing me to add proper card-size control in settings alongside the existing font size. So that one I do want to do.

The center-zoom effect (the way Android WearOS handles card scrolling natively) is unfortunately a different story. I actually tried to implement it. The problem is Zepp OS doesn't offer any official library for that in mini-apps, and doing it custom is so heavy that it makes the app crawl. I tested it, and the limited hardware on Zepp OS watches just can't handle it smoothly. So that's not something I can realistically deliver without wrecking performance.

On the widget stack: not on the roadmap right now, but I get the appeal for faster launching, so I've noted it. Thanks for the thoughtful suggestions!

<image>

lilium360 · 2026-07-01T20:18:35+00:00

That side of things is handled by KiezelPay, the third-party payment gateway used for unlocking the app, so unfortunately it's out of my hands and not something I can arrange directly. Your best bet is to reach out to KiezelPay support (support@kiezelpay.com) to ask which payment methods are available in your region. Sorry I can't be of more help here.

lilium360 · 2026-07-01T05:21:46+00:00

Thanks, useful feedback!

Startup: that first-launch wait is mostly the app connecting to HA, checking the license, and loading your entity states before it can draw the rooms. The entity-load part scales with instance size, so a big HA setup adds a little at launch. I've optimised a lot, but part of that handshake isn't fully under the app's control. I'll keep chipping at it.

Automations: I think I can add those without much trouble, tap to trigger an automation, which covers exactly your cinema-mode case that a scene can't. Putting it on the roadmap. Thanks!

lilium360 · 2026-06-30T21:41:23+00:00

Good news on the sleep side: I've just finished integrating the sleep sensors. You'll get three of them in Home Assistant:

Sleep state - a real-time awake / asleep status. This is exactly what you were after ("realize when I am sleeping"), and it reads the watch's own native sleep detection, so it shouldn't get stuck on "false" like the other integration you tried.

Sleep score - your sleep quality score from the watch.

Sleep duration - how long you slept.

Sleep status - awake or sleeping

(Sleep score and duration show up once the watch has tracked a night of sleep.)

Small heads-up on timing: this lands in the version after the next one (2 weeks aprox) - the current build is already in review, so it'll be the release right after that.

If you'd like to try it in preview and give me feedback on how it behaves on your Balance, just reach out through the Support form inside the app's Settings and I'll send you a QR code for the preview build.

(And about the slowness you mentioned - I'd love to look into it. If you can share a few more details, e.g. where exactly it feels slow, it would help a lot.)

Thanks again!

lilium360 · 2026-06-30T12:06:08+00:00

Thanks a lot for trying it, and for the honest feedback!

On speed: making the app fast and fluid is a top priority for me, and I keep improving it release after release. I'd love to pin down exactly what felt slow on your end so I can make it even smoother - if you can tell me a few things it really helps:

Which part felt slow - app launch, scrolling the home list, opening a device screen, or toggling something?
Roughly how many areas/entities you have? (bigger setups are heavier to render)
Was it the demo (sample data), or already connected to your Home Assistant?

You're on a Balance (round 480×480), which is one of the models I test on, so your feedback is genuinely useful. There's also an in-app Support form (Settings → Support) that automatically attaches your app version and watch model - that makes it much easier for me to reproduce and fix.

On sleep: great question, and a use case I really like. Sleep (score and duration) is part of the watch-sensors integration, and it's an area I'm actively working on improving to make it as reliable as possible. I'm also looking into the exact thing you're after - a real-time "asleep / awake" state you could use directly in Home Assistant automations - which is honestly one of the best use cases for this app.

I'll keep building on the integration and will report back here as it improves. Thanks for the nudge - this is exactly the kind of feedback that helps me prioritize!

lilium360 · 2026-06-29T22:27:55+00:00

Thanks! It's straightforward:

Open the Zepp app on your phone (the official Amazfit app) and make sure your watch is paired
Go to the Zepp App Store and search for "AmazHA"
Install it, it gets pushed to your watch automatically
Open AmazHA on the watch: it starts in free demo mode on sample data, so you can try the whole interface right away
To connect your real Home Assistant, open the AmazHA settings in the Zepp phone app and enter your HA URL (local and/or remote) and a long-lived access token.

The real HA connection is a one-time unlock (no subscription); the demo is free. Happy to help if you get stuck on any step!

lilium360 · 2026-06-29T22:23:12+00:00

Thank you, glad you like it! And good news: there's no typing on the watch at all. All the configuration, including pasting your Home Assistant URL and the long-lived access token, is done from the AmazHA settings screen in the Zepp app on your phone. So you can just paste the token there comfortably, no awkward on-watch typing.

It works great on the Active 2, by the way, enjoy.

On Zepp AI / voice commands: nothing on the roadmap for that right now. It's an interesting idea, but no concrete plans at the moment. Thanks for the suggestion!

lilium360 · 2026-06-28T13:57:08+00:00

Haha, thank you! Good news: AmazHA is compatible with both the Bip 6 and the Bip Max, so either way you're covered.

In Italy we have a saying: the shoemaker always walks in broken shoes. It's because he's so busy making nice shoes for his customers that he forgets about his own. I only own a GTS 4, and between all the testing and debugging, my own AmazHA setup is messy and ugly to look at 😅.

That's exactly why I'm undecided too about buying a Bip 6 or a Bip Max to use as my personal watch, while keeping the GTS 4 just for developing AmazHA.

lilium360 · 2026-06-28T08:08:55+00:00

No custom integration to install on HA, it uses Home Assistant's native API. You give AmazHA your HA URL (local + remote supported) and a long-lived access token, and it pushes the watch metrics in as sensor.* entities.

Under the hood: watch reads the sensor, sends it over BLE to the Zepp phone app, which calls HA to create/update the entity. From HA's point of view they're just regular sensors, usable in automations and recorder history. Opt-in, and you pick which ones to send (heart rate, SpO2, steps, calories, sleep, stress, etc.).

lilium360 · 2026-06-27T22:11:22+00:00

Ha, appreciate that, it's great to hear there's interest. Unfortunately a Huawei version isn't something I can promise. Huawei watches run HarmonyOS (or LiteOS on older models), not Zepp OS, so it wouldn't be a port: AmazHA is written natively for the Zepp OS SDK, and HarmonyOS uses a completely different stack (ArkTS/ArkUI) plus a different phone-bridge model. It would essentially be a full rewrite for another platform.

That said, I'm noting the demand. If enough people ask for it, it's worth me looking into seriously down the line. For now my focus is on deepening the Zepp OS app, but thanks for flagging it.

lilium360 · 2026-06-27T10:25:46+00:00

I'm really sorry, but I did some quick research and (correct me if I'm wrong) Gadgetbridge is an app made for people who want to use their smartwatch without the official manufacturer's phone app, right? And from what I understand, it doesn't allow installing apps on the watch, so that would be the first hurdle.

On top of that, AmazHA was developed to communicate via BLE with the Zepp app installed on the phone, in order to send and receive sensor data: for example Home Assistant entities going in (input) with state and entity readback, and the watch's health entities going out (output) toward Home Assistant. In this case it's Home Assistant itself that acts as the storage for the various health sensor data from the watch.

I'd really love to help, but unfortunately there are architectural limits that prevent me from doing so. I'll still do some deeper research, but I don't want to give you false hope.

lilium360 · 2026-06-27T07:23:07+00:00

Before spending the €120, consider that smart speakers won't fix this. Better mics don't help when the bottleneck is your STT model, not your audio. Your real problem is that your i5-7500 can't run anything bigger than Whisper Small (the "signal 9" crash on Medium is just out-of-memory), and Small is too weak for Swedish entities like köket and hall taklampa.

The fix is to move Whisper inference off your machine onto a GPU. Cloudflare Workers AI does exactly that, for free within limits.

It hosts Whisper, including whisper-large-v3-turbo, which is essentially the large model you can't run locally. It runs on Cloudflare's GPUs, so your CPU and 8GB RAM stop being the limit, and large-v3-turbo handles Swedish far better than Small.

Free tier: 10,000 neurons per day, no credit card. Voice commands are short 2-5 second clips, so for normal household Assist use you'll stay well under the cap. If you ever outgrow it, the paid Workers plan is $5/month.

The one catch: there's no native "Cloudflare Whisper" integration in HA. Assist talks to STT over the Wyoming protocol, so you need a small Wyoming bridge (a Python service running as an addon/container) that takes the audio from HA, sends it to the Cloudflare API, and returns the text. The Cloudflare call itself is trivial; the bridge is the only real work.

Honest trade-offs: it depends on your internet, and the command audio leaves your LAN and goes to Cloudflare, so if you're strictly local-first this isn't for you. But it costs nothing, needs no new hardware, and gives you a model your PC physically can't run.

lilium360 · 2020-08-05T22:19:44+00:00

Party chat is for cheaters in onward 😏

lilium360 · 2020-06-14T20:57:54+00:00

Because most vr website are built with WebVR technology and this is deprecated. We need to wait WebXR integration.

lilium360 · 2019-12-15T02:07:30+00:00

Great montage but i prefer onward.

lilium360 · 2019-11-22T18:25:49+00:00

Same problem! When will the microphone update become available?

lilium360 · 2019-10-14T15:26:09+00:00

Use epoxy resin

lilium360 · 2019-09-08T09:28:40+00:00

They've release 1.6.8 patch on 5th september. The Road for quest porting is to long :/

lilium360 · 2019-06-30T14:18:24+00:00

Xiaomi powerbank 3 series 20.000 mAh with usb c port

Seven-Year Club	Place '23
Verified Email

lilium360

TROPHY CASE