I was in the same position as well, but I went ahead and upgraded. No issue at all. The only difference I've noticed is the charge completion date/time is displayed on the Teslamate status page.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Delayed? Is your time zone set?
There should not be an issue upgrading. There was also no definitive ‘if you reboot, authentication fails’ stance. Dealing with an undocumented, non-supported API - we are literally building the product as we fly it.
MrFixit1094
Member
Thanks for clarifying....
There have been some who indicated they are jumping ship because of the fear that Tesla will do something to exterminate access to the unsupported, undocumented API. I remain optimistic that TeslaMate can continue to thrive, and this community can continue to adapt to whatever comes along. TeslaMate will not sink easily !!
After 4 years I think my Pi SD card is giving up and starting to corrupt the database. My backup last night failed with "pg_dump: error: Dumping the contents of table "charges" failed: PQgetResult() failed" and a load of block errors.
Luckily my last successful backup was only two days ago so restoring from it now, but heads up everyone with long running Raspberry Pi instances, check your backups are working.
I may now setup notifications too for failed back ups, its only by chance I noticed this.
Luckily my last successful backup was only two days ago so restoring from it now, but heads up everyone with long running Raspberry Pi instances, check your backups are working.
I may now setup notifications too for failed back ups, its only by chance I noticed this.
divstar
Member
Hello! I'm looking to host my Teslamate on a VM. Obviously the cheaper the better. Will this run on a 1vcpu 1gb RAM instance?
Docker install | TeslaMate
This document provides the necessary steps for installation of TeslaMate on a any system that runs Docker. For a walkthrough that provides the necessary steps for manual installation see Manual Install.
docs.teslamate.org
It should
garylovesbeer
Member
If you follow this guide you'll be sweet. I ran it on google for a while but the data exchange between Australia and the USA is not free and ended up costing a lot more than free. Started an Oracle VM on the Sydney location and has been running well. Good luck.
BTW I think the most important is creating the swap file.
How to setup and run TeslaMate for free on Google Cloud - TeslaEV.co.uk
A guide on how to install and run TeslaMate in GCP (Google Cloud) for free. Use the excellent TeslaMate data logger in the cloud for £0
www.teslaev.co.uk
What was in the logs? If your post is the same as GitHub did you try both TZ and TM_TZ? Was it only ISE during charging?
I posted this in Github and didn't get any replies, so wondering if the forum has any ideas? I just checked it now and it's sat spinning it's wheels and trying to pull the temp data.
From reading a few pages back I have no TIMEZONE set in my yml file, could that cause issues?
I've not managed to work out a set pattern as I don't check Teslamate that often, but when I do it appears to be missing multiple trips.
for example I'm missing all trips from the 26th Jan until the 6th Feb, then there is another gap until the 9th Feb, and then from the 10th Feb it's stopped recording trips again.
The car was definitely used on the 11th, 12th and 14th Feb but nothing is showing. If I click on the Overview page is missing lots of data, and the odometer, battery level are all incorrect?
I'm running via Docker on a Raspberry PI and on version 1.28.3.
The status says the car has been asleep for 3 d, 17 h and is showing it in the wrong location currently.
I'm seeing some errors around Finch in the logs?
From reading a few pages back I have no TIMEZONE set in my yml file, could that cause issues?
I've not managed to work out a set pattern as I don't check Teslamate that often, but when I do it appears to be missing multiple trips.
for example I'm missing all trips from the 26th Jan until the 6th Feb, then there is another gap until the 9th Feb, and then from the 10th Feb it's stopped recording trips again.
The car was definitely used on the 11th, 12th and 14th Feb but nothing is showing. If I click on the Overview page is missing lots of data, and the odometer, battery level are all incorrect?
I'm running via Docker on a Raspberry PI and on version 1.28.3.
The status says the car has been asleep for 3 d, 17 h and is showing it in the wrong location currently.
I'm seeing some errors around Finch in the logs?
teslamate-1 | ** (RuntimeError) Finch was unable to provide a connection within the timeout due to excess queuing for connections. Consider adjusting the pool size, count, timeout or reducing the rate of requests if it is possible that the downstream service is unable to keep up with the current rate.
teslamate-1 |
teslamate-1 | (nimble_pool 1.0.0) lib/nimble_pool.ex:402: NimblePool.exit!/3
teslamate-1 | (finch 0.16.0) lib/finch/http1/pool.ex:38: Finch.HTTP1.Pool.request/5
teslamate-1 | (finch 0.16.0) lib/finch.ex:324: anonymous fn/4 in Finch.request/3
teslamate-1 | (telemetry 1.2.1) /opt/app/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
teslamate-1 | (tesla 1.8.0) lib/tesla/adapter/finch.ex:63: Tesla.Adapter.Finch.call/2
teslamate-1 | (stdlib 5.2) timer.erl:312: :timer.tc/4
teslamate-1 | (tesla 1.8.0) lib/tesla/middleware/logger.ex:201: Tesla.Middleware.Logger.call/3
teslamate-1 | (tesla 1.8.0) lib/tesla/middleware/json.ex:57: Tesla.Middleware.JSON.call/3
teslamate-1 | Function: #Function<1.42154108/0 in TeslaMate.Vehicles.Vehicle.handle_event/4>
teslamate-1 | Args: []
teslamate-1 | 2024-02-10 00:04:34.253 [warning] MQTT Client has been terminated with reason: {:function_clause, [{TeslaMate.Mqtt.Handler, :connection, [:terminated, []], [file: ~c"lib/teslamate/mqtt/handler.ex", line: 7]}, {Tortoise.Handler, :execute, 2, [file: ~c"lib/tortoise/handler.ex", line: 340]}, {Tortoise.Connection.Controller, :handle_info, 2, [file: ~c"lib/tortoise/connection/controller.ex", line: 215]}, {:gen_server, :try_handle_info, 3, [file: ~c"gen_server.erl", line: 1095]}, {:gen_server, :handle_msg, 6, [file: ~c"gen_server.erl", line: 1183]}, {roc_lib, :init_p_do_apply, 3, [file: ~c"proc_lib.erl", line: 241]}]}
teslamate-1 | 2024-02-10 00:04:37.184 [error] GenServer {Tortoise.Registry, {Tortoise.Connection, "TESLAMATE_302E3536393"}} terminating
teslamate-1 | ** (stop)
teslamate-1 | Last message:
teslamate-1 | 2024-02-10 00:04:37.288 [error] GenServer {Tortoise.Registry, {Tortoise.Connection.Controller, "TESLAMATE_302E3536393"}} terminating
teslamate-1 | ** (FunctionClauseError) no function clause matching in TeslaMate.Mqtt.Handler.connection/2
teslamate-1 | (teslamate 1.28.3) lib/teslamate/mqtt/handler.ex:7: TeslaMate.Mqtt.Handler.connection
teslamate-1 | (tortoise 0.10.0) lib/tortoise/handler.ex:340: Tortoise.Handler.execute/2
teslamate-1 | (tortoise 0.10.0) lib/tortoise/connection/controller.ex:215: Tortoise.Connection.Controller.handle_info/2
teslamate-1 | (stdlib 5.2) gen_server.erl:1095: :gen_server.try_handle_info/3
teslamate-1 | (stdlib 5.2) gen_server.erl:1183: :gen_server.handle_msg/6
teslamate-1 | (stdlib 5.2) proc_lib.erl:241:
teslamate-1 | Last message: {{Tortoise, "TESLAMATE_302E3536393"}, :status, :terminated}
teslamate-1 | 2024-02-10 00:04:59.178 [error] GenServer {Tortoise.Registry, {Tortoise.Connection.Supervisor, "TESLAMATE_302E3536393"}} terminating
teslamate-1 | ** (stop)
teslamate-1 | Last message: {:EXIT, #PID<0.2686.0>,
teslamate-1 | 2024-02-10 00:05:44.068 car_id=1 [info] Start /
teslamate-1 | 2024-02-10 00:07:11.732 [error] Postgrex.Protocol (#PID<0.2432.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.205274.0> timed out because it queued and checked out the connection for longer than 60000ms
teslamate-1 |
teslamate-1 | #PID<0.205274.0> was at location:
teslamate-1 |
teslamate-1 | :erlang.atom_to_binary/1
teslamate-1 | (ecto_sql 3.10.2) lib/ecto/adapters/postgres/connection.ex:1369: Ecto.Adapters.Postgres.Connection.quote_name/1
teslamate-1 | (ecto_sql 3.10.2) lib/ecto/adapters/postgres/connection.ex:1410: Ecto.Adapters.Postgres.Connection.intersperse_map/4
teslamate-1 | (ecto_sql 3.10.2) lib/ecto/adapters/postgres/connection.ex:183: Ecto.Adapters.Postgres.Connection.insert/7
teslamate-1 | (ecto_sql 3.10.2) lib/ecto/adapters/postgres.ex:132: Ecto.Adapters.Postgres.insert/6
teslamate-1 | (ecto 3.10.3) lib/ecto/repo/schema.ex:764: Ecto.Repo.Schema.apply/4
teslamate-1 | (ecto 3.10.3) lib/ecto/repo/schema.ex:377: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
teslamate-1 | (teslamate 1.28.3) lib/teslamate/vehicles/vehicle.ex:729: anonymous fn/4 in TeslaMate.Vehicles.Vehicle.handle_event/4
teslamate-1 |
teslamate-1 | 2024-02-10 00:07:24.243 [error] GenStateMachine :"1" terminating
teslamate-1 | ** (DBConnection.ConnectionError) connection is closed because of an error, disconnect or timeout
teslamate-1 | (ecto_sql 3.10.2) lib/ecto/adapters/sql.ex:1047: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate-1 | (ecto 3.10.3) lib/ecto/repo/schema.ex:764: Ecto.Repo.Schema.apply/4
teslamate-1 | (ecto 3.10.3) lib/ecto/repo/schema.ex:377: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
teslamate-1 | (teslamate 1.28.3) lib/teslamate/vehicles/vehicle.ex:729: anonymous fn/4 in TeslaMate.Vehicles.Vehicle.handle_event/4
teslamate-1 | (ecto_sql 3.10.2) lib/ecto/adapters/sql.ex:1352: anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4
teslamate-1 | (db_connection 2.6.0) lib/db_connection.ex:1710: DBConnection.run_transaction/4
teslamate-1 | (teslamate 1.28.3) lib/teslamate/vehicles/vehicle.ex:721: TeslaMate.Vehicles.Vehicle.handle_event/4
teslamate-1 | (stdlib 5.2) gen_statem.erl:1397: :gen_statem.loop_state_callback/11
teslamate-1 | 2024-02-10 00:08:16.081 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:08:34.327 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:09:04.321 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:09:16.836 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/numbers -> error: "non-existing domain" (26272.888 ms)
teslamate-1 | 2024-02-10 00:09:20.812 [warning] TeslaApi.Error / non-existing domain
teslamate-1 | 2024-02-10 00:09:24.437 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-02-10 00:09:27.042 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:10:01.031 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:10:26.028 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:10:37.911 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:10:37.776 [error] GenServer TeslaMate.Mqtt.Publisher terminating
teslamate-1 | ** (WithClauseError) no with clause matching: {:error, :timeout}
teslamate-1 | (tortoise 0.10.0) lib/tortoise.ex:269: Tortoise.publish/4
teslamate-1 | (teslamate 1.28.3) lib/teslamate/mqtt/publisher.ex:41: TeslaMate.Mqtt.Publisher.handle_call/3
teslamate-1 | (stdlib 5.2) gen_server.erl:1131: :gen_server.try_handle_call/4
teslamate-1 | (stdlib 5.2) gen_server.erl:1160: :gen_server.handle_msg/6
teslamate-1 | (stdlib 5.2) proc_lib.erl:241:
teslamate-1 | Last message (from #PID<0.205289.0>): {
teslamate-1 | 2024-02-10 00:10:40.915 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:04.141 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:06.363 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:07.551 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:07.662 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:07.662 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:07.662 [warning] MQTT publishing failed: :timeout
teslamate-1 | 2024-02-10 00:11:16.237 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/numbers -> error: "non-existing domain" (55056.963 ms)
teslamate-1 | 2024-02-10 00:11:15.578 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:11:17.914 [warning] TeslaApi.Error / non-existing domain
teslamate-1 | 2024-02-10 00:11:19.861 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-02-10 00:11:52.660 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:12:05.284 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/numbers -> error: "non-existing domain" (11747.418 ms)
teslamate-1 | 2024-02-10 00:12:07.525 [warning] TeslaApi.Error / non-existing domain
teslamate-1 | 2024-02-10 00:12:08.199 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-02-10 00:12:19.640 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate-1 | 2024-02-10 00:12:43.587 [info] MQTT connection has been established
teslamate-1 | 2024-02-10 00:12:48.146 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/numbers -> error: "non-existing domain" (8258.504 ms)
teslamate-1 | 2024-02-10 00:12:48.206 [warning] TeslaApi.Error / non-existing domain
teslamate-1 | 2024-02-10 00:12:48.206 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-02-10 00:12:59.083 [notice] :alarm_handler: {:set, {TeslaMate.Vehicles.Vehicle_1_api_error, :fuse_blown}}
teslamate-1 | 2024-02-10 00:13:27.751 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/numbers -> error: "non-existing domain" (8419.050 ms)
teslamate-1 | 2024-02-10 00:13:28.785 [warning] TeslaApi.Error / non-existing domain
teslamate-1 | 2024-02-10 00:13:29.475 car_id=1 [error] Error / :unknown
teslamate-1 | 2024-02-10 00:14:04.495 car_id=1 [info] Start /
teslamate-1 | 2024-02-10 00:14:06.413 car_id=1 [info] Connecting ...
teslamate-1 | 2024-02-10 00:14:08.388 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (1564.239 ms)
teslamate-1 | 2024-02-10 00:14:09.920 car_id=1 [info] Charging / SOC: 39% / Home
teslamate-1 | 2024-02-10 00:14:10.066 car_id=1 [info] Disconnecting ...
teslamate-1 | 2024-02-10 00:14:10.162 car_id=1 [info] Received stream data: %TeslaApi.Stream.Data{time: ~U[2024-02-10 00:14:08.586Z], speed: nil, odometer: 26644.0, soc: 39, elevation: 156, est_heading: 26, est_lat: 53.852985, est_lng: -1.480397, power: -6, shift_state: nil, range: 123, est_range: 128, heading: 27}
teslamate-1 | 2024-02-10 00:19:59.207 [notice] :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_1_api_error}
teslamate-1 | 2024-02-10 00:50:32.595 car_id=1 [info] Derived efficiency factor: 149.10000000000002 Wh/km (27x confirmed)
teslamate-1 | 2024-02-10 00:50:32.595 car_id=1 [info] Charging / Stopped / 4.06 kWh – 36 min
teslamate-1 | 2024-02-10 00:50:32.600 car_id=1 [info] Start /
teslamate-1 | 2024-02-10 00:50:32.674 car_id=1 [info] Connecting ...
teslamate-1 | 2024-02-10 00:53:34.541 car_id=1 [info] Suspending logging
teslamate-1 | 2024-02-10 01:12:48.326 car_id=1 [info] Fetching vehicle state ...
teslamate-1 | 2024-02-10 01:12:48.649 car_id=1 [info] Start / :asleep
teslamate-1 | 2024-02-10 01:12:48.662 car_id=1 [info] Disconnecting ...
teslamate-1 | 2024-02-10 01:30:12.165 [info] Refreshing access token ...
teslamate-1 | 2024-02-10 01:30:12.785 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (610.488 ms)
teslamate-1 | 2024-02-10 01:30:12.799 [info] Scheduling token refresh in 6 h
1.28.3 needs a Timezone set. Fix that and then check again. Having a known issue makes it more difficult to diagnose any other issues.I posted this in Github and didn't get any replies, so wondering if the forum has any ideas? I just checked it now and it's sat spinning it's wheels and trying to pull the temp data.
From reading a few pages back I have no TIMEZONE set in my yml file, could that cause issues?
I've not managed to work out a set pattern as I don't check Teslamate that often, but when I do it appears to be missing multiple trips.
for example I'm missing all trips from the 26th Jan until the 6th Feb, then there is another gap until the 9th Feb, and then from the 10th Feb it's stopped recording trips again.
The car was definitely used on the 11th, 12th and 14th Feb but nothing is showing. If I click on the Overview page is missing lots of data, and the odometer, battery level are all incorrect?
I'm running via Docker on a Raspberry PI and on version 1.28.3.
The status says the car has been asleep for 3 d, 17 h and is showing it in the wrong location currently.
I'm seeing some errors around Finch in the logs?
Edit: also what do your DB logs look like?
Sounds more like your authentication to Tesla might have lapsed. Missing timezone would really just throw an error when charging, not prevent data from being collected. Did you change your Tesla account password anytime recently?I posted this in Github and didn't get any replies, so wondering if the forum has any ideas? I just checked it now and it's sat spinning it's wheels and trying to pull the temp data.
From reading a few pages back I have no TIMEZONE set in my yml file, could that cause issues?
I've not managed to work out a set pattern as I don't check Teslamate that often, but when I do it appears to be missing multiple trips.
for example I'm missing all trips from the 26th Jan until the 6th Feb, then there is another gap until the 9th Feb, and then from the 10th Feb it's stopped recording trips again.
The car was definitely used on the 11th, 12th and 14th Feb but nothing is showing. If I click on the Overview page is missing lots of data, and the odometer, battery level are all incorrect?
I'm running via Docker on a Raspberry PI and on version 1.28.3.
The status says the car has been asleep for 3 d, 17 h and is showing it in the wrong location currently.
I'm seeing some errors around Finch in the logs?
Similar threads
