What will be interesting is if development of TeslaMate continues. The benefit of TeslaMate is self-hosted, self-ownership of your data, tokens, etc. SaaS TeslaMate goes in the face of those "benefits".
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
DeltaOne
Member
When I look back at Drive history, in Tessie, I do see some Home to Home drives. But the vast majority of drives look correct.
Also, on nice days, it's not unusual for me to take the Model 3 on a 30, 60 or 90 minute drive...that was Home to Home. So I have no way of telling for sure if there are any errors in my Drive history. Based on what you say, there may be. I'm okay with that since the vast majority of the data looks correct.
I registered a new company but only got as far as estimating setup costs.We won a new contract in the other company so the dev team was too busy to take on the work.
I see a couple of other companies ran with that idea anyway so I closed the new company down.
I think there are other benefits to TeslaMate given the alternatives (e.g. TeslaFi or TeslaScope).
Also SaaS doesn't mean the data belongs to the hosting entity. I assume the TeslaMate data I have accumulating at Linode/Cloudflare is still mine because they don't have a policy that says all locally generated work product is theirs.
Finally if you want ongoing development it has to be worth someone's time. I don't know why Adrian decided to put down TeslaMate but having to fight Tesla can't be very encouraging.
Months ago. Thankfully some good folks on here and elsewhere have been holding the fort, but I suspect the Fleet API may be a bridge too far.
Hmmm, I think it was after the location bug (triggered by 2023.38) was fixed which was mid-October.
Teslamate go forward · teslamate-org/teslamate · Discussion #3416
Hello everyone! As we know @adriankumpf is ceasing development of this fantastic app going forward. With that said, we need to determine who if anyone can take more responsibility for this project ...
github.com
I successfully updated an instance to 1.28.3. I'm getting updated web pages but logging is suspended and the 1.28.3 instance reports that the vehicle was offline for 12 minutes but online now. I'm still thinking about spinning up fresh instance to see if that still works.
What API issue? If Teslamate seems to be working okay for me now, is there any reason to update?
I think it will continue working until you restart it. Then it will fail. (The API that was deprecated is used on startup.)
If you restart TeslaMate (or its container if you use one) or the system it's running on it may not restart without the update. This update doesn't use the new Fleet API but the start-up has changed. This is similar to the last Tesla-side update that broke TeslaMate.
If it's not an issue (for you) if TeslaMate stops working then you don't need to worry or do anything. If you want on-going vehicle monitoring for the indefinite future you should be considering alternatives to TeslaMate. We can all hope that the devs can keep it working but realistically it could stop at any time unless the user community can migrate to the new API.
The current version is 1.28.3 and the previous was 1.28.2. You can certainly go back to an earlier version but recent updates have been critical.
You can see the version number on the settings page.
E.g.:
Version | 1.28.3 |
|---|---|
GitHub | teslamate-org/teslamate |
Documentation | docs.teslamate.org |
I am indeed on 1.28.3 after it updated. These are errors I found in logs:
Code:
2024-02-03 21:41:26.626 [info] Starting logger for 'Chunky'
2024-02-03 21:41:26.715 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (79.612 ms)
2024-02-03 21:41:26.715 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:41:26.738 car_id=2 [info] Start / :offline
2024-02-03 21:41:56.811 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (93.778 ms)
2024-02-03 21:41:56.811 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:42:26.897 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (83.414 ms)
2024-02-03 21:42:26.898 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:42:56.999 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (98.403 ms)
2024-02-03 21:42:57.000 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:43:27.125 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (122.429 ms)
2024-02-03 21:43:27.126 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:43:57.233 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (104.523 ms)
2024-02-03 21:43:57.234 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:44:27.332 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (94.969 ms)
2024-02-03 21:44:27.332 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:44:57.419 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (83.897 ms)
2024-02-03 21:44:57.419 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:45:27.509 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/VEHICLE_ID_HERE-> 404 (86.960 ms)
2024-02-03 21:45:27.509 car_id=1 [error] Error / :vehicle_not_found
2024-02-03 21:45:27.510 [warning] Restarting Elixir.TeslaMate.Vehicles supervisor
2024-02-03 21:45:27.586 [info] GET https://owner-api.teslamotors.com/api/1/vehicles -> 412 (73.619 ms)
2024-02-03 21:45:27.587 [warning] TeslaApi.Error / %{"error" => "Endpoint is only available on fleetapi. Visit https://developer.tesla.com/docs for more info", "error_description" => "", "response" => nil}
2024-02-03 21:45:27.587 [warning] Could not get vehicles: :unknown
2024-02-03 21:45:27.591 [warning] Using fallback vehicles:
<< blurb on TeslaAPI call>>Looks like the original problem where vehicles and not products is being used as the API request. I’d suggest you’re. It running the right version of Teslamate
As noted you can see the version in the Settings page (see my paste above) or a few lines earlier in the log you should see:
Attaching to teslamate_teslamate_1
teslamate_1 | 2024-02-02 19:14:26.099 [info] Migrations already up
teslamate_1 | 2024-02-02 19:14:30.561 [info] System Info: Erlang/OTP 26 (jit)
teslamate_1 | 2024-02-02 19:14:30.561 [info] Version: 1.28.3
See this issue:
Endpoint is only available on fleetapi · Issue #3629 · teslamate-org/teslamate
Is there an existing issue for this? I have searched the existing issues What happened? I followed the docker instructions, and everything starts fine, but I'm just seeing a blank page on the home ...
github.com
Last edited:
Ahh... I misread, the update available of 1.28.3 I read as the current version. All issues resolved after updating.As noted you can see the version in the Settings page (see my paste above) or a few lines earlier in the log you should see:
Attaching to teslamate_teslamate_1teslamate_1 | 2024-02-02 19:14:26.099 [info] Migrations already upteslamate_1 | 2024-02-02 19:14:30.561 [info] System Info: Erlang/OTP 26 (jit)teslamate_1 | 2024-02-02 19:14:30.561 [info] Version: 1.28.3
See this issue:
Endpoint is only available on fleetapi · Issue #3629 · teslamate-org/teslamate
Is there an existing issue for this? I have searched the existing issues What happened? I followed the docker instructions, and everything starts fine, but I'm just seeing a blank page on the home ...
Similar threads
