Merge branch 'master' into TeslaFleetAPI

.github/workflows/dotnet-desktop.yml

@@ -1,6 +1,7 @@
 name: .NET Core Desktop
 
 on:
+  workflow_dispatch:
   push:
     branches: [ "master","TeslaFleetAPI"]
   pull_request:

TeslaLogger/bin/changelog.md

@@ -1,3 +1,6 @@
+# Version 1.56.1
+- Update certificates for Mono
+
 # Version 1.56.0
 - Support new Tesla API
 - Attention: MapQuest isn't free anymore! Either you remove the key in your settings, if you used it or you have to provide a credit card to MapQuest. 

TeslaLogger/bin/geofence.csv

@@ -6892,6 +6892,7 @@ Kaufland RO-Voluntari,44.489141,26.189812,10
 Ladenetz DE-Wuppertal - Botanischer Garten, 51.261180, 7.162568, 10
 Ladenetz DE-Wuppertal - Rathaus Barmen, 51.272575, 7.198940, 10
 Ladenetz DE-Wuppertal - WSW-Zentrale, 51.279178, 7.187185, 10
+Ladenetz DE-Wuppertal - Hauptbahnhof, 51.255269, 7.151023, 15
 
 Ladeverbund+ DE-Bad Mergentheim Bahnhof, 49.493046,9.769979
 Ladeverbund+ DE-Bad Mergentheim Oskar-Weitbrecht-Weg, 49.486658,9.790112

docker_setup.md

@@ -1,5 +1,5 @@
 # Docker Setup
-For Synology NAS users, check the hints here: [LINK](docker_setup_synology.md) 
+For Synology NAS users, check the hints here: [LINK DSM 6](docker_setup_synology.md) / [LINK DSM 7](docker_setup_synology_7.md) 
 
 Docker on Raspberry: It won't work if you don't have a 64bit OS as MariaDB requires a 64bit OS!
 

docker_setup_synology.md

@@ -1,4 +1,4 @@
-# Teslalogger Docker Setup on Synology NAS
+# Teslalogger Docker Setup on Synology NAS - DSM 6
 
 ![Image](https://raw.githubusercontent.com/bassmaster187/TeslaLogger/master/TeslaLogger/screenshots/docker-synology.PNG)
 

docker_setup_synology_7.md

@@ -0,0 +1,62 @@
+# Teslalogger Docker Setup on Synology NAS - DSM 7
+
+Installation instructions for Synology NAS on DSM 7.2-64570 Update 1
+
+I've had a hard time to get this to work, which in the end had mostly todo with ACLs as this is mostly hidden in an SSH session. But in the end I got it to work. I hope this helps someone else who wants to install this on DSM 7+. I wish I could set it up a bit more secure, as I've given read/write permissions to everyone, but with mixed host/containerized UIDs/GIDs it's very hard to tie it down. So, massive disclaimer that this is not the most secure method, but it works.
+
+Open an SSH session to your Synology NAS and execute the following commands (assumes you already have Container Manager installed and use /volume1, please amend if different):
+
+```
+sudo -i
+cd /volume1/docker
+git clone https://github.com/bassmaster187/TeslaLogger
+cd TeslaLogger/TeslaLogger
+mkdir GrafanaDashboards && mkdir GrafanaDB
+```
+
+Because DSM uses ACLs, the file permissions are a bit more complicated than the standard Linux permissions. The easiest way to make the changes is by using File Station in the Synology Web Portal.
+- Open File Station
+- Browse to /volume1/docker/TeslaLogger
+- Inside this directory, right click on the second TeslaLogger directory and select Properties from the menu
+
+![image](./TeslaLogger/screenshots/DMS7-01-file-station-select-properties.png)
+
+- In the Properties popup, select the Permissions tab
+- Click on the Create button to open the Permissions Editor
+
+![image](./TeslaLogger/screenshots/DMS7-02-properties-create-button.png)
+
+- In the User or Group dropdown, select Everyone
+- In the Permission area, tick the Read and the Write tickbox (all sub items will be ticked)
+- Click the Done button
+
+![image](./TeslaLogger/screenshots/DMS7-03-permissions-editor.png)
+
+- Back on the Properties popup, click on the Save button
+
+Close File Station and open Container Manager
+
+- Select the Project side tab and click the Create button
+
+![image](./TeslaLogger/screenshots/DMS7-04-container-manager.png)
+
+On the Create Project wizard:
+- give your project a name, e.i: teslalogger
+- Select the path: /volume1/docker/TeslaLogger
+- It will detect this already has a docker-compose.yml file, so select to use the existing one and press ok
+
+![image](./TeslaLogger/screenshots/DMS7-05-use-existing-compose.png)
+
+- Optionally change the TZ= timezones (4 instances)
+- Press Next
+- Press Next again
+- Press Done
+
+The containers will boot up. You'll see that the database container will use a bit more resources for a while. It only does that at first boot and the other containers won't boot properly until this is finished. Give it a little time until the CPU for all containers are low. If you have any first time start-up issues, then go into the Action dropdown and select Restart.
+
+![image](./TeslaLogger/screenshots/DMS7-06-containers-boot.png)
+
+These are the URLs you can use, replace "host" with your own NASs hostname:
+
+- Admin: http://host:8888/admin/
+- Grafana: http://ds:3000/

docs/en/faq.md

@@ -65,3 +65,15 @@ Mac User can use the terminal
 Host: raspberry or raspberry.local
 Name: pi
 Password: teslalogger
+
+# Fleet API
+## Commands to car are not working (e.g. turn on sentry mode)
+If you see such errors in your logfile, you forgot to grant access to your car.
+```
+{„response“:null,„error“:„vehicle rejected request: your public key has not been paired with the vehicle“,„error_description“:„“}
+```
+Go to : https://www.tesla.com/_ak/teslalogger.de and follow the instructions
+
+## Error in logfile: Tesla Vehicle Command Protocol required
+You have to migrate to the new official Tesla Fleet protocol.
+> {"response":null,"error":"Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning","error_description":""}