There is a 'driver present' attribute exposed in Teslamate that I don't think appears in this app. It seems to be based on whether a phone key is in range.
I run both Teslamate (for monitoring) and this app (for control) since Teslamate updates in real-time whenever the car is awake rather than polling the car. Teslamate publishes everything to MQTT, and there is a Teslamate app for Hubitat that brings all that data into the Hubitat.
A few of the automations I run:
-
Tire rotation reminder: Using a hub variable to set the next reminder mileage, and a private boolean to only have the rule run once per week, send notification if mileage is above reminder mileage
-
Tire pressure warning: If any of the tires is below a certain PSI, send a notification
-
Turn on lights when car arrives home: When the geofence changes, if geofence = home, capture foyer lights, turn on foyer lights, wait 5 minutes and restore foyer lights. Teslamate allows for very easy setup of multiple geofences each with a settable radius. Since Teslamate is updating in real-time and I have the home geofence set to a pretty small radius, I can see the lights come on as I pass the same spot near my house every time.
-
Charge off peak: (currently disabled as I'm using another solution): If time is off peak (using a hub variable that gets set based on date and time) and car is plugged in and battery level is less than charge limit, start charging
-
End charging if on peak: Using the same hub variable as above, if the car is charging and the time changes to off peak, send command to stop charging.
-
Notify when not plugged in: If geofence = home and car is not plugged in and 30 minutes elapses, send notification
-
Set charge limit: Uses a hub variable that is settable from a Hubitat dashboard tile to set the max charge limit on the car. I find this more convenient than using the Tesla app.
-
I also have set up several commands using Google Assistant and a virtual switch... lock/unlock car, open trunk, open frunk, etc.