Seeing offline rather than sleep after updating to 2024.8.4 and Teslamate version 1.28.4

[dsgdesign]

Hello dev & user community. This teslamate open source project is a marvellous effort and I appreciate it very much. Been using it for 2 years. I can't figure out by myself what is going on and need some input. Hesitant at this time to move this as an issue.

Similar to the locked discussion started by bodosum. Started seeing vehicle offline rather than sleep after updating Tesla Model 3 SR+ to 2024.8.4. Was on Teslamate 1.28.3. Updated to the latest 1.28.4 hoping this would fix the issue. It does not.

[cwanja]

Let’s comment on #3658 to consolidate conversations.

Start with a response to here - were you on TeslaMate 1.28.3 when you updated? And then immediately saw offline? Or were you on 1.28.4?

Based upon your post, it seems that the offline state started in a Tesla update and not TeslaMate.

[dsgdesign]

Yes I was on Teslamate 1.28.3 when I updated.

[durzel]

I was also on 1.28.3 when I updated, and started seeing offline. I updated TeslaMate to 1.28.4 just speculatively to see if there was an update that might fix it, with no change in behaviour. For me this definitely happened as soon as the car was updated.

[micves]

Based upon your post, it seems that the offline state started in a Tesla update and not TeslaMate.

Thats also how I read the post. The states offline and asleep is coming directly from the response from tesla servers/api.

Did you try to reset the car after the update? (Press and hold the jog buttons on the wheel)

I think the issue is a little different than #3658, so it might be okay to keep it here and shut down #3658 instead

[dsgdesign]

So my issue started on Teslamate 1.28.3 after the car was updated to 2024.8.4. Since this morning I am running the latest Teslamate 1.28.4 hoping that would resolve this new behaviour. I just did a ride in the vehicle and I have observed upon my return that the drives were correctly reported in Teslamate. I did the reset on the steering wheel as suggested but still saw the car going offline rather than sleep. Repeated the reset just in case. Here is the tail of the teslamate log after the last drive:

teslamate-1 | 2024-03-20 14:04:47.513 car_id=1 [info] Driving / Ended / 0 km – 0 min
teslamate-1 | 2024-03-20 14:04:47.514 car_id=1 [info] Start / :online
teslamate-1 | 2024-03-20 14:04:57.937 [warning] Too many disconnects from streaming API
teslamate-1 | 2024-03-20 14:04:57.937 car_id=1 [info] Creating new connection …
teslamate-1 | 2024-03-20 14:04:57.937 car_id=1 [info] Disconnecting ...
teslamate-1 | 2024-03-20 14:04:57.965 car_id=1 [info] Connecting ...
teslamate-1 | 2024-03-20 14:05:11.721 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/XXXXXXXXXX/vehicle_data -> 408 (9163.525 ms)
teslamate-1 | 2024-03-20 14:05:11.721 [warning] TeslaApi.Error / %{"error" => "{"error": "timeout"}", "error_description" => "", "response" => nil}
teslamate-1 | 2024-03-20 14:05:11.722 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-03-20 14:05:40.875 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/XXXXXXXXXX/vehicle_data -> 408 (9150.597 ms)
teslamate-1 | 2024-03-20 14:05:40.876 [warning] TeslaApi.Error / %{"error" => "{"error": "timeout"}", "error_description" => "", "response" => nil}
teslamate-1 | 2024-03-20 14:05:40.876 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-03-20 14:10:07.803 car_id=1 [info] Suspending logging
teslamate-1 | 2024-03-20 14:18:37.129 [info] Streaming API: Vehicle offline
teslamate-1 | 2024-03-20 14:18:37.129 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
teslamate-1 | 2024-03-20 14:18:37.610 car_id=1 [info] Start / :offline
teslamate-1 | 2024-03-20 14:18:37.646 car_id=1 [info] Disconnecting ...
teslamate-1 | 2024-03-20 14:19:58.337 [info] GET /
teslamate-1 | 2024-03-20 14:19:58.347 [info] Sent 200 in 10ms
teslamate-1 | 2024-03-20 14:24:20.220 car_id=1 [info] Start / :online
teslamate-1 | 2024-03-20 14:24:20.316 car_id=1 [info] Connecting ...
teslamate-1 | 2024-03-20 14:24:59.821 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/XXXXXXXXXX/vehicle_data -> 408 (9168.062 ms)
teslamate-1 | 2024-03-20 14:24:59.823 [warning] TeslaApi.Error / %{"error" => "{"error": "timeout"}", "error_description" => "", "response" => nil}
teslamate-1 | 2024-03-20 14:24:59.825 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-03-20 14:29:33.146 car_id=1 [info] Suspending logging
teslamate-1 | 2024-03-20 14:32:40.574 [info] GET /
teslamate-1 | 2024-03-20 14:32:40.584 [info] Sent 200 in 9ms
teslamate-1 | 2024-03-20 14:37:21.080 [info] Streaming API: Vehicle offline
teslamate-1 | 2024-03-20 14:37:21.080 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
teslamate-1 | 2024-03-20 14:37:21.558 car_id=1 [info] Start / :offline
teslamate-1 | 2024-03-20 14:37:21.599 car_id=1 [info] Disconnecting ...

[cwanja]

Thanks for the detailed response and logs. To me, this looks like a Tesla change in behavior for the streaming API - either a bug or new feature. I assume we could change the application pattern to record offline as asleep, but those are two different states in my opinion.

Further more, I am on TeslaMate 1.28.4 / Tesla car version 2023.44.30.8 with zero offline patterns. Sleeping normally, which lends me to believe it is not a TeslaMate issue.

[dsgdesign]

Your hypothesis seems plausible considering your observations on 2023.44.30.8. I have a suspicion that this new behaviour I'm seeing was brought about by some changes in 2024.8.4. I will leave it up to the maintainers to see if this is a new issue that needs to be addressed. There are not many cars yet on this update according to Teslascope and Not a Tesla app websites. If others are experiencing this after updating to 2024.8.4 please chime in.

[micves]

I'm also thinking it's a change from Tesla. I have a Model S 2017 upgraded to MCU2 and have never seen asleep, only offline. So I'm not worried :)

It does look suspicious with the short wakeups on the graph in the end.
Can they be explained by you opening the app or going near the car og similar?

[rc-16]

I'm on Teslamate 1.28.3. Today I updated the car (model 3) to 2024.8.4. I have not driven it since the update. Before the update the car would report "asleep". Today it reports "offline". I haven't rebooted the car yet but I suspect its a Tesla change - nothing to do with Teslamate.

Hope this helps to confirm your theory. Relevant (hopefully) log entries follow:

2024-03-19 16:02:11.322 car_id=1 [info] Start / :online
2024-03-19 16:15:36.891 car_id=1 [info] Start / :asleep
2024-03-19 21:29:05.634 car_id=1 [info] Start / :online
2024-03-19 22:35:00.132 car_id=1 [info] Start / :asleep
2024-03-20 10:50:22.395 car_id=1 [info] Start / :online
2024-03-20 10:52:23.614 car_id=1 [info] Update / Start
2024-03-20 11:29:43.029 car_id=1 [info] Start / :online
2024-03-20 12:29:31.812 car_id=1 [info] Start / :offline
2024-03-20 13:22:20.747 car_id=1 [info] Start / :online
2024-03-20 13:34:55.917 car_id=1 [info] Start / :offline

[bodosom]

I noted this in "After updating to 2024.8.4 all sleeps are marked as off-line." #3751 and per cwanja appended a log file to #3658.

To me, this looks like a Tesla change in behavior for the streaming API - either a bug or new feature.

Although not conclusive TeslaFi shows these periods as asleep not off-line. This was also the case in #3658

[cwanja]

Does TeslaFi report anything as “offline”? Could be following my mention above that they treat “offline” as “asleep”.

Is anyone else running multiple services scraping the API?

[bodosom]

Does TeslaFi report anything as “offline”?

I don't know. That was the "not conclusive" bit. I do see that Tessie doe not make that distinction. Hard to know if the other clients are folding the two states into one or if Tesla has decided the distinction is irrelevant.

Does power-off take the car off-line?

[init6-git]

There appears to be an option to consider offline as asleep in Teslafi:

If 'Offline Asleep' is noted in the the raw data page under the note section this means that the offline session is being considered a sleep session. Some software versions report the vehicle as offline when idling instead of asleep so TeslaFi will consider the vehicle sleeping in this case. This settings can be adjusted in Sleep Modes->Advanced->Show Offline As Asleep.

from https://support.teslafi.com/knowledge-bases/2/articles/13486-the-raw-data-page-is-showing-my-vehicle-as-offline

[bodosom]

Does TeslaFi report anything as “offline”?

I'd forgotten that TeslaFi has a "raw" data viewer. Prior to 2024.8 TeslaFi reported awake/sleep. After the 2024.8 update it reports awake/offline with the "Show offline as asleep" option disabled.

[ktsenvolt]

I am having the same issue after the 2024.8.4 update. So the Teslamate version 1.28.4 update did not make a difference. Hopefully, the next version of Teslamate will fix it by changing the "offline as sleep".

[bodosom]

Offline and sleeping are two different states. Some clients (e.g. Tessie) might collapse them into "sleeping-or-offline" which is true but reporting offline as sleeping seems a bit wrong.

[bodosom]

Does TeslaFi report anything as “offline”? Could be following my mention above that they treat “offline” as “asleep”.

A retrospective look at TeslaFi data shows offline and sleeping as distinct states prior to 2024.8. In my case offline is rare but seems to reliably happen after a software update.

[cwanja]

Apologize for the question again, as there are several threads and scenarios here. On TeslaFi, after 2024.8.X - what is TeslaFi showing? Does it still show distinct offline and asleep states? Or are they just showing as offline?

[bodosom]

As of 2024.8.4 TeslaFi only shows offline (with the show offline as sleep toggle off). For what it's worth I've only seen four states on TeslaFi: asleep, online, offline and null (blank). E.g. they track updates but the update window is labeled "online".

[cwanja]

If I understand, TeslaFi is showing the same behavior as TeslaMate?

[bodosom]

If I understand, TeslaFi is showing the same behavior as TeslaMate?

With respect to online/offline/sleeping yes.

[cwanja]

Thank you again. Based upon this, I believe we do not make any changes to TeslaMate as it would potentially incorrectly capture “offline” states as sleep states. We wait it out and see if Tesla reverses course on future updates.

[durzel]

Have heard multiple reports that Tesla have paused or stopped the rollout of this version (2024.8.4). TeslaFi shows installs tailing off. Could be related to this issue?

[jheredianet]

Thank you again. Based upon this, I believe we do not make any changes to TeslaMate as it would potentially incorrectly capture “offline” states as sleep states. We wait it out and see if Tesla reverses course on future updates.

Good decision, I think this is something that everybody can live with it ;-)

[cwanja]

Edit 4/3 - based upon a follow-up response [additional 1, 2], it seems that there is a Tesla in-car software change impacting certain CPUs. We have identified that Atom based cars are not showing as "sleeping", but Ryzen cars are. Please continue to keep this thread updated.

Original post
Crafting this response as a "consolidated answer".

Due to the duplicate threads posted about this (#3658, #3755), our investigation reveals that Tesla made a change in 2024.8.X to start reflecting "sleep" patterns as "offline" via the API. Other third-party loggers have confirmed that. Current versions of TeslaMate are not impacted and thus is it not a TeslaMate issue.

Offline is different than sleep (historically) and we do not feel that logged offline as sleep is currently a valid step. We will wait to see if Tesla changes course in a future update. As @durzel mentioned, rollout of 2024.8.X has paused the rollout and this could be a reason.

Edit: thank you to everyone that contributed and provided data, input and comparison.

[durzel]

TeslaFi gives the option to treat "offline" as "asleep". No idea why or when this was decided upon, but perhaps it would be worth adding if this behaviour is permanent. As far as "we will wait to see if Tesla changes course in a future update", what sort of timeline do you think we're looking at here?

[cwanja]

@durzel sleep and offline are very different patterns (historically). I am hesitant to say this is the "new standard" especially since we are seeing other still reporting sleeping patterns.

[djpalmis]

I second that: it is really important for me to discern sleep and offline. Offline means "connection problems": it is very useful for me to understand if the router in my garage needs a reset.. or if somebody is stealing your car..
So: definitely it is better to wait new updates and see.. (finger crossed..)

[cwanja]

@djpalmis you regularly deal with people stealing your car? 🤣

[djpalmis]

Well.. I'm Italian.. so.. you never know.. 😄

[SirSheik]

Hello.
I don't know if my comment helps or will make things more complicated.
I currently have Teslamate version 1.28.0 and the latest version of Tesla 2024.8.7 and this problem that you comment does not occur to me.
I believe that the origin of the problem is more in some change with the version of Teslamate 1.28.5.
If you need more information or if you need me to do some test, let me know.
Thank you very much for your time and effort in this project.

[jheredianet]

Hi, just to report as @SirSheik, in order to make a test, I've reverted my setup and pulled version 1.28.0 of Teslamate, and it's true. The states work as expected:

So now, I'm not so sure that is a failure/change from Tesla API, it seems that it's about Teslamate.

[KILYBMW]

I have also done the test, and in version 1.28.0 the states work correctly.

[micves]

@SirSheik have you tried 1.28.5 ?

[durzel]

Does 1.28.0 correctly identify a genuine offline event though? (e.g. car parked underground with no LTE access)

[bodosom]

... I believe that the origin of the problem is more in some change with the version of Teslamate 1.28.5. If you need more information ...

This also happens in Teslamate 1.28.4. What Tesla release are you on? What does your log say? Something like:

car_id=1 [info] Start / :asleep
car_id=1 [info] Disconnecting ...

or something like:

car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
car_id=1 [info] Start / :offline

[KILYBMW]

In version 1.28.0, this does not happen.

[micves]

I must say. I'm pretty confused by these new reports.
When stream reports offline, is does a normal fetch of the status directly, so it would say offline regardless.
But maybe there is some timing issue. If you ask/poll for a status right after stream gets offline, it will be offline (1.28.5), but if you ignore stream and just ask at the given interval it will be asleep (1.28.0).

[RafaG]

Same problem here. Teslamate v1.28.5, Model 3 2020 v2024.8.7

[djpalmis]

Exactly same configuration (I just add "Long Range"), same issue.

[Hectorgd55]

Hello, in case it helps, my car has an Atom chip and it also shows offline. TeslaMate version is 1.28.4, Model 3 2019 v2024.8.7

[Too5shot]

I also experience this issue on my 2020 Model 3 with Intel Atom, and my Highland Model 3.
Both cars are on 2024.8.7 and I run TeslaMate 1.28.5

[Too5shot]

Just a little update here, my Highland M3 is now showing the correct state.
Nothing chabged as far as I know, still the same versions of TM an Tesla software.

[cwanja]

Well that is not confusing at all. Only thing I could think would be a server side API fix that tells the API endpoint the “proper” state.

Curious if others start seeing the “correct” state logging.

[Too5shot]

I will test with the 2020 M3 as well, just disabled sentry and will post an update when it has "fallen asleep".

[Too5shot]

For the 2020 M3 state is still "Offline".

2024-04-02 21:30:25.003 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
2024-04-02 21:30:25.098 car_id=1 [info] Start / :offline
2024-04-02 21:30:25.102 car_id=1 [info] Disconnecting ...

Was curious so I also pulled the TM logs for the events leading up to "asleep" state for the Highland.

2024-04-02 18:19:24.041 car_id=2 [info] Charging / Complete / 11.00 kWh – 115 min
2024-04-02 18:19:24.041 car_id=2 [info] Start / :online
2024-04-02 18:19:24.045 car_id=2 [info] Connecting ...
2024-04-02 18:21:23.735 car_id=2 [info] Received stream data: :inactive
2024-04-02 18:22:26.760 car_id=2 [info] Suspending logging
2024-04-02 18:23:54.162 car_id=2 [info] Fetching vehicle state ...
2024-04-02 18:26:07.885 car_id=2 [info] Fetching vehicle state ...
2024-04-02 18:28:51.141 car_id=2 [info] Fetching vehicle state ...
2024-04-02 18:30:46.020 car_id=2 [info] Fetching vehicle state ...
2024-04-02 18:30:46.120 car_id=2 [info] Start / :asleep
2024-04-02 18:30:46.124 car_id=2 [info] Disconnecting ...

[cwanja]

This brings back the reality that CPU chip might make a difference. And it potentially further validates that TeslaMate does not impact since your Ryzen Model 3 automagically started sleeping.

More data points, more confusion. But thank you!

[cwanja]

@micves any thoughts? Know PR #3672 changed up the sleep pattern, but I am still not sure that PR caused this impact as cars are just going straight to offline and not a pattern of offline/online/offline etc. Think anything from #3508 ?

If a user had no issues in 1.28.2, jumped right to 1.28.5 - 1.28.3 and 1.28.4 both included "sleep" and "offline" code changes.

[micves]

Only confusion :) #3508 captures the offline message from stream and sets the internal state of Teslamate to offline.
This was not necessarily the real state of the car, since that comes from polling/fetchin on either vehicle_data (/api/1/vehicles/#{id}/vehicle_data) or non-vehicle_data (/api/1/vehicles/#{id})

So #3672 was made to fix this possible temporary change in state:
stream says offline -> go to Teslamate internal state offline -> poll/fetch -> maybe not yet offline (or asleep) -> switch Teslamate internal state dependent on respons

Instead it just triggers an instant poll/fetch and let that handle whatever comes from Tesla servers, something like this instead:
stream says offline -> poll/fetch -> switch Teslamate internal state dependent on respons

The log from here #3797 shows something interesting in the end:

2024-04-01 13:53:23.880 [notice] SIGTERM received - shutting down
2024-04-01 13:53:26.390 [info] Migrations already up
2024-04-01 13:53:28.713 [info] System Info: Erlang/OTP 26 (jit)
2024-04-01 13:53:28.713 [info] Version: 1.28.5
2024-04-01 13:53:30.263 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (1506.007 ms)
2024-04-01 13:53:30.263 [info] Refreshed api tokens
2024-04-01 13:53:30.266 [info] Scheduling token refresh in 6 h
2024-04-01 13:53:30.271 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
2024-04-01 13:53:30.271 [info] Access TeslaMateWeb.Endpoint at http://teslamate.rato.live
2024-04-01 13:53:30.572 [info] Starting logger for 'ZX Spectrum'
2024-04-01 13:53:30.588 [info] MQTT connection has been established
2024-04-01 13:53:30.693 car_id=1 [info] Start / :offline

It looks like Teslamate is restarted and ends up in state offline without stream doing anything (not running at this point)
At startup a poll/fetch is as far as I know used to set the initial internal state.

So I'm just confused about people reporting same Tesla version (2024.8.7) behaves differently on different Teslamate versions.

Does this line end up doing more than what I tried explaining above?

teslamate/lib/tesla_api/stream.ex

Line 158 in 99053e0

state.receiver.(:vehicle_offline)

[cwanja]

@adriankumpf know you rode off into the sunset, but would love any insights you can provide or have on this thread / situation.

[cwanja]

And now someone reporting that without a change to TeslaMate or Tesla in-car software, the state is reporting correctly. Although it was working properly at one point.

[djpalmis]

M3 2020 issue stil present since 2024.8.7

[djpalmis]

Fun(?) Fact:
My M32020, with 2024.8.7, not only received a useless update (no matrix headlights) but they even broke something that worked before (car states).
😟
I'm starting feeling my car "vintage".. 😭

[Kacper2Kaczmarek]

I can confirm that the CPU does make a difference. I have two M3 connected to Teslamate - 2021 (Atom) and 2022 (Ryzen). Now that they're both updated to 2024.8.7, the first one reports as "offline" whereas the second one still correctly reports as "asleep":

[cwanja]

Thanks for the details @Kacper2Kaczmarek! Believe this is further driving the case that this is a Telsa change. But we will still continue to monitor.

Just to confirm, what version of TeslaMate are you running?

[Kacper2Kaczmarek]

I'm on 1.28.5

[cwanja]

Thank you!

[MariusTheUnicorn]

Same here..
Tesla Model 3 2021 Intel Atom.
Tesla Software: 2024.8.7
Teslamate: 1.28.5

[keithdw1972]

I am seeing something similar, the car hasn't slept in over a week apparently - where can I look to find out what is causing this?

Tesla Model Model 3 SR+
Tesla Software: 2024.8.7
Teslamate: 1.28.5

[Too5shot]

If sentry mode is on the vehicle will stay online

[keithdw1972]

hmmm, thats a fabulous answer 👍

someone, probably my wife, has enabled Sentry at home ⭕

[djpalmis]

Any feedback from 2024.8.9 on "Intel CPU"?

[djpalmis]

Thanks for the feedback.
I can't open a service ticket, I suppose 😄

[dsgdesign]

I started this thread in the hopes of understanding what is going on, and I must say it has been a very interesting discussion so far. Thanks to all for your input!

I have been searching to see if users of the TeslaLogger project https://github.com/bassmaster187/TeslaLogger were having similar offline issues, but did not get much out of the issues section on their GitHub repository. There appears to be a discussion of offline status in their German support forum: https://tff-forum.de/t/status-offline-seit-2023-44-30-9-teslalogger-app-traege/327608 but it doesn't seem in relation to 2024.8.X updates.

Interestingly their project appears to have moved on to supporting the new Tesla-Fleet API. Although it might have nothing to do with this particular offline issue we are seeing, I am curious to ask if anyone has tried TeslaLogger and if it can differentiate between offline and asleep status?

[bodosom]

As I noted earlier TeslaFi uses the "new" API and they also started reporting sleep as offline for my MY2022 Model Y (atom processor) after Tesla software version 2024.8.

[dsgdesign]

Understood. I was mostly curious to see if this behaviour was common to different logging platforms, hence my question about TeslaLogger. I guess we are now pretty much in a waiting game until Tesla releases other versions...

[djpalmis]

Not a funny game because the news is that Tesla abandoned development on Intel CPU
https://x.com/NotATeslaApp/status/1780268503150264529

I guess we could wait forever..

[CT2HUU]

I have the same issue.
My 2019 Model X Long Range show "offline" rather "asleep".
I'm in version 2024.8.9 and TeslaMate 1.28.5
Offline is really a different state compared to asleep.
Looking forward to have it nice.

[darek-margas]

This happen to my car after 2024.14.3 upgrade. MY2022/Ryzen

[davigar1391]

Ídem for me. I updated today to 2024.14.3 and it shows offline instead sleep. MY2022 Model 3 with Ryzen

[jaigoff]

Idem for me since 2024.14.3. Model 3 2023 .

[cptzz]

Idem for me after update 2024.14.3, Model 3 2024
Errors in log

[darek-margas]

I noticed it is also reported for Home Assistant Tesla integration as sleeping sensor showing "off" all the time. Must have been an API change, maybe due to new API migration.

[Imaginous]

FYI: Today I have updated my Model 3 (Highland) to version 2024.14.3 and it is now also showing offline instead of asleep.
The Model 3 (Highland) has an AMD chip ofcourse.

[Thebasestar]

Same for me, in Italy

[durzel]

At this point I think I'd be happy to have a settings option to allow offline to be treated as asleep, ala TeslaFi.

ith 2024.14.x it appears that Ryzen cars are being affected as well, so we'll reach a point in which all of the fleet reports offline. Whatever change has been made, it doesn't seem to be a bug from Tesla's perspective, perhaps the opposite - depreciation of the (free?) mechanism for determining status.

Understand the reticence in people to conflate the "offline" and "asleep" states, but if TeslaMate (and co) can't differentiate between those two states anymore then what practical difference does it make?

[StarkITA]

I think it would be the best "user-facing" solution. It leaves the user the choice to have "dirty" data of its own choice, ultimately

[jaredhobbs]

Just wanted to chime in here as well. My Cybertruck has been going from online or charging to offline instead of sleep since the 2024.14 update as well.