Welcome to Teslemetry 3.0

If you've been following along, you'll know this has been a long time coming. Back in Website 2.5 I talked about the enormous scope of the website rewrite I'd been working on, and how I made the decision to ship incremental improvements instead of waiting for perfection. In the 2025 Wrapped post I set the goal of finishing this work in 2026. Well, here we are — welcome to Teslemetry 3.0.

Built from the ground up

This isn't a facelift. The entire website has been rebuilt on Nuxt 4 and Nuxt UI 4, giving Teslemetry a modern foundation to build on for years to come. Every page has been redesigned with a focus on clarity and usability, whether you're managing your vehicles, monitoring your energy site, or configuring your integrations.

The new design language is cleaner and more consistent, with better use of space, improved navigation, and a layout that still works just as well on your phone as it does on your desktop.

Server-side rendering is more efficient, client-side navigation is snappier, and the overall experience should feel noticeably faster. Combined with the backend migration off Firebase that we completed with Website 2.5, the entire stack is now leaner and more capable.

Dramatically more reliable commands

If you've ever sent a command to your vehicle and received an error — only to have it work fine on the second try — you'll appreciate this one. The Teslemetry backend now has an intelligent retry system that handles the most common causes of transient failures automatically.

When your vehicle is waking up, the system now waits patiently and retries rather than failing immediately. When Tesla's servers are rate limiting or experiencing issues, Teslemetry respects their backoff signals and retries on your behalf. Signed commands that arrive during a wake transition are retried with increasing delays instead of being rejected outright. The system also handles a wider range of temporary faults from the vehicle itself — busy states, clock synchronisation issues, and internal errors are all now recoverable.

The net result is that commands from Home Assistant, automations, and the console are significantly more likely to succeed on the first attempt, especially for vehicles that are asleep or in transitional states.

On a related note, when multiple sources send commands to the same vehicle simultaneously — say your Home Assistant automation and a manual command from the app at the same time — those requests are now queued rather than racing against each other. This prevents conflicts and ensures commands are processed in order.

Webhook health monitoring

Previously, if your webhook endpoint went down, you might not notice the data gaps for days or even weeks. Teslemetry now monitors webhook health daily. If your webhook hasn't had a successful delivery in 7 days, you'll receive an email notification explaining the issue and how to reconfigure it. Abandoned webhooks are automatically cleaned up to keep things running smoothly.

For Tint customers, if your connected vehicle hasn't sent data in 7 days, you'll receive a targeted notification with troubleshooting steps to help you meet your obligations.

Celebrating the launch with lower prices

To mark the launch of Teslemetry 3.0, quarterly and annual vehicle subscriptions have had a price reduction — they now match the base Teslemetry subscription which are cheaper on longer subscriptions. If you've been paying month-to-month, now is a great time to switch to a longer billing cycle and save.

This applies to everyone, including existing subscribers. Just visit the new subscription management page and modify your subscription to lock in the lower rate. The longer the cycle, the more you save.

One caveat: if you're on grandfathered pricing from Teslemetry's launch, the new rates may not be cheaper depending on how many vehicles you have. It's worth checking the new prices on the subscription page before making any changes.

The iterative approach paid off

Looking back, the decision to ship Website 2.5 as an intermediate step was absolutely the right call. It let me ship the new backend, gather feedback on the rental automation feature, and build confidence in the new architecture — all without blocking other work. Teslemetry 3.0 was able to focus purely on the frontend experience because the hard infrastructure work was already done.

What's next

This launch is a foundation, not a finish line. With the new codebase in place, I can iterate faster than ever. Internationalisation, new integrations, and continued UX improvements are all on the roadmap.

As always, Teslemetry likes to move fast, so if you run into any issues please reach out to support and I'll get them sorted.

Thank you for being part of the Teslemetry journey — here's to the next chapter.