there is now 9 sets free so go in quick as i will not go for the paid version as this is way to expensive
Wouldnt it be possible to adress a second different (free) enode account?
Unfortunately I cannot register yet although I have an Xpeng Account as my xpeng g9 will only be delivered in November…
Mulig å øke hvor ofte den oppdaterer bilens posisjon?
Ønsker den skal trigge garasjen til å åpne seg når den nærmer seg., men 10m er ganske mye for det.
Thanks for building and maintaining this app — really appreciate having XPENG integration in Homey at all.
I’m new to the app, so take this as a fresh-eyes observation rather than a complaint: I noticed pluggedInStatus/chargingStatus can lag real events by hours (mine sat frozen ~2 hours despite a 10-min poll interval and me actively using the official XPENG app in that window, including opening the charge port) — while range, location, and battery on the same device kept updating normally in that same period (minutes-old, not hours). So it looks like a per-field issue upstream (Enode/XPENG API) rather than the whole feed being stuck — matches what others reported here too, and your reply that it’s not fixable app-side makes sense given that.
One workaround for anyone hitting the same thing: if you also have a smart charger reporting a cable-connected/charging status of its own, or you’re OK using GPS proximity-to-home as a signal, either is a much faster/more reliable “car is home and plugged in” indicator than waiting on this app’s pluggedInStatus alone. That’s what I ended up using as a fallback for my own automations.
Thanks again for the work on this!
@Kjetil_Vert Is chargingLimit read-only because Enode’s API doesn’t support setting it, or is the write listener just not implemented yet — any chance of adding SET support (e.g. via a flow action)?
My friend has Xpeng G9 and he’s getting this “Problem generating link: Something went wrong. Please try again later. If the problem persists. Please check your vehicle status or restart the app.” error when trying to add it as a device? Can you fix it?
6ed41fd2-3e71-4eaa-ac5e-779deb7e771c
