Ignore cap on Tesla API calls and overworking the charge controller switch on startup

I plugged my Tesla in today to start charging from excess solar (yay spring!) and opened my trusty Charge HQ app to confirm but was met with a message stating that API messages are capped for Tesla. I completely get this and understand why but from a UX perspective it would be great to ignore the cap for the first few minutes while things establish themselves at the start of a new charging session. Once the Tesla API was sent I was then met with a message that to prolong the life of your wall charger we are delaying the instruction for 13 mins! Again I understand why but its a bad UX to have to override this to get things going. Again, can you ignore this logic in the first few mins while charging is established. Thanks for your great product!

@magennis.weate thanks for your post.

What you experienced is actually an uncommon race-condition bug. After you plugged in, Charge HQ had an out-of-date solar data feed and incorrectly determined that there was not enough solar to charge, so it stopped the charging immediately. This is something we’ll investigate further.

The status message regarding “conserving Tesla API quota” is erroneous and misleading - we’ll fix it.