You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the car has reached it's target state of charge and stopped charging as a result, then the "start charging" button in the app is inactive.
Over time vampire drain will reduce the state of charge - left long enough (so it has lost 3 or 4%) the car will top itself up to the target state of charge.
If, while the car is in this state (button in app inactive), I send a start charging command, the car won't start charging, but wakes up (accelerating the vampire drain).
If I move the target state of charge slider in the app, then move it back - the "start charging" button in the app is reactivated and I can start charging successfully. However I suspect the cars default behaviour is to minimise wear on the battery so I don't really want to make the car charge when it wouldn't to protect the battery.
What I'm hoping to find is the indication in get_vehicle_data() that in effect tells me if the button in the app is active or inactive (so I can avoid sending a start charging command if the button is inactive).
Does anyone already know what this data is? I wondered if it might be "charge_enable_request", "managed_charging_active" or "user_charge_enable_request" (or something I've missed)? Trying to get the car into the right state to test again has been tricky so I'm hoping someone may know.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If the car has reached it's target state of charge and stopped charging as a result, then the "start charging" button in the app is inactive.
Over time vampire drain will reduce the state of charge - left long enough (so it has lost 3 or 4%) the car will top itself up to the target state of charge.
If, while the car is in this state (button in app inactive), I send a start charging command, the car won't start charging, but wakes up (accelerating the vampire drain).
If I move the target state of charge slider in the app, then move it back - the "start charging" button in the app is reactivated and I can start charging successfully. However I suspect the cars default behaviour is to minimise wear on the battery so I don't really want to make the car charge when it wouldn't to protect the battery.
What I'm hoping to find is the indication in get_vehicle_data() that in effect tells me if the button in the app is active or inactive (so I can avoid sending a start charging command if the button is inactive).
Does anyone already know what this data is? I wondered if it might be "charge_enable_request", "managed_charging_active" or "user_charge_enable_request" (or something I've missed)? Trying to get the car into the right state to test again has been tricky so I'm hoping someone may know.
Thanks in advance...
Beta Was this translation helpful? Give feedback.
All reactions