Fryyyyy / Fryyyyy/zeekr_ev_api
Charging action intermittently stops responding until phone app usage
- Dominant language
- Python
- Stars
- 37
- Forks
- 11
- Avg merge
- 20h 49m
- Merged PRs (30d)
- 1
Description
I've built an automation to start/stop charging at optimal times. However I've found that the command to 'turn_on" the switch for charging is only intermittently working (turn_off looks fine from what I've observed). It appears that when I've recently used the Zeekr app on my phone, this works reliably, however if I've not used it for a few hours then the HA automation does not work. As an example the automation fired maybe 20 times in the night to turn on the EV charging, however none of them resulted in the switch actually turning on.
It almost seems like the vehicle goes into deep sleep and only wakes from the mobile app.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the charging switch turn_on failure after the vehicle has been idle, comparing it with behavior immediately after using the Zeekr phone app. Trace the charging command entry point and determine how the vehicle is awakened or contacted; done means automated turn_on commands reliably work after several hours without app usage, with relevant regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100