[APP][Pro][TEST] Zeekr APP - Credits OpenZeekr 0.2.5

control & read out your Zeekr from Homey Flows

A quick note up front

I built this as a proof of concept. I want to be upfront: I have no experience with coding or maintaining apps whatsoever — I put this together with AI assistance, step by step. It works on my own car.

So I’m mainly sharing it as inspiration: I really hope it shows what’s possible and motivates someone with real development experience to build a proper, maintained Zeekr app for Homey. If that’s you, please feel free to take any of this and run with it.

What I set out to do

The original idea that kicked this off:

“I want to turn an existing Android app — OpenZeekr, which gives full control over your Zeekr by logging in with your email — into a Homey app. My goal is to preheat my car and read it out through Homey flows.”

So: not a rewrite of the Android app, but a Homey app that talks to the same Zeekr cloud, so preheating and status read-out can run from Homey Flows.

What it does

A Zeekr car device with:

  • Battery %, range, charging state + charging power (kW)
  • Locked/unlocked, doors/trunk/windows open, interior & exterior temperature, odometer
  • Automatic status polling (interval configurable, default 5 min)

Flow actions: start climate (preheat/cool with target temp + duration), defrost, seat heating/ventilation per seat, steering-wheel heating, start/stop charging, set charge limit, battery preconditioning, windows, tailgate, lights/horn, sentry mode, and “refresh status now”.
Flow triggers: charging started/stopped, cable connected/disconnected, climate on/off, range changed, status updated (battery/range/location), command failed.
Flow conditions: is charging, cable connected, climate on, battery above/below X %, range above/below X km.

Example flow: every weekday at 07:00, if the outside temperature is below 3 °C → start climate at 21 °C for 15 minutes.

How it works (and why it behaves)

  • The cloud layer is ported from OpenZeekr (MIT) — the reverse-engineered account login, request signing, status read-out and remote-control command catalog — rewritten in JavaScript for the Homey Apps SDK (v3). The Bluetooth digital key of OpenZeekr is deliberately left out; it only works right next to the car and isn’t needed for cloud control.
  • The two signing schemes (user-center login HMAC and the TSP gateway X-SIGNATURE) were cross-checked byte-for-byte against the reference zeekr_ev_api implementation, so the requests are identical to what the stock app sends.
  • There are automated tests covering signing, VIN/password crypto, status parsing and the login flow, and the app validates at Homey’s strictest publish level.
  • It talks to the EU Zeekr/Geely TSP cloud (other regions are present but unverified).

Requirements & important caveats

  • Homey Pro (2023); install via the Homey CLI (it’s not in the App Store — see below).
  • You supply your own app keys. No Zeekr secrets are shipped (same principle as OpenZeekr). You extract the six keys from the official OpenZeekr release APK with a small included tool — no root or Frida needed.
  • One active session per account. The Zeekr cloud allows only one login at a time: logging in from Homey logs you out of the official Zeekr app, and vice-versa. Recommended: create a second Zeekr account, share your car to it from your main account, and use that second account in Homey — then the official app on your phone stays logged in.
  • It’s a reverse-engineered, unofficial integration. Zeekr can change the API without notice, which would break it until someone patches it. No warranty, use at your own risk.

Install (short)

Get the code: GitHub - bullseye1977/Zeekr-Homey · GitHub (git clone, or Code → Download ZIP and unzip).
Get the APK: Release OpenZeekr 0.2.6 · borconi/openzeekr · GitHub

  1. Install Node.js 18+ and the Homey CLI (npm install -g homey), then homey login.
  2. In the app folder: homey app install (installs straight onto your Homey — no Docker needed).
  3. Extract your keys from your OpenZeekr APK:
    node tools/extract-keys.js openzeekr-x.y.z.apk zeekr-keys.json
  4. Homey app → Apps → Zeekr → Configure: enter email, password, region (EU) and paste the keys JSON → Save → Test login (should list your car).
  5. Devices → + → Zeekr → add your car.

Status

Logged in and verified on a real Homey Pro 2023 with a Zeekr 7X (EU): login works, the car is detected, status reads out, and commands (preheat/charging/etc.) run from flows. It’s a proof of concept — rough edges are expected.

Credits & license

Built entirely on the reverse-engineering work of OpenZeekr by borconi and the projects credited there. No Zeekr secrets are included — you provide your own from your own app install. MIT licensed.


[grid]






[/grid]

Android only i guess. Extract keys is android only

allready using the openZeekr app which works realy great. As a new Homey user (pro 2026) have to figure out how to install it.

Yes currently only android

I wish we could get this for IOS :slight_smile: are those key’s not the same on IOS? I think claude told me those keys should be the same so we had to ask a android user :smiley:

I just configured this, and it works great!
Not sure what you mean about “android only”, however you don’t need an android device to configure this on Homey.

Great! You only need the OpenZeekr.APK for extracting the keys. You do not need to install the APK first on your phone. The keys are stored in the APK i hope this make sense.

See post above

Ok nice but you need en separate account en if you already share it with for example your partner you cant share it with another account. Need to check how we can solve this. Anybody else able to share with more then 1 account?



Added distance as well