My T Companion 1.10.7

My T Companion 1.10.7

• Record navigation session start place (start_name) from live geofence or open-drive start geofence/address so My T can show start → destination on destination trips.

My T Companion 1.10.6

My T Companion 1.10.6

• When the car changes navigation destination mid-drive, close the previous session with end_reason: redirected and open a new session for the new destination.
• App destination-trip list can show start/end as a closed loop and treat detours as a separate trip.

My T Companion 1.10.5

My T Companion 1.10.5

• Fix a mutex deadlock that blocked GET /api/v1/cars/{id}/navigation/push-history after the first navigation push delivery.
• Navigation push history is readable again from My T Settings.

My T Companion 1.10.4

My T Companion 1.10.4

• Records navigation push sessions (destination, distance, duration) for App history via GET /api/v1/cars/{id}/navigation/push-history.
• Capability: navigation_push_history.
• Navigation end events include real trip timing: trip_started_at, trip_ended_at, duration_minutes, and driven distance for authentic Live Activity end frames.
• Continues to use only https://push.my-tesla.app/v1/events as the trusted push relay.
• Includes 1.10.3 history API and 1.10.2 domain/unpair hardening.

My T Companion 1.10.2

My T Companion 1.10.2

• Adds App compatibility metadata to the authenticated capabilities response.
• Lets My T distinguish recommended App updates from minimum required versions.
• Uses push.my-tesla.app as the only trusted push relay endpoint.
• Keeps all existing TeslaMate, parking, charging, and navigation behavior unchanged.

My T Companion 1.10.1

My T Companion 1.10.1

This reliability release improves destination-navigation Live Activities.

• Navigation can start from genuine driving state and destination data before
  optional distance or ETA values become available.
• Active sessions survive a Companion restart long enough to reconcile with
  fresh TeslaMate MQTT state. An unconfirmed restored session emits a real end
  event instead of being silently discarded and leaving the Lock Screen stuck.
• Navigation end events use an independent delivery worker and are no longer
  delayed behind retries for ordinary updates.
• New regression tests cover early start and terminal-event priority.

No coordinates, routes, credentials, VIN, or driving history are added to push
payloads. The release remains backward compatible with normal TeslaMate use.

Update an installer-managed deployment with:

sudo /opt/my-t-companion/update.sh

My T Companion 1.10.0

My T Companion 1.10.0

• Parking plug, charging, security and climate observations now default to
  long-term retention instead of 365 days.
• A 50,000-event capacity guard preserves the newest genuine observations and
  prevents unbounded storage growth.
• Temporary navigation, charging and push-deduplication state now has explicit
  age and count limits.
• New backup, restore and storage-status commands support safe VPS migration.
• TeslaMate PostgreSQL remains read-only and is never pruned by Companion.

This release is backward compatible with My T. Updating is recommended, not
required for ordinary TeslaMate features.

My T Companion 1.9.3

My T Companion 1.9.3

This maintenance release fixes repeated App pairing and adds deployment
resource safeguards.

MQTT stability

• Replaying the same valid pairing no longer creates duplicate software,
  charging, or navigation MQTT clients.
• A genuinely changed pairing cleanly disconnects the old client before the
  replacement starts.
• Charging and navigation keep one delivery worker for the lifetime of the
  process.
• A regression test replays the same pairing three times across all push
  monitors.

Deployment safeguards

• The container is limited to 1 CPU, 256 MB memory, and 128 processes.
• Docker JSON logs rotate at 10 MB and retain three files.
• Existing pairing, notification, parking-event, and Live Activity state remain
  in the persistent Companion data volume during upgrades.

My T Companion 1.9.2

My T Companion 1.9.2

This patch release fixes the Caddy route migration in 1.9.1.

Fix

• Creates the temporary Caddy route file before writing the new
  /api/v1/cars/{id}/parking-events route.
• Adds a regression test for the upgrade-specific initialization order.
• Retains updater rollback protection if a build, health check, proxy
  validation, or reload fails.

Version 1.9.2 includes all genuine future parking-event features from 1.9.0 and
the complete installer source-copy fix from 1.9.1. Users should install 1.9.2.

My T Companion 1.9.1 (superseded)

Superseded by v1.9.2. Do not install v1.9.1: its Caddy upgrade path writes the new parking-event route before creating the temporary route file, so the updater rolls back. Use v1.9.2.