myteslamate

[brianmay]

For a while switched to myteslamate proxy, because using a newer fleet API proxy seemed to be better.

But suddenly realized I was not getting charge updates anymore. As in the battery % was updated 2 days ago. And car has been driven multiple times since. And having no updates combined with my personal software meant the car started charging at peak power periods. Which is not good.

Drive detection worked for all these drives, and drive tracking mostly works. Just the battery didn't appear to update a all. Weird. And I suspect this meant that teslamate was not getting updates to charging/not charging.

I had a quick scan through teslamate logs, and couldn't see anything obvious wrong. It was very verbose with errors when the car was asleep (not sure if that is normal here with myteslamate), but when car was awake during drives everything looked fine.

• Except, there was one trip where the location made some premature random jumps back to home which was a bit weird.

Anyway, for now I have changed back to the owners-api. Initially it didn't work, because I forgot to update teslamate. Duh. But hopefully I should have a working system again.

Maybe one day will try again. Maybe I did something wrong (I doubt it somehow) but for now just wanted to document my experiences.

Typing this quickly, so apologies if something I said here doesn't make sense :-)

[zexpe]

Somebody was saying in a discussion here that the Fleet API fails to update whilst the car is parked - maybe that's why it's missing charges?

[JakobLichterfeld]

Prhabs @jlestel is the best contact for MyTeslaMate concerns. I personally assume you must disable streaming api in settings when using MyTeslaMate

[jlestel]

Thanks @brianmay for the detailed testing. The logs you posted are from Jun 21–24, and a few separate things were going on (most are already fixed since):

• Stale stream data: a queue wasn't being drained correctly, so buffered samples replayed out of order and TeslaMate dropped them as stale. Fixed Jun 26, so the symptoms in your logs predate the fix and should be gone now. If you still see time: jumping backwards, ping me.
• Sleep detection / the 408s on vehicle_data: you were right that the proxy was interfering here. Previously it tried to infer the awake/asleep state on its own; it now queries the vehicle's real state instead, so it no longer trips the fuse or pushes TeslaMate into calling get_with_state on a sleeping car.
• Sparse vehicle_data: even though you were subscribed to both plans, your telemetry config was at the free-tier level (9 fields). It's now on the full 48-field set, so the data will be considerably richer. On that note, I'm considering offering a free API/telemetry tier with this minimal config — the idea being a low-cost fallback to switch to if the Owner API ever goes away.

On streaming: with the dequeue bug fixed, I'd recommend keeping it on. MyTeslamate uses the stream to enrich vehicle_data, so disabling it actually gives you less complete data. @JakobLichterfeld: that's the reverse of the usual assumption, but it's specific to how the proxy merges stream + polling here.

On the token in the URL: agreed, it shouldn't be a query param. I'm preparing a PR to move it to an Authorization header.

Happy to dig further if anything resurfaces post-fix.

[brianmay]

Oh, I stuffed up. I thought the token logging issue was teslamate, but of course, that was after I used myteslamate. So it is debatable who is at fault here :-)

I changed back to owners-api on the 27th because the battery state in teslamate was two days old. And I had other issues that are perhaps connected, e.g. after completion of drive car would be shown just outside property, not inside property where it stopped. Which is why my software had problems, it believed the car wasn't at home, and didn't setup charging correctly for at home.

As this was the 27th, not convinced that all problems were resolved :-( - but looks like in trying to diagnose this I got confused by outdated issues.

I probably should try again sometime, time pending.

Random thought: Would be really good if I could get some sort of proxy feed of the raw stream (not the legacy streaming API) from Tesla. Is this possible? This would help debug if issues I faced are Tesla, myteslamate, or teslamate.

[jlestel]

No worries, easy to mix things up.

Worth giving it another spin: since yesterday you're getting all 49 fields instead of the previous 9.

And great idea on the raw stream, it'll be useful, ty.

[jlestel]

Quick follow-up: you can now see the raw Telemetry events as they arrive in your dashboard. The exact telemetry samples streaming in from the vehicle, in order, with their timestamps and fields.