DFRobot Support Sold Me a Defective Board They Knew About

Community General Discussion
1

I purchased an FireBeetle 2 ESP32-P4 AI Development Kit (MIPI CSI / DSI & Wi-Fi 6) board from this seller, and they knowingly shipped a defective unit. I confirmed this after extensive troubleshooting and independent verification. The board was non‑functional from the start, yet I spent an entire day and night attempting to make it work, including writing custom code and testing multiple configurations. This resulted in wasted time, lost productivity, and unnecessary effort caused directly by the seller’s decision to send hardware they were already aware was faulty.

This is not a simple quality‑control mistake — it reflects a disregard for consumer protection standards. I am requesting corrective action, including a verified replacement or refund, and I am filing this complaint to prevent other customers from experiencing the same issue.

2

Good luck with that.

I don't know what DFRobot's customer service is like, but some retailers will try and turn the blame on you for using it.

I once tried to return an LED bulb that didn't work out of the box, only to be told that as I had taken it out of the box and put it in a lamp holder, I was in some way to blame. Must have been my 500-V DC mains supply.

Hopefully, they will put things right. If they don't, then roll out as many poor reviews as you can.

3

I'm guessing @rid1122 is already aware, but just to be sure it is clear to others who read this, I should state that DFRobot is not affiliated with the Arduino company in any way.

Arduino has gone to great lengths to establish an open hardware ecosystem. This has allowed many different companies to manufacture hardware that can be used with the Arduino framework. A massive and diverse array of 3rd party compatible, derivative, and clone products are supported by the flexible framework designed by Arduino, without relying on any coordination between the independent producers and the Arduino company.

As for your situation with the board. I would recommend giving the DFRobot's customer service (or the seller you purchased from if you didn't buy directly from DFRobot) the opportunity to support you before you get out your pitchfork. I think that most of us would be pretty happy to do something 99.99% perfectly. However, if a company has that success level in their quality assurance, that still means one out of every 10000 customers is going to have a bad time. It might well be that 99.99% is not actually a good success rate in manufacturing (this isn't an area I work in, so I don't know), but even a company that manages to add more 9s to that figure is still going to make a mistake eventually. The more important thing is what they do when the inevitable mistake does occur.

If you are unlucky enough to be the one customer out of 10k who gets a bad board, it is easy to jump to the conclusion that your experience is representative of every customer's experience. Meanwhile, the other 9999 are happily using their functional board.

There is also the problem that the ones who had a bad experience are (understandably) motivated to complain loudly, while the ones who got exactly what they expected have no reason to mention it. So if you go searching for others also reporting problems, they may be easy to find.

Another thing to consider is the "you get what you pay for" factor. Quality assurance requires resources. Companies that produce products where reliability is critical invest a large amount of resources into QA. They must set a price on those products high enough to covers those resources. A company that produces products targeted to a hobbyist/maker market might decide that their market prefers a low priced product, and can tolerate a lower quality assurance rate.

4

I keep the scatter gun as a last resort.

A good retailer will put things right without pulling up the drawbridge or finding a hundred reasons not to do something. My local council does that.

I always give them a chance, and it sorts the wheat from the chaff. It's a lot easier for online sellers to walk away than going to a physical shop.

It is deeply frustrating when you have paid upfront, got the goods and as in this case, they don't appear to work. DFRobot is quite well known and probably has a reputation to maintain.

Yes, if you buy cheap, expect cheap, but imagine if some child starting out in the world of electronic etc. and their first attempt ends in failure, tears. Not good.

5

Just curious why you say they knew ??

Where ia the proof of that claim? Why would t it be a quality‑control mistake ?

Ask for a refund …

Note also that they will have no proof you did not power the board with 24V or did stupid things. In my past life I’ve seen the most vindictive customers to actually have abused the product and trying to bully their way into support.

Not saying this is your case - just saying this exists.

6

The module timeouts out or a slight signal fade causes a dropped connection. This is :100: FireBeetle 2 ESP32-P4 AI Development Kit issue. Update your computers ports compatible in every aspect of the uploading ,you will have no luck

The hard 0.0.0.0 address under these clean software test conditions points to a physical hardware assembly fault. End of story
Look, I am definitely not a tech expert, but everything points to this being a defective board straight out of the box. It just isn't working, it's defective. And I'm convinced they were aware of it. Why test every single board when you can have your customer test it for you and you give them a cheap refund. Here's store credit. Buy more junk.

PXL_20260801_143003299
PXL_20260801_1430032991920×664 177 KB

7

We are technically and facts driven here, and it's the Arduino Forum, not the DFRobot support line or forum. I can sympathize on the frustration and venting need, and this actually gives some useful context to work with.

The fact that you saw a 0.0.0.0 address means code was uploaded and the serial connection worked fine. So the core hardware, the chip, the USB to serial converter, the flashing process, is working. The issue narrows down to the Wi-Fi module not getting an IP address, which is different from the board being dead out of the box.

There is a documented reason this could happen. DFRobot published a notice stating that some FireBeetle 2 ESP32 P4 boards manufactured on October 31, 2025 had a firmware flashing issue on the ESP32-C6 Wi-Fi coprocessor during production, with a fix available via their ESP32-C6 Firmware Update Guide. That matches your symptom closely.

So, did you check your board's manufacturing date against that window, and did you go through the Getting Started guide before concluding it was unfixable? You mentioned writing custom code and testing configurations for a full day and night, but didn't say whether the documented setup steps, including this firmware update, were part of what you tried. That would help clarify whether this is a case the fix doesn't cover, or one where it might.

The WiFi issue can also come from other elements - like you own WiFi infrastructure you are testing with, signals perturbations due to your environment and the small antenna on those modules etc...

So a couple of questions this raises. Is your underlying point actually that a kit like this should not ship at all if there is a known risk it needs a firmware update before it works, rather than that the board itself is defective? Those are two different arguments, and worth separating, since the first is more about expectations for tech kits in general and the second is about this specific unit.

A sub $20 eval board pairing two separate chips is not a plug and play consumer device, and skipping the getting started documentation on a board like this is a common way to end up stuck on something that has a known, published solution.

Before asking for a refund and publicly warning other buyers etc, the reasonable step would be to confirm in details whether the documented fix applies to your unit and clarify what you have explored and be also specific about what are angry about....

Hope the venting helped - and if you had not updated the firmware, then I suggest you try that.

8

As a rule, people who write such emotional messages about software bugs or malfunctioning hardware - do not have a habit to read the documentation...
It brings to mind the joke about the man who complained that the steering wheel and dashboard had been stolen from his car, only to discover he had sat in the back seat...

9

Is that seller an authorized DFRobot distributor? If not, all bets are off. There are copies and look-alike boards on the market.

Did you read the board documentation and user manual?

A quick search turns up several different sources for what appears to be the same board, including multiple manufacturers or brands. Who did you actually purchase it from?

Also, how have you determined that the board is defective? Is this based on a simple, well-defined test, or only with your custom test software? Before concluding the hardware is bad, it's important to verify it with a known-good example or one of the manufacturer's test programs.

10

Read the manual. Wow. What great advice. Or maybe it’s just an arrogant shield for people who don't actually know the answer.
Why not just help solve the problem? Let me guess...we hide behind documentation because we couldn't fix the issue ourselves if we tried. Read the documentation...give me a break.. post it here.

This is the world we live in now, where real answers are nowhere to be found.

11

This attitude won’t get you very far here ..

Did you read my answer?

The ask was “did you read the manual and apply what seems to pertain to your issue” since you failed to provide suitable information in your long rant and after you provided a tiny bit of information it appears that the board is not really dead on arrival…

But you keep venting rather than focusing on what matters…

Until you clarify what you did , the status of the firmware etc, how do you want us to be able to provide any suitable guidance?

so good luck

12

Reading the documentation is what most people do.

I had a quick look at the DFRobot site with this kit and it looked to be pretty complete.
I think you've jumped in thinking everything's going to work straightaway.

The clue is in the name, Development Kit. Development usually requires some user effort.

You've already said you aren't a tech expert, but you buy a fairly complex kit.

A genuine Arduino board, where instructions have been followed, 99% of the time will work out of the box just by applying power. The problems arise when someone decides to save a few quid and buy a cheap clone. It doesn't work. It uses a different chip or a different bootloader. Use the right bootloader and it works. All that frustration goes away.

It's pointless using the Arduino forum like a review site, or some consumer protection advice site.

I would draw breath and in the first instance ask DFRobot politely, outline your problems and see what happens.

13

You're right.
But, I do think there is value in posting. People's favorite word. "Documenting" my perspective.
Once support helps me solve it, I plan to post their exact solution back here so it can serve as a clear reference to help others down the road... After all, I'm writing to inform. 2 Help all the non experts.

14

Posting a rant / venting on a technical forum is probably not how you achieve this ..

If you had posted a different version then things would be different. Consider this for example

I picked up a FireBeetle 2 ESP32-P4 AI Development Kit and have spent a full day trying to get it working, without success. I'm not a tech expert, so I'm hoping some of you can point me in the right direction before I go further down the refund route.

The symptom: after uploading code, the board reports a 0.0.0.0 address and the Wi-Fi connection never comes up. Serial upload itself works fine, so the flashing process and USB connection seem okay. The problem seems isolated to the Wi-Fi coming online.

What I've tried so far: multiple configurations, some custom code, different ports on my computer. What I haven't checked yet which I saw in the getting started guide : the manufacturing date on the board, or whether there's a known firmware issue for this batch or if I need to go through those steps.

Before assuming the unit is defective, has anyone run into this exact 0.0.0.0 symptom with the ESP32-P4 kit. Is there a standard troubleshooting sequence I should run through first, firmware update, getting started guide, or anything specific to the ESP32-C6 Wi-Fi coprocessor on this board. Happy to share whatever details would help diagnose this properly.

PS: we still don’t know if you tried installing the firmware…