this post was submitted on 23 May 2025
16 points (90.0% liked)

homeassistant

14875 readers
4 users here now

Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @[email protected]

founded 2 years ago
MODERATORS
[email protected]
[email protected]
16
Teslemetry using excessive number of "wake up" calls (self.homeassistant)
submitted 3 weeks ago by ExcessShiv to c/[email protected]
4 comments fedilink hide all child comments
 

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?

all 5 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 3 weeks ago* (last edited 3 weeks ago)

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.