Mine came up with 66 entities, if i knew how to export the list for HA I would share. Pretty much everything you can think of but if you’re chasing anything specific please ask
Thanks Geoff,
66 entities sounds nice. Are the Charging Power included ? (for real-time monitoring of the power) - I´m using solar panels for charging so the power goes up and down 
It is missing a LOT of sensors from the other integration by japyjaap/R3ffoTz, and I got tired of waiting for this to be added so I vibe coded all of the crucial ones, such as travel plan, charging ETA, vehicle/engine state, while “fixing” some of the issues that I didn’t like, such as converting the tire pressure unit to bar instead of kPa for easier readability.
Sorry, I have been slack on reviewing these big PRs.
I’ll get back onto it.
Yes, we get charging power (and current, speed and voltage)
Mind sharing a manual of how to?
Im also an iphone user
Are we aware of any # of API calls allowed per day ?
Has anyone created or found a list of what all the charger codes mean? My best guesses so far are:
0 = unplugged
2 = scheduled charging
4 = Stopped at % limit
25 = scheduled NOT charging
6 = manual charging (no schedule)
No, but the official app really spams it so I’m assuming if there is one it’s very high
1 Like
Awesome, I´ll adjust the polling interval to 1 minute then.
Hi all, great work on this integration — exactly what I’ve been waiting for with my Zeekr 7X!
Unfortunately I’m an iPhone user so decompiling the APK isn’t straightforward for me. I understand the secret keys (HMAC access/secret, password public key, prod secret, VIN key/IV) are baked into the app binary rather than being per-account — is that correct?
If so, would anyone who has already extracted them be willing to share? It would open this up to a lot more people in the same boat. Happy to help test and report back on my setup (7X, Australian market, Home Assistant with existing EV charging automations).
Also @atishyak — any progress on that extraction guide you mentioned back in January? Even rough notes would be hugely appreciated!
Thanks for your help, @Fryyyyy and @Whysee. I received the keys, but I don’t have a password to log in to my Zeekr account. I log in using my phone number. Is it possible to set up integration using my phone number?
Can one skip the Emulator step and download the APK Directly from an APK mirror?
Nevermind. Check and check
Next step is to get the SOC pushed to Tibber.
Can confirm it works on the Zeekr 001
Everyone’s keys are different, it’s specific to your car and account.
Download mumuplayer android emulator and use that to extract the keys, it’s what I did. Set up a new account and share to it so you use those keys, else it will kick you oout of your app account any time it does something.
No the keys are the same for everyone.
At the moment we don’t support this but we welcome pull requests
Hi,
I’m trying to use the extracted keys with the Zeekr EV API but getting a signature authentication failure at the bearer login step.
Setup:
- App: com.zeekr.overseas (EU version)
- App version: 3.0.0
- Extraction region: --region EU
- Country code used: SE (Sweden)
- zeekr-ev-api version: latest from GitHub
Error:
Bearer login failed: {‘code’: ‘079025’, ‘msg’: ‘Signature authentication failed.’,
‘data’: None, ‘debug’: {‘bizName’: ‘API Gateway’}}
Note: The first login step (_do_login_request) succeeds, but _bearer_login fails
with the signature error. When using country_code=‘AU’ with EM keys, the first
login step fails with code 9300 instead.
Also worth noting: When querying the EU API gateway directly for URL data,
it returns: {“msg”: “Invalid access key”, “code”: “0001”}
This suggests the HMAC keys extracted with --region EU may not be correct
for the EU API gateway.
Has anyone successfully authenticated with a Swedish/EU account using
com.zeekr.overseas v3.0.0? Any help would be appreciated!
Ah my bad then.
You can try logging an issue on the key extractor Github