Do OTA Software Updates Count as California Lemon Law Repair Attempts?

Quick answer: An over-the-air (OTA) software update may count as a California lemon law repair attempt when a manufacturer uses it to address a warranty defect you reported. The key questions are whether you presented the problem, whether the update targeted it, and whether the problem continued. A routine update sent to every vehicle is not automatically a repair attempt. The distinction matters for Tesla, Rivian, Ford, GM, and other vehicles that receive remote fixes.

Have a serious software or safety problem? Even one serious incident can justify an early California lemon law case review; one incident alone does not establish a buyback claim. You can seek advice while documenting the defect and arranging necessary repairs.

What the statute actually requires

The Song-Beverly Consumer Warranty Act (Civil Code § 1790 et seq.) requires a manufacturer to replace or repurchase a qualifying new motor vehicle that it cannot repair to conform to its express warranty after a reasonable number of attempts (Civil Code § 1793.2(d)(2)). The statute says service or repair and attempts; it does not specify a replacement part or a particular software-delivery method.

California's pattern jury instruction, CACI 3202, addresses repair opportunities, including occasions when the manufacturer's representative does not successfully identify or fix a reported problem. In Oregel v. American Isuzu Motors, Inc. (2001) 90 Cal.App.4th 1094, the court explained that consumers must give the manufacturer a reasonable opportunity to repair; the manufacturer's failure to take advantage of that opportunity is not the consumer's responsibility. In Robertson v. Fleetwood Travel Trailers of California, Inc. (2006) 144 Cal.App.4th 785, the court recognized that the presentation requirement could be satisfied by repairs undertaken at the consumer's residence with consent.

Those rulings support an argument that a manufacturer-directed remote fix can be a repair opportunity, but neither decided whether an OTA-only update qualifies. The question is not simply whether the vehicle visited a dealer: it is what notice and opportunity the manufacturer received and what repair it undertook.

The three things that decide whether an OTA update counts

1. Did you report the defect through an authorized service channel?

Civil Code § 1793.2(c) generally calls for delivering a nonconforming vehicle to an in-state manufacturer service facility. Written notice can stand in for delivery when delivery cannot reasonably be accomplished for specified reasons, including the nature of the defect. An app message alone should not be assumed to satisfy every legal presentation requirement.

Report the symptoms through a manufacturer service app, authorized dealer, or customer-care channel; request a service appointment when appropriate. A Tesla service-app ticket, Rivian service request, Ford dealer record, or GM customer-care case can help establish notice. A social-media complaint alone is much weaker. If the manufacturer's answer is, "We are sending an update to address your complaint," preserve that message, along with the date and service-ticket number.

2. Was the update directed at your defect or merely a general release?

An update specifically identified as correcting your reported problem is stronger evidence than a general firmware release with dozens of changes. A general release might still be relevant if service records, release notes, or manufacturer communications connect it to the complaint. But installing software and later reporting the same symptoms does not automatically establish two separate repair opportunities; document each renewed request and the manufacturer's subsequent response.

In Donlen v. Ford Motor Co. (2013) 217 Cal.App.4th 138, the court addressed evidence of a defect that persisted beyond the warranty period. Continued or recurring symptoms after an update can help show that the original warranty problem was never corrected, even if its effects temporarily disappeared.

3. Was the vehicle usable or out of service for repair?

Many OTA installations occur while the owner keeps the vehicle, so an ordinary software download does not automatically add days to the lemon law's out-of-service calculation. But if a failed update disables the vehicle or requires it to remain unavailable while the manufacturer performs repairs, the circumstances may support counting qualifying repair downtime. Record when the car became unusable, when repair efforts began, and when it was usable again. Mere inconvenience or inability to drive, without the statutory connection to repairs, is not necessarily enough.

Software defects are defects

Song-Beverly does not exclude software simply because the vehicle's hardware is intact. Under Civil Code § 1793.22(e)(1), a covered nonconformity substantially impairs the vehicle's use, value, or safety. Examples may include unintended braking, a blackout of a screen controlling safety-related functions, a battery-management fault that substantially limits range, adaptive-cruise failures, or a software-related 12-volt battery drain. Whether a particular defect meets the standard depends on its actual effects and the warranty evidence.

The presumption still works for software

The Tanner presumption in Civil Code § 1793.22(b) may establish that the manufacturer had a reasonable number of repair opportunities if, within the first 18 months after delivery or 18,000 miles, whichever comes first, one of these conditions occurs:

• The same defect likely to cause death or serious bodily injury if driven has been subject to repair two or more times, with the required direct manufacturer notice.
• The same defect has been subject to repair four or more times, with the required direct manufacturer notice.
• The vehicle was out of service for repairs of covered defects for more than 30 cumulative calendar days, subject to statutory exceptions.

The direct-notice requirement for the two- and four-attempt routes applies when the manufacturer made the required disclosures in the warranty or owner's manual. A qualifying third-party dispute resolution program can also affect when the presumption may be invoked. An OTA remedy directed at the defect may support an attempt under these rules, but that characterization remains fact-dependent.

These numbers create a rebuttable presumption, not an exclusive checklist for every claim. Outside the presumption, the number of reasonable opportunities depends on the circumstances. Silvio v. Ford Motor Co. (2003) 109 Cal.App.4th 1205 held that a single repair opportunity alone does not trigger the replacement-or-restitution duty under § 1793.2(d)(2). That does not mean an owner should delay getting legal advice after a serious first event.

Why OTA cases get lost: the documentation gap

A dealership repair order normally records the complaint, date, mileage, and work performed. An overnight software update may leave only a temporary screen notification. If the dispute later concerns whether the manufacturer tried to fix a particular defect, missing records can make the owner's position harder to prove.

Close that gap:

1. Report each occurrence through an official service channel. Describe the symptom, date, conditions, and safety impact; request a case number.
2. Save the service conversation linking a proposed update to your specific complaint, including emails and app screenshots.
3. Record software versions before and after relevant updates, with dates and screenshots where available.
4. Report continuing symptoms after each attempted fix in writing, and ask what repair or inspection the manufacturer will perform next.
5. Request an authorized service appointment when appropriate. A dealer or mobile-service repair order creates a clearer record. Keep any written refusal or instruction to await an update.
6. Preserve notices to the manufacturer, especially when the warranty requires direct notice to invoke the statutory presumption.

Do not delay necessary safety repairs to gather evidence. If the vehicle is unsafe to operate, stop driving it and follow applicable safety and recall instructions. You can also have us review your OTA repair history before another update or service visit; the review does not replace required notices or repairs.

Recall remedies delivered OTA

U.S. safety recalls can use OTA software remedies. For example, NHTSA recall 25V-002 concerned loss of rearview-camera images in certain Tesla Model 3, Model S, Model X, and Model Y vehicles. Tesla released a free OTA update and provided for computer replacement on vehicles with specified hardware failure or stress. This is a documented example of an OTA recall remedy, not proof that every affected vehicle has an unresolved lemon law defect.

If your vehicle received an OTA recall fix but the same serious symptom persisted, preserve the recall notice, installation date, updated software version, and subsequent service communications. The recall and repair history can support the analysis, but the existence of a recall or software push does not automatically establish a failed California lemon law repair attempt. Check NHTSA's recall lookup for your vehicle and promptly follow applicable safety guidance.

Pre-suit notice for opted-in manufacturers

California's AB 1755 and SB 26 established additional procedures for manufacturers that elected to participate. For covered actions, Code of Civil Procedure § 871.24 requires a written demand and specified vehicle and repair information at least 30 days before filing an action seeking civil penalties under Civil Code § 1794(c); the consumer must also possess the vehicle when the notice is sent and comply with applicable possession requirements during the manufacturer's response period. Section 871.21 provides filing periods tied to warranty expiration and original vehicle delivery, with statutory tolling rules. These are legal deadlines and procedures, not reasons to postpone a case review.

Opt-in status depends on the responsible manufacturer and the applicable election. Consult the California Department of Consumer Affairs' official opt-in list rather than assuming every brand follows the same rules. We can help assess which procedures apply; contacting us does not itself satisfy a legally required manufacturer notice.

Frequently asked questions

Does a Tesla software update count as a repair attempt under California lemon law?

It may, especially if Tesla received your defect report and identified an OTA update as the remedy. Preserve the service-app messages and software versions. An automatic update without a documented complaint is less persuasive, and whether a remote update legally counts depends on the record.

Can a car qualify for lemon law relief based only on software problems?

Yes, potentially. The issue is whether a covered warranty defect substantially impairs use, value, or safety and whether the statutory repair-opportunity requirements are met—not whether the cause is software or hardware.

How many OTA updates are required?

There is no separate statutory OTA-update number. The Tanner presumption addresses two repair attempts for specified serious safety defects, four attempts for the same defect, or qualifying repair downtime, within its time and mileage window. A claim may warrant early review even before those thresholds are met.

What if the manufacturer sends updates but will not schedule service?

Keep written requests for an appointment, the manufacturer's responses, and evidence of any attempted OTA remedies. Refusing an inspection may matter to whether you gave the manufacturer a reasonable opportunity to repair, but it does not automatically prove the claim.

Do I need a lawyer for a software-related lemon law claim?

Not every dispute requires litigation, but an attorney can evaluate whether the available records establish a defect and repair opportunities, and whether additional manufacturer-controlled service data may be obtainable. Civil Code § 1794(d) permits recovery of reasonable attorney's fees and costs for a consumer who prevails, subject to applicable law; recovery is not guaranteed.

Request a California lemon law case review

If your Tesla, Rivian, Ford, GM, or other vehicle has a persistent software or safety defect, you do not need to decide for yourself whether each OTA update qualifies as an attempt before seeking advice. Save the service messages, repair records, update history, and symptom timeline. Request a free case review or call (888) 536-6628 to discuss potential California lemon law rights and next steps.