TWCManager: Unable to STOP charge!?
Hi,
Do I read the log correctly that the script is trying to send a “STOP CHARGE” to the car (last 5 lines)?
09:30:33 Policy 8 Evaluating Policy match (tm_hour), condition (gte), value (6)
09:30:33 Policy 8 Evaluating Policy match (tm_hour), condition (lt), value (20)
09:30:33 Policy 8 Evaluating Policy match (settings.hourResumeTrackGreenEnergy), condition (lte), value (tm_hour)
09:30:33 Policy 7 All policy conditions have matched. Policy chosen is Track Green Energy
09:30:33 TeslaAPI 8 Entering car_api_available - next step is to query Tesla API
09:30:33 TeslaAPI 8 car_api_available returning True
09:30:33 TWCManager 1 Green energy generates 0W, Consumption 0W, Charger Load 1211W
09:30:33 TWCManager 1 Limiting charging to 0.00A - 0.00A = 0.00A.
09:30:33 TWCManager 1 Charge when above 6A (minAmpsPerTWC).
09:30:43 TeslaAPI 8 Entering car_api_available - next step is to query Tesla API
09:30:43 TeslaAPI 8 car_api_available returning True
09:30:43 TeslaAPI 8 startOrStop is set to stop
09:30:44 TeslaAPI 8 Car API cmd<Response [200]>
09:30:44 TeslaAPI 4 CARNAME: stop charge response{'response': {'result': True, 'reason': ''}}
It doesn’t seem to work as the car is charging and not stopping at all!? Is this a bug on my CAR or something? Because my Powerwall is below 90% and should use the solar energy only to charge it till it’s 90% and then deliver energy for the car.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (6 by maintainers)
Reasonable suggestion. Anything lower than the current charge should suffice, so another option would just be to always set it to 50%. Updated, if you do a
git pull.That assumes we know which car is connected. But we could use the minimum charge at home more generally, or simply set it to the minimum. Regardless, the car would declare itself done. I’d have to go through the logic to make sure the fallback doesn’t get overwritten on the next cycle or stored as the new outside value, though.