You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
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
We could start a rumour that they're prepping for the UK launch of the Model Y
It's been like it for at least 6 months (when I got my P74D) - I raised a PR against TeslaLogger when I noticed the issue of P3D v LR on the degradation dashboard.
It could be a sign of the potential battery change coming though
Hi,Can't seem to post the code inline so here's a text file.
P74D started showing up for me a couple of days ago when I upgraded from 1.24.0 to 1.24.2.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?
DM me and we'll try to get it working.Hi,
I cant seem to get this to work. Followed the instructions above from init6. The panel gets names Gas Savings, but there is a read banner saying Panel plugin not found: undefined
not very familiar with what I am doing, so must be something I have missed.
I tried the instructions for russinating panel including the edits from init6 but that didnt work either. I got a syntax error
thanks
Vardhan
It was an update to the API that Tesla publish. Coincidental with the Teslamate update.P74D started showing up for me a couple of days ago when I upgraded from 1.24.0 to 1.24.2.
It's been in the API for at least 6 months (when I got mine)It was an update to the API that Tesla publish. Coincidental with the Teslamate update.
Yep, looks like it. The API now returns trim_badging: "p74d" in case of the Model 3, for example. |
Where I raised the issue against teslalogger on 27/marI'm just going with what the guy who wrote Teslamate says
adriankumpf commented 3 days ago
Yep, looks like it. The API now returns trim_badging: "p74d" in case of the Model 3, for example.
What's GCS? Same as GCP?I've been trying to set up teslamate on GCS, but am having issues creating the .htpasswd file. I keep getting an error say .htpasswd is a directory, any ideas?
That will almost certainly be restrictions/permissions on the server sideI've been trying to set up teslamate on GCS, but am having issues creating the .htpasswd file. I keep getting an error say .htpasswd is a directory, any ideas?
you likely just fluffed the syntax somewhere - if you can post a little more content around the commands you're using we can probably help.I've been trying to set up teslamate on GCS, but am having issues creating the .htpasswd file. I keep getting an error say .htpasswd is a directory, any ideas?
agreed, or host at home behind a proper firewall (maybe on a pi or something) reachable only from internal networkyou likely just fluffed the syntax somewhere - if you can post a little more content around the commands you're using we can probably help.
However.... call me paranoid if you like, but I do find it quite alarming that people are happy to put something that knows your home address, movement habits, real-time location of your car and holds the token that has the ability to remotely unlock and start your car.. on the public internet with just single factor http basic auth and no rate limiting/brute-force protection etc to protect it (i.e. something that a 12 year old with an afternoon or two to spare can likely defeat). Sure, pin to drive will stop it being driven away, but still....
I would strongly advise at least looking into something a little more robust like cloudflare access/argo tunnel, zerotier etc to better protect it and not expose it all to the world.
Thanks for the advice, i have already setup on my NAS but was wanting to try out a method so could access anywhere.agreed, or host at home behind a proper firewall (maybe on a pi or something) reachable only from internal network