Your Tesla, Your History

Tesla 1.0.0 brings vehicle status and recorded driving history into mvmOS. Your installation talks directly to Tesla Fleet API and stores its collected history on your own server. See the vehicle and the journey • Inspect available battery, range, climate and vehicle sensor readings. • Review recorded trips with route points, distance, duration and estimated efficiency. • Explore charging sessions, named places, energy and estimated costs, together with battery health estimates and sleep history. • Group trips into journeys and use regional date and time controls to select their periods. Understand charging costs Named places can supply AC and DC prices. Time-based tariff rules and manual session totals refine reporting, with different currencies kept separate. When readings do not fall exactly on a tariff boundary, the split is marked as estimated. These local energy-cost calculations are separate from Tesla's own API charges. Collect without wake-up commands The scheduler uses different intervals while driving, charging, idle, parked or asleep. The app does not send wake-up commands. History begins when collection is configured; missing connectivity and polling gaps can leave incomplete routes or estimates. Keep control of sharing The owner can share with selected existing Apps Hub favourites. Viewers can read status and history; shared administrators can manage history and settings. Credentials, registration, reconnecting, disconnecting and further sharing stay with the owner. Unrelated and anonymous visitors do not gain access through the public catalogue or direct API requests, and revoked grants are checked against current permissions. Before connecting Tesla requires Core 1.17.0, an Apps Hub profile, your own compatible Tesla vehicle and Fleet API developer credentials, and a public HTTPS domain for the installation. Initial server setup requires desktop root access and creates a stable public verification key; setup installs the cryptography Python package if needed. Tesla API availability, permissions and charges apply separately. The desktop and phone or car-browser views belong to your mvmOS installation on a Linux server. Battery and efficiency figures depend on collected samples and are estimates, not diagnostic measurements.