Spyke

Teslemetry using excessive number of "wake up" calls

I am using the teslemetry integration to dynamically adjust my charging amps to match the surplus production from my solar panels. I have an automation that checks surplus production every 2min and adjust amps only if needed.

But teslemetry seems to trigger the wake up command every single time I want to send a command to my car, regardless of the cars sleep state. This means that teslemetry is burning through my command credits in an absurdly short amount of time as every wake command costs a ridiculously 20 credits.

How can I stop teslemetry from triggering these expensive and utterly unnecessary wake up commands?

View original on lemmy.dbzer0.com

I don't have a Tesla and am just starting to dip my toes into home automation. That said, there's an article on Teslemetry that discusses the cost of these actions and is trying to reduce them to only when necessary. Here's a link. I'm not sure if the HA integration is using the queue they talk about or if it's something that needs to be set by you, but hopefully this gives you a useful starting point. If nothing else, there's a Discord link that may prove useful.

2
ExcessShivreply
lemmy.dbzer0.com

Yes well, unfortunately I can't just waste that kind of money so that's not really an option. FWIW, I bought it more than 4 years ago before he went full apeshit in public.

4
Kuinoxreply
lemmy.world

I bought it more than 4 years ago before he went full apeshit in public

No no, in 2021 he had already :

  • sabotaged high speed rail in america.
  • endorsed Kanye West presidential campaign
  • defied COVID-19 lockdowns
  • fought against mandatory vaccines
  • called a diver that was rescuing children a "pedo".
    whelp i'm too lazy to list more
6

You reached the end

Teslemetry using excessive number of "wake up" calls | Spyke