add back teslamate geofence tracker support

brchri · Dec 21, 2023 · 59131ca · 59131ca
1 parent d805ac7
commit 59131ca
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 7 deletions.
diff --git a/cmd/app/main.go b/cmd/app/main.go
@@ -271,6 +271,7 @@ func onMqttConnect(client mqtt.Client) {
 		possibleTopics := []string{
 			tracker.LatTopic,
 			tracker.LngTopic,
+			tracker.GeofenceTopic,
 			tracker.ComplexTopic.Topic,
 		}
 

diff --git a/examples/config.teslamate.mqtt.yml b/examples/config.teslamate.mqtt.yml
@@ -56,10 +56,4 @@ garage_doors:
             required_finish_state: closed
     trackers: # defines which trackers should be used to operate garage; list of trackers includes an arbitrary (but unique) id and topic definitions to retrieve latitude and longitude
       - id: 1 # required, some identifier, can be number or string
-        lat_topic: teslamate/cars/1/latitude # topic to retrieve latitude for tracker
-        lng_topic: teslamate/cars/1/longitude # topic to retrieve longitude for tracker
-      - id: 2 # required, some identifier, can be number or string
-        complex_topic: # if lat and lng are published to a single topic via json payload, use this instead of lat_topic and lng_topic
-          topic: some/complex/topic
-          lat_json_key: lat # json key for latitude; only top-level json keys are supported, cannot be nested within other json keys
-          lng_json_key: lng # json key for longitude; only top-level json keys are supported, cannot be nested within other json keys
+        geofence_topic: teslamate/cars/1/geofence