TeslaMate [megathread]

init6 · Oct 2, 2021

GeorgeSymonds said:
I'd also look at the API documentation (also on github) if you really want to know to see what data is provided everytime you ask the car. From memory the car tells you how energy is in the battery so it could simply subtract that at the end from the beginning but of course these things are never that simple as the battery reports a bit more after its warmed up and when cooled down again loses some.

That's a good point. The 'size' of the battery changes with temperature, hence why Teslamate has the little snowflake icon when it's cold.

DeltaOne · Oct 3, 2021

The TeslaMate timeline has some unusual entries following my last Model 3 firmware update. See the attached pic.

Anyone else ever see this? Is there any way for me to delete the weird entries?

init6 · Oct 3, 2021

DeltaOne said:
The TeslaMate timeline has some unusual entries following my last Model 3 firmware update. See the attached pic.

Anyone else ever see this? Is there any way for me to delete the weird entries?

Might be related to the streaming errors mentioned above. What version of TM are you on? There was a new version last week to fix that issue.

TM88 · Oct 3, 2021

DeltaOne said:
The TeslaMate timeline has some unusual entries following my last Model 3 firmware update. See the attached pic.

Anyone else ever see this? Is there any way for me to delete the weird entries?

I've seen this discussed on the Teslamate

Trip is additionally recorded in many individual trips · teslamate-org teslamate · Discussion #2022

First of all many thanks for the great piece of work! I've been using teslamate in my new Model 3 for a few days now and I'm very excited about everything you can learn about the car. However, I al...

github.com

If you search for "kcdr", when I last looked, it was the last post, might have a solution to help sort out the issue.
Let us know how you got on if you decide to try it out.

DeltaOne · Oct 3, 2021

init6 said:
Might be related to the streaming errors mentioned above. What version of TM are you on? There was a new version last week to fix that issue.

I'm on 1.24.2. I think that's the current release version.

DeltaOne · Oct 3, 2021

TM88 said:
I've seen this discussed on the Teslamate

Trip is additionally recorded in many individual trips · teslamate-org teslamate · Discussion #2022

First of all many thanks for the great piece of work! I've been using teslamate in my new Model 3 for a few days now and I'm very excited about everything you can learn about the car. However, I al...

github.com

If you search for "kcdr", when I last looked, it was the last post, might have a solution to help sort out the issue.
Let us know how you got on if you decide to try it out.

Thanks, I'll check it out and report back.

hakunamattata · Oct 3, 2021

I just upgraded Teslamater, after reboot I am getting an "INternal Server Error". Attached is a snippet of docker logs, any suggestions?

021-10-03 22:35:55.684 [error] Task #PID<0.4720.0> started from #PID<0.4664.0> terminating
** (stop) exited in: GenServer.call(TeslaMate.Mqtt.Publisher, {

ublish, "teslamate/cars/1/trim_badging", "", [retain: true, qos: 1]}, 10000)
** (EXIT) an exception was raised:
** (WithClauseError) no with clause matching: {:error, :timeout}
(tortoise 0.10.0) lib/tortoise.ex:269: Tortoise.publish/4
(teslamate 1.24.2) lib/teslamate/mqtt/publisher.ex:41: TeslaMate.Mqtt.Publisher.handle_call/3
(stdlib 3.16) gen_server.erl:721: :gen_server.try_handle_call/4
(stdlib 3.16) gen_server.erl:750: :gen_server.handle_msg/6
(stdlib 3.16) proc_lib.erl:226:

roc_lib.init_p_do_apply/3
(elixir 1.12.3) lib/gen_server.ex:1024: GenServer.call/3
(elixir 1.12.3) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
(elixir 1.12.3) lib/task/supervised.ex:35: Task.Supervised.reply/5
(stdlib 3.16) proc_lib.erl:226:

roc_lib.init_p_do_apply/3
Function: &:erlang.apply/2
Args: [#Function<4.48828428/1 in TeslaMate.Mqtt.PubSub.VehicleSubscriber.handle_info/2>, [trim_badging: nil]]
2021-10-03 22:35:55.690 [error] Task #PID<0.4726.0> started from #PID<0.4664.0> terminating
** (stop) exited in: GenServer.call(TeslaMate.Mqtt.Publisher, {

ublish, "teslamate/cars/1/latitude", "45.648821", [retain: true, qos: 1]}, 10000)
** (EXIT) an exception was raised:
** (WithClauseError) no with clause matching: {:error, :timeout}
(tortoise 0.10.0) lib/tortoise.ex:269: Tortoise.publish/4
(teslamate 1.24.2) lib/teslamate/mqtt/publisher.ex:41: TeslaMate.Mqtt.Publisher.handle_call/3
(stdlib 3.16) gen_server.erl:721: :gen_server.try_handle_call/4
(stdlib 3.16) gen_server.erl:750: :gen_server.handle_msg/6
(stdlib 3.16) proc_lib.erl:226:

roc_lib.init_p_do_apply/3
(elixir 1.12.3) lib/gen_server.ex:1024: GenServer.call/3
(elixir 1.12.3) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
(elixir 1.12.3) lib/task/supervised.ex:35: Task.Supervised.reply/5
(stdlib 3.16) proc_lib.erl:226:

roc_lib.init_p_do_apply/3
Function: &:erlang.apply/2
Args: [#Function<4.48828428/1 in TeslaMate.Mqtt.PubSub.VehicleSubscriber.handle_info/2>, [latitude: 45.648821]]
2021-10-03 22:36:15.568 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.568 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.568 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.569 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.569 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.569 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.570 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.570 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.571 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.571 [warn] MQTT publishing failed: :timeout

init6 · Oct 3, 2021

hakunamattata said:
I just upgraded Teslamater, after reboot I am getting an "INternal Server Error". Attached is a snippet of docker logs, any suggestions?

021-10-03 22:35:55.684 [error] Task #PID<0.4720.0> started from #PID<0.4664.0> terminating
** (stop) exited in: GenServer.call(TeslaMate.Mqtt.Publisher, {ublish, "teslamate/cars/1/trim_badging", "", [retain: true, qos: 1]}, 10000)
** (EXIT) an exception was raised:
** (WithClauseError) no with clause matching: {:error, :timeout}
(tortoise 0.10.0) lib/tortoise.ex:269: Tortoise.publish/4
(teslamate 1.24.2) lib/teslamate/mqtt/publisher.ex:41: TeslaMate.Mqtt.Publisher.handle_call/3
(stdlib 3.16) gen_server.erl:721: :gen_server.try_handle_call/4
(stdlib 3.16) gen_server.erl:750: :gen_server.handle_msg/6
(stdlib 3.16) proc_lib.erl:226: roc_lib.init_p_do_apply/3
(elixir 1.12.3) lib/gen_server.ex:1024: GenServer.call/3
(elixir 1.12.3) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
(elixir 1.12.3) lib/task/supervised.ex:35: Task.Supervised.reply/5
(stdlib 3.16) proc_lib.erl:226: roc_lib.init_p_do_apply/3
Function: &:erlang.apply/2
Args: [#Function<4.48828428/1 in TeslaMate.Mqtt.PubSub.VehicleSubscriber.handle_info/2>, [trim_badging: nil]]
2021-10-03 22:35:55.690 [error] Task #PID<0.4726.0> started from #PID<0.4664.0> terminating
** (stop) exited in: GenServer.call(TeslaMate.Mqtt.Publisher, {ublish, "teslamate/cars/1/latitude", "45.648821", [retain: true, qos: 1]}, 10000)
** (EXIT) an exception was raised:
** (WithClauseError) no with clause matching: {:error, :timeout}
(tortoise 0.10.0) lib/tortoise.ex:269: Tortoise.publish/4
(teslamate 1.24.2) lib/teslamate/mqtt/publisher.ex:41: TeslaMate.Mqtt.Publisher.handle_call/3
(stdlib 3.16) gen_server.erl:721: :gen_server.try_handle_call/4
(stdlib 3.16) gen_server.erl:750: :gen_server.handle_msg/6
(stdlib 3.16) proc_lib.erl:226: roc_lib.init_p_do_apply/3
(elixir 1.12.3) lib/gen_server.ex:1024: GenServer.call/3
(elixir 1.12.3) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
(elixir 1.12.3) lib/task/supervised.ex:35: Task.Supervised.reply/5
(stdlib 3.16) proc_lib.erl:226: roc_lib.init_p_do_apply/3
Function: &:erlang.apply/2
Args: [#Function<4.48828428/1 in TeslaMate.Mqtt.PubSub.VehicleSubscriber.handle_info/2>, [latitude: 45.648821]]
2021-10-03 22:36:15.568 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.568 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.568 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.569 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.569 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.569 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.570 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.570 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.571 [warn] MQTT publishing failed: :timeout
2021-10-03 22:36:15.571 [warn] MQTT publishing failed: :timeout

I'd maybe check your config files - especially around mqtt.
What are you running this on? a cloud server or something of your own?

hakunamattata · Oct 4, 2021

init6 said:
I'd maybe check your config files - especially around mqtt.
What are you running this on? a cloud server or something of your own?

Running it on my own Raspberry Pi, it is weird but for some reason the containers within docker were running for past 4 weeks, even after an OS reboot. I recycled all Teslamate related containers and that seems to have resolved the problem

DeltaOne · Oct 4, 2021

TM88 said:
I've seen this discussed on the Teslamate

Trip is additionally recorded in many individual trips · teslamate-org teslamate · Discussion #2022

First of all many thanks for the great piece of work! I've been using teslamate in my new Model 3 for a few days now and I'm very excited about everything you can learn about the car. However, I al...

github.com

If you search for "kcdr", when I last looked, it was the last post, might have a solution to help sort out the issue.
Let us know how you got on if you decide to try it out.

The link you posted had great info. I've decided that the "fix" (editing the database) is beyond my capability and would require more research/time than I want to spend on this. Thanks for the link!

I may have gotten the weird entries before updating to 1.24.2, I don't remember which event happened first.

TM88 · Oct 4, 2021

DeltaOne said:
The link you posted had great info. I've decided that the "fix" (editing the database) is beyond my capability and would require more research/time than I want to spend on this. Thanks for the link!

I may have gotten the weird entries before updating to 1.24.2, I don't remember which event happened first.

It happened to me on 2 drives of different days before I updated to 1.24.2, and like you I decided to leave as it is too.

acatwith12 · Oct 4, 2021

init6 said:
One more question - do drives or charges that happened prior to 30/9 (UK & Ireland Forum )display properly, or have they all disappeared too?

So I just updated... drives or chargers prior to 9/30 are there. Update did not fix the missing location on drive/charges on only 9/30. Drives/charges after 9/30 appear... weird lol

init6 · Oct 4, 2021

acatwith12 said:
So I just updated... drives or chargers prior to 9/30 are there. Update did not fix the missing location on drive/charges on only 9/30. Drives/charges after 9/30 appear... weird lol

Do you mean they appear and that's weird or they appear weird?

The update likely wouldn't fix anything that has already happened. IIRC it was just to stop them from being wrongly created. Have you had any erroneous drives charges since you updated?

acatwith12 · Oct 4, 2021

init6 said:
Do you mean they appear and that's weird or they appear weird?

The update likely wouldn't fix anything that has already happened. IIRC it was just to stop them from being wrongly created. Have you had any erroneous drives charges since you updated?

No erroneous drives/charges, just that every drive on 9/30 doesn't display location on the main page of each Drives/Charges. If I click in to the timestamp it will show the location correctly. Maybe a visual bug who knows but not glaring since my data is still recorded as far as I can tell

phil4 · Oct 5, 2021

Never noticed that before... my car is now shown as a Model 3 P74D. It's a 2020 (chrome) Performance.

Wonder if others with the MIC and the like see different?

init6 · Oct 5, 2021

phil4 said:
Never noticed that before... my car is now shown as a Model 3 P74D. It's a 2020 (chrome) Performance.

Wonder if others with the MIC and the like see different?

Same here - 2021 LR. Seems to be the trim badging field.

Bobly · Oct 5, 2021

init6 said:
Same here - 2021 LR. Seems to be the trim badging field.

Same here, seems to have begun showing up in the API responses since some time yesterday.

GeorgeSymonds · Oct 5, 2021

API seems really flaky at the moment, I’ve seen a few comments on it being variable and some of the old api calls have now been stopped

init6 · Oct 5, 2021

There's a worry that not supported becomes not allowed.

GeorgeSymonds · Oct 5, 2021

init6 said:
There's a worry that not supported becomes not allowed.

I think its more chasing round finding the new version of the API and cross referencing the old data to the new - take the naming convention, that’s changed to the old school P for performance, battery side, D for dual motor.

TeslaMate [megathread]

Active Member

Member

Attachments

Active Member

Member

Member

Member

Member

Active Member

Member

Member

Member

Member

Active Member

Member

Member

Active Member

Attachments

Member

Active Member

Active Member

Active Member

Similar threads