Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

TeslaMate [megathread]

init6

Member
Oct 16, 2020
951
596
Scotland
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.
 
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?
 

Attachments

  • Screen Shot 2021-10-03 at 10.55.38 AM.png
    Screen Shot 2021-10-03 at 10.55.38 AM.png
    83.7 KB · Views: 33

TM88

Member
Apr 12, 2021
43
28
LONDON
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
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.
 
I've seen this discussed on the Teslamate
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.
 
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, {:publish, "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: :proc_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: :proc_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, {:publish, "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: :proc_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: :proc_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

Member
Oct 16, 2020
951
596
Scotland
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, {:publish, "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: :proc_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: :proc_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, {:publish, "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: :proc_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: :proc_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?
 
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
 
I've seen this discussed on the Teslamate
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

Member
Apr 12, 2021
43
28
LONDON
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.
 

init6

Member
Oct 16, 2020
951
596
Scotland
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?
 
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
 
  • Like
Reactions: init6

Products we're discussing on TMC...

About Us

Formed in 2006, Tesla Motors Club (TMC) was the first independent online Tesla community. Today it remains the largest and most dynamic community of Tesla enthusiasts. Learn more.

Do you value your experience at TMC? Consider becoming a Supporting Member of Tesla Motors Club. As a thank you for your contribution, you'll get nearly no ads in the Community and Groups sections. Additional perks are available depending on the level of contribution. Please visit the Account Upgrades page for more details.


SUPPORT TMC
Top