But has it worked?
To admit they have any issues at all is an admission of a defect. Something abhorred by product liability insurance carriers. I don’t know about you but I’ve watched as a manufacturer and a customer dragged legal teams to business meetings for the sole purpose of defining what constitutes a defect in order to assign a problem as a defect or to avoid being found to have one.
I'd agree... the Legal Console Tables have been busy and will continue... major $$ to be generated.
The discussions on the DJI forums is positive toward the FW update, since it addressed a few other issues too.
Knowing if it fixed the problem, is loose since it was minimal that even had the problem to determine... BUT...

DJI says it's been fixed and we believe that blindly correct?
All Fixed... We'd like to think so... but as in all FW logic... it may have an effect elsewhere... hopefully not a greater negative! But on the upside, this prior issue before the FW update, had effect on a percentage not even .5% of the base, and the chatter on the DJI side, the business UAV shops didn't show a concern; the majority of businesses continued normal running since it wasn't a mandatory grounding.
This whole matter as I stated initially was an over step for 1-3 incidents... primarily 1 shop. Compared to other issues; DJI admittedly acknowledges the I2 motor adhesion issue and blows it off as no concern with many expressing the ill-effects... so much so that 3rd party had time to develop counter measures. Yuneec is aware of H520 failures with no major concerns and a few others from DJI to boot. When all these issues have had a larger impact and greater percentage to the base without the slightest warning notices. This matter was FW from the get go, and suspected unique to the 1 shop's operations. The updated FW primarily addresses the 1) forced no-fly until updates performed... that in itself would have probably corrected the initial issue since the other 99.5% didn't experience the problem and 2) Steps to safeguard from Temperature issues... actually something all LiPO's have as a safety concern.
I found it amusing, the negative chatter was greater on our Yuneec thread than on the 3 threads on the DJI forums... essentially the ones operating business didn't acknowledge it as a major concern and continued normal operations... especially in USA & Non UK.
I still ponder the Govt & Politics involved in this ordeal, the notice was issued after 1 failure. Something smells more of CYA than anything.
Optimistically, I do hope it has a positive effect, the concerns become managed more through controlled maintenance SOP and the Outcome is overall positive for the Industry. But I AGREE, the Council tables have been busy and will continue to be busy.
On a similar channel... there's a senseless volley of smart battery vs vanilla LiPo debates and the issues of smart batteries. I do hope the smart batteries get better with each advancement, and I do think the days of vanilla are fading due to increasing legal and requlatory requirements. I doubt the primary power source is going to be allowed to be non-managed for aerial crafts much longer, it'll probably get a lot more complicated in FW for all RC aerial.
No one imagined the position of the automotive industry in computerization 15-20 years ago. It used to be stated to rule out a drivability problem simply pull the electronics as a test.... return it to basics. Well, on modern engines it won't run without electronics: distributorless, crank sensors, fuel patterns, Cam lift & duration computer generated, air, brakes, etc and extremely tight monitoring of voltage usage and generation. With the advancement in electronics, it'll no longer take 15 years to push designs, we''ll probably see a major change in power requirements easily within 5 years since the Govt wheels are already turning.
Even my large Tattu 22,000mAh LiPo's now have electronics.... kinda mini-smart, but helpful for storage & Hi/Low Temps. Ya... we'll all be fussing with advanced electronics for RC soon and again the one with the most experience when the requirements get "pushed" down to us will most likely have the edge.