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).

[cwanja]

Cross pollination from TMC - seems the state behavior might be related to the chip inside of your Tesla. Per TMC

Atom chips show “offline” | Ryzen chips show “asleep”

Further showing that there might be a Tesla software issue. Not ruling out TeslaMate given reports of people rolling TeslaMate back and states reporting “normal”. But I am not confident in that reporting. I am also re-opening to continue to the discussion.

[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.

[chk2902]

Bei mir evtl. darauf zurückzuführen:

[Thread Pool Worker:6]: Result.Statuscode: 429 (TooManyRequests) cmd: vehicle_data?endpoints=vehicle_config&let_sleep=true Sleep: 42408000ms, ratelimit-limit: 300, ratelimit-remaining: 0, ratelimit-reset: 42408, sleep till: 13.06.2024 02:00:00

Sprich zu viele Abfragen?

Mal abwarten. Parallel habe ich eine andere App, die auch das Auto abfragt, und Tronity (ein bisserl viel, aber ich experimentiere gerade, was die beste App ist, und meine App braucht für die Überschussladung die SoC-Daten)

[djpalmis]

Note that the native Tesla app can distinguish between offline and "asleep" so it would seem Tesla chooses not to share that state with Teslamate or equivalent software.

Can you elaborate this? How do you understand if it is offline or in sleep in Tesla app?
I mean: as soon as you start the app the car wakes up.. so.. it will be online for sure. I don't understand.

[durzel]

Note that the native Tesla app can distinguish between offline and "asleep" so it would seem Tesla chooses not to share that state with Teslamate or equivalent software.

Can you elaborate this? How do you understand if it is offline or in sleep in Tesla app?

I mean: as soon as you start the app the car wakes up.. so.. it will be online for sure. I don't understand.

The Tesla app will report "Asleep for X hours" in small grey text below the car graphic. I have no idea how accurate this number is, as I've not bothered to compare.

It is noteworthy that the app recognises and tells the user the car is/was asleep, though. It didn't previously do that.

As we know the Tesla app wakes the car up when opened, so it's not much use to try and use this info about how long the car has been asleep, unlike in TeslaMate.

[Olyts]

Agreed, just looked at my « state » page it does report ( 2 occasions) a sleep state… but inconsistently. Very strange…

[bodosom]

Note that the native Tesla app can distinguish between offline and "asleep" so it would seem Tesla chooses not to share that state with Teslamate or equivalent software.

Can you elaborate this? How do you understand if it is offline or in sleep in Tesla app? I mean: as soon as you start the app the car wakes up.. so.. it will be online for sure. I don't understand.

Until recently the native app would report "last seen ..." until the car was back "online" or report an error. I assumed the former was sleep and the latter was "offline". As noted the current app (4.34.0 in my case) actually says asleep for N hours until the car comes online. However in my app (Apple) the "Asleep ..." status line replaces Parked, just below the battery icon.

[mtuan293]

Note that the native Tesla app can distinguish between offline and "asleep" so it would seem Tesla chooses not to share that state with Teslamate or equivalent software.

Can you elaborate this? How do you understand if it is offline or in sleep in Tesla app?
I mean: as soon as you start the app the car wakes up.. so.. it will be online for sure. I don't understand.

The Tesla app will report "Asleep for X hours" in small grey text below the car graphic. I have no idea how accurate this number is, as I've not bothered to compare.

It is noteworthy that the app recognises and tells the user the car is/was asleep, though. It didn't previously do that.

As we know the Tesla app wakes the car up when opened, so it's not much use to try and use this info about how long the car has been asleep, unlike in TeslaMate.

Before the update, my car was running 2024.3.25, Teslamate reported "Asleep", and the official Tesla app reported "Last seen".
Ever since updating to 2024.14.9, Teslamate now reports "Offline", the Tesla app now shows "Asleep for ... hours".
Not sure if the app can distinguish between asleep, offline or last seen whatever. Those are the differences I have noticed so far.

What if this is just some wording changes by Tesla? Or are there actual technical differences?

2024 Model Y Performance. So whatever latest hardware as of now.

[LelandSindt]

On 6/13/2024 I went from 2024.3.25 to 2024.14.9 and started seeing this issue. And when I say seeing, I mean it quite literally.... My project Gaussmeter is pulsing purple.

As this behaviour seems to be spreading, is it still the prevailing logic that that a "Treat Offline and Asleep" mode is still un-necessary?

[rsunny2012]

Hello,

Currently i am on 2024.14.9 and i have upgraded teslamate to 1.29.2. I am still seeing car is in offline ( when its asleep). i am not getting charging data during night time.

[cwanja]

Currently i am on 2024.14.9 and i have upgraded teslamate to 1.29.2. I am still seeing car is in offline ( when its asleep)

Version 1.29.2 does not alter the way TeslaMate records and displays "sleep" patterns; it will continue to register as offline. It is presumed that Tesla has chosen not to differentiate between 'sleep' and 'offline' states in the API endpoint, opting to display only 'offline'. While their first-party app may show these states, that advantage stems from their ownership of both the API and the app. Currently, there is no consensus on updating TeslaMate to display 'sleep' rather than 'offline'.

i am not getting charging data during night time.

If your car wakes to charge, this should be recorded how it previously was. There has been no change to this behavior pattern. If you believe there is an issue, gather the logs and submit an issue.

[rsunny2012]

sure. thanks for the response.

[mbuico]

Same here.
for statistical purposes only.. 2023 model 3 Standard Range Ryzen CPU update 2024.20.1

[abc123xxx]

Is the whole thing fixed/corrected in TeslaMate 1.29.2?

[durzel]

No, see #3753 (reply in thread)

[jheredianet]

It has been quite some time since this has been progressively happening with all types of car firmware versions.
Maybe we should consider that the states that Tesla now gives is: Offline = Asleep

What is your opinion?

[durzel]

I'd at least like to have the option to have "dirty data" and "treat offline as asleep", ala TeslaFi.

Also, would it not be possible to take an educated guess as to the real state based on the previous one?

• if the car goes from "online" to "falling asleep" and then to "offline", in an orderly way, it's very likely it is "asleep" instead.
• If the car goes straight from "online" to "offline" - then it is more likely that the car has no LTE service and is actually offline.

[Olyts]

Might be difficult since I occasionally see some sleep mode, and a lot of offline. So there is still some “sleep mode” info available somewhere since the updates…

[TheDK]

Same here - once very 5-10 times I'd say... So it does not seem to be deliberate? Maybe the MCU does go offline before the sleep state goes through?

[abc123xxx]

What is the current standing? Is a solution being worked on?

[durzel]

Since i updated to 2024.20.9 on sunday, the asleep state is back!

Thanks, but this feedback isn't much use without vehicle information - particularly MCU chipset (Ryzen or Atom).

I'm on 2024.20.9 and have not seen any difference (2020 M3P, Atom). "Asleep" still not reported by TeslaMate.

[jjpeersman]

Also, it seems to be a one-off as after the drive tomorrow it is back to offline… (2024 MY, Ryzen)

[jrothlis]

Still showing offline for me on 2024.20.9 - Atom, M3 LR 2019.

[Imaginous]

I have seen the same behavior, after an update the car is asleep, but after one drive it shows offline again.

[jheredianet]

I have seen the same behavior, after an update the car is asleep, but after one drive it shows offline again.

Same here, it worked just once. Then it came back to offline again.

[git-anish]

Since updating to 2024.15.15 on the 10th of July the asleep state appears ~ once per day

Its seemingly random, anecdotally the sleep state appears more often after exiting and locking the car rather when the car is entering and exiting sleep state unattended.

2023 Model S LR - Ryzen

[Olyts]

Yes, I also did noticed a state change from offline to sleep after a brief online moment.

[durzel]

Apropos of nothing but the latest Tesla app (4.35.0) - at least on iOS - now no longer wakes up the car when you open it. Instead, it only wakes it up if you send a command, or pull down to refresh.

This might be significant in the context of comparing TeslaMate and the app. I suspect the app will say "Asleep for X hours" while TeslaMate will be reporting offline.

[cwanja]

It is an improvement. But if you press into 'Controls' without actually sending a command, it still wakes the car up. Not sure what is 'pulled' from the vehicle to just load the commands screen, but not send a command. But it's a nice quality of life improvement regardless.

And it seems the car can now 'sleep' for longer periods of time. Mine was at 13 hours when I launched the app today.

[bodosom]

... the app used to say "Last seen X hours" and Teslamate reported that as "Sleep". Now it's "Asleep" in the app and Teslamate says "Offline".

I did a screen recording of V4.34 and it said "Last seen ..." for a frame or two and then "Asleep for ..." and then "Parked". What has changed for me in V4.35 is the app no longer shows a status change of Asleep to Parked just from opening the native app.

As reported many, many, many times previously Teslamate (in most cases) still can't distinguish between Asleep and Offline although Tesla (at least the native Tesla app) does make that distinction. Tessie (which is purported to use the new API) has the same behavior but it reports Asleep instead of Offline while Teslafi let you pick which status to report.

[cwanja]

It is an improvement. But if you press into 'Controls' without actually sending a command, it still wakes the car up. Not sure what is 'pulled' from the vehicle to just load the commands screen, but not send a command. But it's a nice quality of life improvement regardless.

This implementation is flawed it seems. Seems any sub-menu you click into wakes the car. Or if you refresh the main page, it wakes the car. Maybe this is laying foundation for future enhancements. But as of today, engaging anywhere within the app still wakes the car, regardless of whether you send a command or not.

Edit: I will make a correction. It seems that there are certain menus that do not wake the car (namely service, thankfully). Essentially, be selective / mindful in what you do when the app is open.

[mtuan293]

As reported many, many, many times previously Teslamate (in most cases) still can't distinguish between Asleep and Offline although Tesla (at least the native Tesla app) does make that distinction.

I don't think that's a limitation in Teslamate but rather a change from Tesla. As some have reported their Teslamate still ocasionally reports Sleep in between Offline states. I notice the app now says Asleep instead of Last seen so definitely something has changed from Tesla's end.

Tessie (which is purported to use the new API) has the same behavior but it reports Asleep instead of Offline while Teslafi let you pick which status to report.

This seems like Tessie just changed their wording to "Asleep" to match the native app. 🤔 What new API are you talking about?

[bodosom]

I don't think that's a limitation in Teslamate but rather a change from Tesla.

This has also been mentioned many times in multiple threads.

[dahouet]

Hello

Interesting thing
State changed to Asleep from offline last night without a wake of the car

Only this logline in TeslaMate :
2024-07-19T01:59:45.276770494Z,stdout,2024-07-19 03:59:45.276 car_id=1 [info] Start / :asleep

[StarkITA]

Could you specify which MCU?

[mechoriet]

after updating today to 2024.26.3.1 on my m3 2024

this is the first time I've seen this state other then offline(asleep)
could it be they fixed it in this update or just a rare detection of it?

[Olyts]

I don’t think this “fixed” by this update. Wake up your car and let it sleep again. You’ll find out.

[mechoriet]

well woke it up from the app and let it go offline/sleep again

[cwanja]

This has been the last seven days of states for me (not driving a lot at the moment).

I do not actually believe it will take an in-car software update. I feel like the owners API is just receiving the wrong information. Maybe the owners API is dependent upon the in-car software, but I find that hard to believe.

Version 2024.15.15. Similar pattern to @git-anish, but sleeping more frequently than once per day.

[ktsenvolt]

Today is the first day I saw the car asleep.
2020 Model 3 2024.26.3.1
Teslamate 1.30.1

[a1exus]

Today is the first day I saw the car asleep. 2020 Model 3 2024.26.3.1 Teslamate 1.30.1

What changed? Did you update Tesla software or?

[ktsenvolt]

It did not work the next day. It is just the Tesla F/W updated.

[MariusTheUnicorn]

Teslamate still offline other than asleep...

2021 Model 3 SR+ (LFP battery) (MCU2-Intel)

Teslamate 1.30.1

Tesla software 2024.26.6

Can teslamate pleeease give a option to fix this? Just e button or something? Offline to Asleep manually...

//Marius

[Olyts]

Well, mine is much better since 2 days!

[LelandSindt]

Wonder if it's even worth recording any more?

Please do not drop support for logging/reporting the car state as reported by Tesla... I use it.

[cwanja]

Why does "falling asleep" last a variable amount of time?

As said, when Cabin Overheat Protection is active on my car, and everything else that would otherwise keep it online is deactivated (e.g. Sentry, climate, etc), TM will report it "falling asleep" for hours.

Other times it seems to last sound 15 mins, until the HV contactors go, at which point it will report "offline".

Doesn't the fact it is reported on the UI for a variable amount of time, between the true "online" and "offline" states, mean it has meaning? (even if it only relates to TM's own state).

To turn your argument on its head - how (and indeed why) does TM report "falling asleep"? Why/when is it choosing to report that? Why shouldn't it just go from "online" straight to "offline" - the car's true state changes?

Let me try my best to reply to your entire message. There is a lot of history and anyone who has tracked TeslaMate for years and remembers differently, please chime in.

Tesla API used to be that if you poll it, you would keep the car awake. Thus, TeslaMate implemented a "falling asleep" method where the app would not poll the car to let it sleep. Tesla implemented a non-waking (word?) API endpoint to check for the "state" of the car. Thus in the window of TeslaMate displaying "Falling asleep", TeslaMate is polling this API endpoint to look for a state change. It used to be anywhere from 20 to 30 minutes before it would fall asleep. Some users saw almost an hour (personally think I was one of them). There is no "defined" amount of time that TeslaMate waits in a "falling asleep" state. It is just a visual UI label that shows TeslaMate is letting the car enter asleep or offline states as reported by the API. Scan you states table and you will not find a single "falling asleep" state.

[bodosom]

Wonder if it's even worth recording any more?

I would say no. Of course I don't see the point of having the streaming API be a toggle. I would say drop the streaming toggle and presumably "falling asleep" falls away.

[durzel]

Why does "falling asleep" last a variable amount of time?
As said, when Cabin Overheat Protection is active on my car, and everything else that would otherwise keep it online is deactivated (e.g. Sentry, climate, etc), TM will report it "falling asleep" for hours.
Other times it seems to last sound 15 mins, until the HV contactors go, at which point it will report "offline".
Doesn't the fact it is reported on the UI for a variable amount of time, between the true "online" and "offline" states, mean it has meaning? (even if it only relates to TM's own state).
To turn your argument on its head - how (and indeed why) does TM report "falling asleep"? Why/when is it choosing to report that? Why shouldn't it just go from "online" straight to "offline" - the car's true state changes?

Let me try my best to reply to your entire message. There is a lot of history and anyone who has tracked TeslaMate for years and remembers differently, please chime in.

Tesla API used to be that if you poll it, you would keep the car awake. Thus, TeslaMate implemented a "falling asleep" method where the app would not poll the car to let it sleep. Tesla implemented a non-waking (word?) API endpoint to check for the "state" of the car. Thus in the window of TeslaMate displaying "Falling asleep", TeslaMate is polling this API endpoint to look for a state change. It used to be anywhere from 20 to 30 minutes before it would fall asleep. Some users saw almost an hour (personally think I was one of them). There is no "defined" amount of time that TeslaMate waits in a "falling asleep" state. It is just a visual UI label that shows TeslaMate is letting the car enter asleep or offline states as reported by the API. Scan you states table and you will not find a single "falling asleep" state.

Thanks, that's a comprehensive explanation.

I guess what I'm saying in a roundabout way is that at the point the TeslaMate UI displays "falling asleep", to the point it changes to something else, that (unless I'm fundamentally misunderstanding) this could be recorded in the "states" table. That would ultimately facilitate a "predictive sleep" enhancement that would let users treat "offline" as "asleep" in the case where the car transitions from "falling asleep" to "offline".

[djpalmis]

I did not change anything! No firmware update, no reset, nothing!
I was playing a little with Tesla app, setting charging costs, nothing more.
I don't even think I woke up the car because I did not send any command 🤷🏻‍♂️

[Olyts]

Car was plugged in right? I was on 2024.26.6 and sleeping was showing very often… since 2023.25.7 it was back to offline… since this morning, first “asleep”, car was connected over night. Will se how it goes this week.

[djpalmis]

Yes, it was plugged since yesterday.
My car is on 2024.26.7 since a couple of weeks.

[djpalmis]

Back to offline, as usual. Maybe it was just a glitch

[git-anish]

Update from this earlier message

Here's what I observed over the last 8.5 days while the car was parked and left alone:

• The car is still on 2024.15.15, no OTAs have been installed since Jul 10
• The car spent ~42% of the time 'asleep' and the rest in the 'offline' state
• 24 total long duration states, 10 asleep, 14 offline
• Out of 10 asleep cycles, 6 times the car entered 'asleep' after being 'offline' 2x
• On Sep 13, the car woke up for 16 minutes, went offline for 10 minutes, and transitioned back to 'asleep' without waking again. This is unique since it didn’t happen at other times during this period.
• The Sep 13 behaviour makes me think that the offline vs. asleep distinction may be API-driven rather than based on what the car is reporting. This is the first time I’ve left the car alone for this long since this issue began.

Has anyone else seen similar behaviour?
I'd love to hear if others notice the same asleep/offline behaviour when leaving the car untouched for a while.