Search results

Update 2 : unfortunately, because of the message that I had to update my docker-compose.yml file and it came with a link which I followed, I lost all entries in my database :-( Of course I didn't make a backup first, so I have to start all over again....

Update : changed my f1 micro server to E2 micro server on GCP, and problems are gone. The server upgrade wouldn't fix it, but the restart of the server probably did. (weird that this forum doesn't have an EDIT button to edit my own post with the update).

I seem to have the same issue since a couple of days. My car status was showing OFFLINE, when I know it was online for sure. When I connected to TeslaLogger website, it showed me the message that the docker-compose.yml file needed to be updated. So I did just that. After update, the message on...

I received that email too, but didn't came to it up check it out. So is it a little better than the F1 micro server ? Only in RAM or also in CPU ?

Found it, thank you !

Hi @bassmaster, I only have 1 geofence, which is "home". But I can only charge at public charging stations, I don't have a charging station at home. So for my needs, I need to be able to set multiple geofences. All by location. Is that possible as well ?

Does anyone know how I can set a price for a charging station, so that TeslaLogger automatically fills the correct cost per session on that specific charging station ? Now I have to manually enter the cost per kWh for each session and that it a lot of manual work.

I think I have found the cause.... Besides a VM for TeslaMate, I also created a second VM for TeslaLogger to test that. However, that never worked and so I stopped the VM. When I check "Disks" in GCP, I saw that my TeslaLogger VM was using a "Balanced PD capacity" disk and that was exactly...

Up until recently I wasn't charged of anything as well. Only when my free trial was up and I had to upgrade my billing account, it started to charge costs. I have a normal micro-f1 server, exactly set up according to that manual you posted, with a standard disk that is.

Question to the ones using Teslamate on GCP micro-f1 server : My free trial period expired and to make Teslamate work again I had to switch to a paid account, which I did as I thought that the micro-f1 server was free. It turns out not to be free, I am being charged for some costs. Not that it...

That specific session I added 39,37 kWh according to Teslamate. I'm driving a model 3 SR+, which has a 50 kWh battery according to the specs. So when I added 39,37 kWh and that is to 90%, If that is 85% added, 100% will be 46,32 kWh. If that is 78% added, 100% will be 50,47 kWh I'm more...

I'm on the latest version, 1.22.0 So that fix I should already have, but maybe this fix causes this difference in reporting. My first drive reported in TeslaMate was on the 11th of February, version 1.12.3 was then the latest one. That strange "bump" in range I see that on several sessions...

Sure, this session is from today. Car showed 5% battery when starting to charge. TeslaMate shows 12%. Cold battery is possible, only drove about 300 meters to the public charging station.

Yes, the time is correctly logged in TeslaMate. P.S. I also have TeslaLogger running on the same GCP micro F1 server and it is off as well.

Works like a charm @bassmaster

Hi guys, I have been using TeslaMate in GCP since February and I just noticed something. I don't have my own charger at home, so I have to rely on public charges and about 300 meters from my home is a public charger. When I start charging, I always get notified by the Tesla app. It also says...

Actually I'm quite the n00b when it comes to Linux and docker containers. To set up TeslaMate, I just simply followed this guide : How to setup and run TeslaMate for free on Google Cloud - TeslaEV.co.uk Luckily this guide also explains how to set up a 1 GB swap file.

Hi @bassmaster , I now have both TeslaMate and TeslaLogger running on 1 GCP micro f1 server and both are working great (thanks to your fix). Of course I want to make comparisons between the two and honestly TeslaLogger looks more appealing. However there is 1 major disadvantage of TeslaLogger...

you HERO !! It finally works ! Thank you so much Christian !

Thanks a lot for testing this issue Christian, we really appreciate it. Thank god I'm not stupid :cool: I'm quite sure it is not a block on Google cloud, because I also have TeslaMate running on another micro f1 server (same set-up as the one with TeslaLogger) and TeslaMate runs very well...

I don't use MFA, maybe that is the problem...

Good to know that I'm not the only one. I was starting to doubt myself. This is the exact error I am getting too. And I know for sure that I'm using the correct credentials, I have TeslaMate in another GCP micro f1 server working perfectly. I have sent @bassmaster already my log file, hope he...

I have sent you a PM with the logfile. Thanks for checking out the problem @bassmaster

I still face 3 problems : 1. My car isn't recognized. I do not have 2FA/MFA enabled on my account. Credentials are correct in TeslaLogger.exe.config (checked by logging in my account manually). I still get this error : shm 65536 4 65532 1% /dev/shm tmpfs 303336 0 303336 0% /proc/acpi tmpfs...

Yes, I'm running Debian 9 64bit on the GCP micro-f1 server

Nearly there, just need to overcome some issues. In the log an error appears : 05.03.2021 14:44:01 : Exec_mono: rm -rf /etc/teslalogger/tmp/* 05.03.2021 14:44:01 : Exec_mono: rm -rf /etc/teslalogger/tmp 05.03.2021 14:44:02 : Exec_mono: mkdir /etc/teslalogger/tmp 05.03.2021 14:44:03 ...

EDIT : Ok, that error appeared apparently because I was too quick connecting, before TeslaLogger was finished creating the database. When I waited a couple of minutes that error was gone. However, my car is not seen even if I entered the information correctly in the TeslaLogger.exe.config file...

Well, I have the micro-f1 server up and running on GCP. DNS is configured and working. Firewall ports 3000 and 8888 are opened. Installed docker and docker-compose latest versions I can connect to my server via web browser (over the internet, no VPN) to http://my domain:8888/admin But when I go...

I'm using the free instance of GCP indeed and for TeslaMate it runs well. I even have a free domain name registered to use. Have someone installed TeslaLogger in the cloud and want to share their instructions with me ?

Hi bassmaster, I have Teslamate running in a Google Cloud VM (micro F1 server with Debian 9 and docker). Do you know if it would be possible, like Teslamate, to run in also in the Google Cloud ?