News
My journey with a SolarCity System: Snow, Net Metering
After 9 months of planning, waiting and negotiating, my SolarCity system installation was finally completed in December of 2014. Following the install, the only steps that remained were to implement updates required for net metering and to finalize the electrical and building inspections.
The electrical inspection went quickly, but the building inspection was a pain. The local building inspector wasn’t very responsive and scheduled inspections shortly after large snow storms, but then refused to do the inspection due to “snow covering the panels”.
While we waited for the inspections, which finally took place in March of 2015, National Grid installed a new Net Meter. Net meters are capable of monitoring the amount of power being sent back into the grid. The meter swap is quick work, but be forewarned that it requires power to be cut from your home during the swap.
Weathering the Storm
We had a brutal Winter here in the Northeast and this was my first year with panels. So I had concerns about the impact of the heavy snow being on top of the panels, and also how one goes about cleaning off the snow. I asked SolarCity about proper handling and they told me not to worry about it:
“We understand your concern with the snow and the load that it would cause. Please be advised that when your system was built, our engineers took into consideration, your roof structure as well as the amount of weight that it would be able to hold. We also have the system approved by the City for load bearings.The City and our engineers did take into consideration, the amount of largest amount of snow that your roof can withstand before we installed. I understand that there was a mass message out to all the people in the area advising them to make sure that they clear the roof. We advised that you allow the snow to melt/slide down on its own., If you are hiring someone to come out to clear the roof. Make sure that they be careful and they only sweep the panels.”
I patiently waited for the snow to slide off the panels and sure enough it did, and with no issues. The snow slides off the black, wet glass-like surface of the solar panels. You definitely don’t want to be anywhere below the roofline when the snow decides to let go!
Early Issues – Broken Gear
Once National Grid completed the net metering install, I was finally approved to turn on the system. The first step involves turning a big dial (on each inverter) from off to on. I have three inverters which means three dials to flip on.
I turned each of them on. Two lit green almost immediately while the remaining inverted displayed a red fault light. There were no instructions on what to do in this scenario; no manuals and no guidance, so my only option was to call for help.
Getting help from SolarCity on the issue at had was a frustrating experience. SolarCity has a lot to learn when it comes to customer service. I spoke to several customer support managers as I continued to escalate my issue.
Finally, after five weeks of follow ups and many phone calls, I got the broken inverter fixed.
Tip:
SolarCity doesn’t bother to tell you this, but what I discovered was a little black button in the middle of the inverter. It’s hard to see but if you press the button you’ll be able to cycle through messages on the digital display, one of which is a fault code. Providing SolarCity with a fault code is much more useful than just letting them know that a red light is blinking.
Early Issues – Snow Fall
As mentioned earlier, snow doesn’t stick to the panels for long, but it does manage to build up before it lets go. Imagine 3 feet of heavy snow mixed with ice over your entire roof all letting go at the same time. It’s not a slow drip. It’s an avalanche.
The end result is dead flowers, dead bushes, and broken branches on vegetation immediately below the roof. As much as it’s common sense that snow will eventually melt from a roof and slide down, I wish SolarCity would have warned us that snow tends to slide from solar panels at a much quicker rate. I would have done something to fortify those flowers and bushes. After all, landscaping is not cheap.
There’s an accident waiting to happen so I think it’s in SolarCity’s best interest to pre-warn people of this, especially newbies to the world of solar panels.
Summary
Eleven months after starting the project, my SolarCity system finally went live (partially) on February 23, 2015. And on April 1, 2015, the third inverter was fixed allowing the system to work in its full capacity.
The image to the right is showing the day when the transformer on my street blew up and the entire street lost power for several hours. I added 33% more power from my large system going back into the network while using very little (Winter time) the same day the transformer blew. But then again, it was also April 1. Nobody made a fuss — National Grid replaced the transformer and all has been stable since. My best guess as to why that happened? Perhaps the transformer was already near its thresholds and my solar installation was the one to tip it over?
I’ll be writing about system monitoring, cost savings and billing errors in upcoming posts. The story isn’t over yet.
Turn-by-turn navigation is not new technology.
For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.
Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.
Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.
Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.
But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.
This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.
More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.
It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?
Multiple Data Sources
First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.
Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.
Persistent Learning
FSD seems to struggle with persistent learning from driver interventions.
Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.
This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.
I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.
The next thing I’ve noticed, and this might be controversial, is that Nav has gotten even worse.
I think that might actually be a good thing; Tesla seems to be adjusting it. They just need to adjust it the opposite way.
The car is taking extremely strange routes to very… https://t.co/UHg3tVfNA2
— TESLARATI (@Teslarati) June 16, 2026
Reasoning, Scaling, and Intuition
Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.
Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.
Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.
Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.
Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.
A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”
Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”
🚨 A Tesla Cybertruck, which is illegal to drive in the UK due to safety concerns, has been seized by police in Greater Manchester
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a… pic.twitter.com/cqhdPok3DM
— TESLARATI (@Teslarati) June 16, 2026
The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.
The Greater Manchester Police Department then added:
“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”
The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.
Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.
A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.
Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.
A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.
CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.
Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:
The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.
Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.
This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
