Search results

I managed to get 10.0.1 working the problem are raspberries from the first day. Grafana needs a new glibc and the only stable way is to upgrade to a new debian.

If you run it on docker, you can overwrite the version. For Raspberry, you need to update it. Unfortunately Grafana is notorious for breaking changes and new bugs, so let me please check if everything works fine with the newest Version. After that you can update your docker file and everything...

As far as I can see, the cells are CATL NMC 6,9Ah with 50C. So 345A should be ok. https://german.alibaba.com/product-detail/Hige-rate-50C-CATL-Li-NMC-1600396466241.html

I've got here a 16V battery out of a Model Y with a dead BMS. I was able to get 60A from the battery - maybe more, but my test equipment was limited to 60A.

Why don't you use the wires comming from the Battery?

Hi, Sorry I had some day offs and was out of town. basically it should import everything from teslafi - do you have a logfile? I don't know what installation you have, but if you run teslalogger inside a docker container, you have to copy in subfolder: \TeslaLogger\www\admin\wallpapers\1

Please PM me your Logfile.

Did you try to update to newest Teslalogger Version? Could you please PM me your logfile?

Teslalogger has an interface to ScanMyTesla and a bunch of statistics against all Teslalogger Users. e.g : You can compare your degradation against all other cars. Thats my car for instance: My Degradation

Do you already have some data recorded? Could you please PM me a logfile from Admin Panel.

I think from Tesla side there is no solution for pre 2017 cars with MCU2 upgrade: 12v battery is now charging 24 hours / day I read about somebody tried to install a higher capacity 12V battery to keep the recharge cycles to a minimum, but I didn't see a proof it will working. In theory it...

The top priority of teslalogger is to make sure your car can sleep as there is no Teslalogger at all. This is how it should look like: If you have MCU1 make sure you have these settings: - 'Energy Savings' is enabled on your vehicle - 'Always Connected' is OFF on your vehicle - Cabin...

please try to make a manually update. It should repair all dashboards if something went wrong.

Sorry guys for the late response, I have been on a long trip (3250mls / 5200km) to the Black Sea / Romania. It was very nice. Authentification Problems As many have seen, Tesla has changed the authentification process the last few days, so we had problems inserting new cars to Teslalogger...

We are actually about to integrate wallbox meter and solar meter. So you can exactly see, what you really have to pay for the charging and not what Tesla claims. And how much you used solar for charging. In Germany / Austria and Switzerland we have following popular Wallboxes with built in...

It's pretty much the same. If Google or their employee might have access to your private cloud, they just have your Tesla Token and can open the car, but not start / drive it.

yes, it is possible. name all your public carging stations you frequently use and set "copy charging costs".

Go to Admin Panel. Menu / Extras / Geofence. Edit the geofence your charger is located. Enable "Copy Charging Costs"

There is actually an English manual in progress, but not ready. Could you please name the dashboard with not translated words and metric system.

Please update to the latest version and check if it works now. Maybe you have to enter your credentials once again.

you have to wait a couple of days as tesla changed the authentification process. So all loggers are not able to authentificate since last Friday. We have to figure out a workaround for the captcha issue.

If your dockerfile is as mentioned in the docs and the teslalogger container starts up without errors, everything should run great. make sure you have enough virtual memory on google cloud, if you choose the free one. Double check you wait long enough on the first startup, as the google cloud...

Yes.

Update Admin Panel can now be proteced by password. Check menu/settings/Teslalogger Adminpanel credentials If you running on Docker. Make supre you update the dockerfile: bassmaster187/TeslaLogger

Could you please PM me your link

Here we go:

It doesn't need tasker anymore. We also use streaming API as long as it will work. The sleep settings are if you want to make sure the api will not polled during night hours. There are some S 85 with downgraded firmware to 2019.12.1.1 out there with sleep problems - not all. As long as your car...

I feel your pain as I own a 1964 Chevy Impala and all tools I've got are metric. So with every bolt I have to calculate from metric to inch... I'll make sure you can change your units in all statistics.

Could you please check that issue with the new update

I'll check it tomorrow if there may be something wrong.

Yesterday Abetterrouteplanner has been hacked. That's why Teslalogger is perfect: you don't need to share your credentials with a 3rd party service. https://forum.abetterrouteplanner.com/blogs/entry/37-test-data-leak-from-abrp-server/

Your abrp account has been reseted. So now it should work.

It seems like it is a problem on ABRP side, so I'll ask them what we can do.

Do you have a screenshot?

Teslalogger is now officially supported by Abetterrouteplanner

These are just warning there are some not translated keys. But the Abetterroutplanner feature is working and sending data to ABRP?

Update: Teslalogger can now send data to Abetterrouteplanner. Abetterrouteplanner is an awesome tool to calculate routes but also to track in real time, in the car if you still make it to the destinations. It takes into account intermediate destinations, foreign charging stations, desired SOC at...

Thanks, I'm gonna check this

Update we made a couple of updates to the dashboard: "Timeline Plugin". It is now translated, use your prefered units, maps will be rendered even without MapQuest key. There are links to other dashboards. Try it out and let me know if you like it and what are you missing.

It seems like mono has a memory leak with HttpHandler in last Teslalogger version and we found a workaround. Make sure you update Teslalogger to the latest version. If you still have problems, let me know.

Is anything strange in /var/Log/messages ? oom reaper for instance...

install latest mono and it should work.

We could add some sort of proxy in docker-compose to achieve this. I think you can do it by yourself if you create a .htpasswd file in apaches webfolder. For encryption you might do the same as you did for TeslaMate. BTW: make sure you add like 1 GB of virtual RAM to your Google micro server. I...

Please update your Teslalogger.

It seems like some connections are routed to a different load balancer and this one is blocking several user-agents... please update to the latest teslalogger and give it another try.

I can confirm either google cloud is blocked by tesla or there is another problem in authentification process. My account works on different docker and raspberries perfect, but on google cloud not with the same timeout error you guys have. If I use a token from my raspberry on google cloud...

I tried a fresh reinstall and it seams like it works. 18.03.2021 10:29:43 : #1: GetAvgConsumption: nothing found!!! 18.03.2021 10:29:43 : #1: No Refresh Token 18.03.2021 10:29:43 : #1: Login with : 'XhrXsXXanXXoXeaXaiX.XX' / 'xxxxxxxxxxx' 18.03.2021 10:29:44 : #1: Start waiting for MFA code...

I think you didn't wait to build / update the whole database long enougt. Please go to admin panel / settings / credentials. Is there your car listet? if not, please add a new car. Otherwise please send me your whole logfile.

I tied the micro F1 Server of Google Cloud Platform and it works well. I used Debian 10 as a boot disk. installed docker and docker-compose open port 3000 and 8888 in google cloud platform firewall and follow the Teslalogger Docker Setup: bassmaster187/TeslaLogger I did not make any...