Default geo-fences seem to small · Issue #833 · teslamate-org teslamate So if a charger was not correctly detected, the intended solution is to create a geo-fence yourself e g in your case "Tesla Rugtvedt Supercharger" (Or consider contributing to OSM :) -> https: www openstreetmap org node 7004520227#map=19 59 03748 9 67440)
TeslaMate Erfahrungs- und Datenthread - #1422 von Neo1 - Apps und Data . . . In den Charging Stats muss Supercharger im Adressnamen oder im Geofence-Namen stehen: (addr name ILIKE '%supercharger%' OR geo name ILIKE '%supercharger%') Und bei den TeslaMate Custom Dashboards Charging Costs Stats kommt noch der display_name dazu
[BETA] Tesla Vehicle via TeslaMate MQTT - Page 2 - Hubitat My workaround was to use Node Red to publish "none" as the geofence value when Teslamate reported the geofence as null image 1561×361 51 KB In the flow above the first MQTT node listens for the geofence value, the switch node only forwards messages where the geofence is null
Environment Variables - TeslaMate TeslaMate accepts the following environment variables for runtime configuration: Local path containing UNIX socket for database if that connection mechanic is preferred Provide one of DATABASE SOCKET_DIR and DATABASE (USER|PASS|HOST|PORT) Set to true if SSL should be enabled or noverify if certificate verification should not be performed
Supercharger place is not recognized · Issue #3217 · teslamate-org . . . I've recently charged at a Supercharger, but the place is not recognized by TM while being present in OSM Here is a copy of the map: Expected Behavior The place should be detected as "Zaventem Supercharger, Zaventem", but it's detected as "Weiveldlaan 29, Zaventem" Steps To Reproduce No response Relevant log output
Pull actual supercharging fees from account API · teslamate-org . . . Actual supercharger fees for a session can be pulled from the Tesla API by hitting https: www tesla com teslaaccount charging api history?vin=5YJ3XXXXXXXXXX It would be a cool feature to pull supercharging actual costs from the acct API after a charging session completes instead of relying on geofenced cost numbers
TeslaMate [megathread] | Page 58 | Tesla Motors Club You would enter this as 0 10828 in the Cost field for your Home Geofence, I do the same with my rate of £0 055 kWh However there looks to be a known issue with precision beyond 3 digits, there is an Issue for it on the Github already along with a workaround to tweak the Database for it You may want to comment here too if you're
Edit Geo-Fence Charge Cost not saving · teslamate-org teslamate . . . As workaround i update it manually in the DB via a query like UPDATE charging_processes SET cost=charge_energy_used*0 113 WHERE geofence_id='1' and start_date >= '2024-03-01 00:00:00' ; Is there a direct query to modify the charge rate for the geo-fence ID itself (11 in my case)? Thanks!