Frequent off-line state in 1.28.3

[bodosom]

Are other people seeing this?

28.3

28.2

[zknobody]

I did see 1 offline since the update
Also noticed the car waking up for some unknown reason, not sure if it's related to this

[bodosom]

The constant wake/sleeps in my states display are from my power company time-of-use monitor.

[zknobody]

try giving the vehicle MCU a reboot, this might of worked for me

[bodosom]

I have two instances of TeslaMate 1.28.2 and 1.28.3. The issue is that only the 1.28.3 instance is reporting off-line.

[zknobody]

not sure what's causing the wake up for me but I have had the offline occur twice in 24 hrs
if anyone knows which logs to check let me know

[cwanja]

Seeing zero offline states in the last seven days.

[bodosom]

I have an time-of-use app that constantly wakes my car if it's plugged in and there's a pending charge (as shown in the state graphic above). The off-line instances seem to be somewhat interleaved with those wakes. I didn't have a scheduled charge in the last 24 hours so the car was asleep overnight and there were no instances of going off-line.

[micves]

@bodosom do you have a log you can share in the same timespan as the screenshot?

I would like to see if you have something like this:

[info] Streaming API: Vehicle offline
car_id=1 [info] Stream reports vehicle as offline

Because that was added in 1.28.3 (and might be a bit to aggressive)

[micves]

And maybe there is a rational explanation for it :) Do you have the log from when it happened?

[bodosom]

 2024-02-22 05:03:07.219 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/149... -> error: "non-existing domain" (8004.509 ms)
 2024-02-22 05:03:07.219 [warning] TeslaApi.Error / non-existing domain 
 2024-02-22 05:03:07.220 car_id=1 [error] Error / :unknown
 2024-02-22 05:03:29.467 [info] Streaming API: Vehicle offline
 2024-02-22 05:03:29.467 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
 2024-02-22 05:03:29.861 car_id=1 [info] Start / :offline 
 2024-02-22 05:03:29.873 car_id=1 [info] Disconnecting ...    
 2024-02-22 05:07:53.768 [notice]     :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_1_api_error}
 2024-02-22 05:33:26.692 car_id=1 [info] Start / :online
 2024-02-22 05:33:26.720 car_id=1 [info] Connecting ...
 2024-02-22 05:35:08.977 car_id=1 [info] Charging detected: -1 kW
 2024-02-22 05:35:09.871 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (368.580 ms)
 2024-02-22 05:35:09.911 car_id=1 [info] Charging / SOC: 57% / Home
 2024-02-22 05:35:09.911 car_id=1 [info] Disconnecting ...

[brianmay]

"non-existing domain" does look like some sort of DNS issue on your end. But after that it seems to resolve "nominatim.openstreetmap.org" OK. Weird.

[bodosom]

Doh! I had a network outage in that window. I'll grab the prior instances data but it seems innocuous.

[bodosom]

I can provide more exhaustive logging if it helps.
Blank lines represent elided material.

 2024-02-19 18:17:33.788 car_id=1 [info] Vehicle is still online. Falling asleep for: 36 min
 2024-02-19 18:20:40.854 [info] GET /
 2024-02-19 18:20:40.867 [info] Sent 200 in 12ms
 2024-02-19 18:20:43.301 [info] GET /
 2024-02-19 18:20:43.311 [info] Sent 200 in 10ms
 2024-02-19 18:29:58.887 [info] Streaming API: Vehicle offline
 2024-02-19 18:29:58.888 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
 2024-02-19 18:29:59.293 car_id=1 [info] Start / :offline
 2024-02-19 18:29:59.306 car_id=1 [info] Disconnecting ...
 2024-02-19 18:30:19.619 car_id=1 [info] Start / :asleep
 2024-02-19 18:41:03.486 car_id=1 [info] Start / :online
 2024-02-19 18:41:03.518 car_id=1 [info] Connecting ...

 2024-02-19 18:45:50.965 [warning] GET https://owner-api.teslamotors.com/api/1/vehicles/14.../vehicle_data -> 540 (2838.140 ms)
 2024-02-19 18:45:50.965 [warning] TeslaApi.Error / vehicle error: it is online but not responsive
 2024-02-19 18:45:50.965 car_id=1 [error] Error / :unknown
 2024-02-19 18:46:11.526 car_id=1 [info] Suspending logging
 2024-02-19 18:49:29.375 [warning] Too many disconnects from streaming API
 2024-02-19 18:49:29.375 car_id=1 [info] Creating new connection …
 2024-02-19 18:49:29.375 car_id=1 [info] Disconnecting ...
 2024-02-19 18:49:29.387 car_id=1 [info] Connecting ...
 2024-02-19 18:51:50.260 [notice]     :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_1_api_error}

 2024-02-19 18:55:36.312 [info] Streaming API: Vehicle offline
 2024-02-19 18:55:36.312 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
 2024-02-19 18:55:36.730 car_id=1 [info] Start / :offline
 2024-02-19 18:55:36.742 car_id=1 [info] Disconnecting ...
 2024-02-19 19:07:21.107 car_id=1 [info] Start / :online
 2024-02-19 19:07:21.133 car_id=1 [info] Connecting ...

[micves]

It seems to be okay, even though this one is a bit strange:

2024-02-19 18:29:58.887 [info] Streaming API: Vehicle offline
2024-02-19 18:29:58.888 car_id=1 [warning] Stream reports vehicle as offline, fetching vehicle state ...
2024-02-19 18:29:59.293 car_id=1 [info] Start / :offline
2024-02-19 18:29:59.306 car_id=1 [info] Disconnecting ...
2024-02-19 18:30:19.619 car_id=1 [info] Start / :asleep

Stream reports offline and the state is fetched and result is offline
20 seconds later with the same internal kind of fetch, the result is asleep instead.
I would think the same timing of fetches in earlier versions of teslamate would make the same pattern.

[bodosom]

After updating to 2024.8.4 all sleeps are marked as off-line. #3751

In #3751 (reply in thread) @cwanja said:

You should consider moving back to the main branch as that branch has been merged into master and released. If the master release does not resolve your issue, I would comment back on your original post #3658 and tag the @micves for review. Again, logs are going to be needed to troubleshoot.
Going to lock this to prevent duplicate efforts.

I provisioned image: teslamate/teslamate:latest (1.28.4)

Log attached:
Log.txt

[micves]

Is the log.txt only suppose to be 40 lines or was it unintentionally cut off?

I don't see any troubling in the log. There are some timeouts but that could just be Tesla server/api stuff.

The offline state is coming from Tesla, so there is not much to do about it.
I'm on a Model S from 2017 upgraded to MCU2. I only see offline, never asleep.

[bodosom]

Is the log.txt only suppose to be 40 lines or was it unintentionally cut off?

That snippet is since the last restart at the time of capture. I can provide a refresh if it seems useful.

[micves]

Not really actually. It seems to be a Tesla thing. They might fix it again later or you just live with it like I do :)

[cwanja]

I believe based upon all of the collective evidence we have, it seems Tesla in-car software branch starting with 2024.X has changed from "sleeping" to offline. I would be curious if anyone could go to their car when it has been "offline" for several hours and see if you press a door handle or something and heard the HV battery "click" on. If so, then offline is the new asleep in 2024.X and we could consider changing the recorded pattern from offline to asleep.

But this does not seem like an "issue" with TeslaMate.

[durzel]

I woke my car up this morning via the app, and it went from offline to online in TeslaMate. It was definitely asleep at the time because I heard the contactors.

It could be that Tesla don't disambiguate between "offline" and "asleep" anymore. A bit annoying because the car is obviously listening for network communications even when asleep to be able to be woken up via the app, etc. "Offline" to me means it is unreachable.

[cwanja]

Thanks for the that information @durzel.

I am hesitant to suggest an immediate change because Tesla could reverse the software decision (or bug) and we would not know they re-introduce an actual "offline" state. But this at least gives us more data to go off.

[jheredianet]

After updating to 2024.8.4 all sleeps are marked as off-line. #3751

In #3751 (reply in thread) @cwanja said:

You should consider moving back to the main branch as that branch has been merged into master and released. If the master release does not resolve your issue, I would comment back on your original post #3658 and tag the @micves for review. Again, logs are going to be needed to troubleshoot.
Going to lock this to prevent duplicate efforts.

I provisioned image: teslamate/teslamate:latest (1.28.4)

Log attached: Log.txt

Same behaviour here, not sure if Tesla now is considering "asleep" as "offline" state.

This is what is happening:

[bodosom]

This is discussed and resolved here: #3753

[cwanja]

Going to close as per the comment here #3753 (comment)

[jheredianet]

BTW, just to point that it's not only reporting "offline" but also that the driver is present

Tested in different scenarios and the behaviour is the same. Are you having the same behaviour?

[durzel]

No I'm not seeing spurious "driver present" states, sorry.