Mike Bishop

(I edited the above; don't update your config based on the e-mail notification without seeing the edits.)

Ideally, if the car could sink arbitrary amounts of current, we want to charge with anything over the export limit. The fictitious consumption addresses that, basically by considering your export...

Latching is about when the conditions for the policy are no longer met; it doesn't have any impact on when a policy is active, but deciding not to offer current....

The point was to avoid a 1m stall on the background thread by using the error backoff mechanism that already existed. If the backoff is too aggressive for those errors,...

Yeah, MMM-Powerwall's strategy with Teslamate MQTT is: - Figure out how to match API vehicles with MQTT vehicles; it'd be easy if Teslamate surfaced the VIN or ID, but they...

Can you try the [`location_frequency`](https://github.com/ngardiner/TWCManager/tree/location_frequency) branch and see if that helps? It looks like it pings the car's location with a cache time of 1 minute, and checking the location...

Unfortunately, that's a bit of a chicken and egg problem. From the TWC's perspective, there's no difference between not being plugged in and being plugged into a sleeping car. We...

If you look in settings.json, is the home latitude/longitude set correctly? The existing logic is to assign the coordinates reported by the first car that appears **in the API** to...

It's worth noting that TWCManager has no API access to the location your car believes is home -- it only has access to the car's present GPS coordinates. So it...

Hm. The fact that you had to do it twice, though, suggests that TWCManager is forgetting and snapping to a new (wrong) location.