Three of my older Wyze cameras stopped working immediately after the latest firmware update.
I spent about two hours with support. The front-line reps were excellent—patient, professional, and clearly doing their best within the limits they’ve been given.
But the process itself is the problem.
As a network engineer with 30 years of experience, I can say confidently: this is not a network issue. This looks like a firmware regression affecting older devices—something that should have been caught in testing.
Instead, the support flow is stuck in a loop of basic troubleshooting (reboots, connectivity checks) with no effective path to engineering. Add in multiple chat disconnects, and the experience becomes unnecessarily frustrating.
This points to a larger issue at Wyze: a support model that’s internally focused rather than customer-focused. When front-line teams are isolated from engineering, real problems don’t get solved—they get recycled.
I suggest Yun Zhang, Melissa Kirmayer Eamer and Dongsheng Song admit their support system stinks and redesign it from the ground up.
What would help:
-
Stronger regression testing across legacy hardware
-
Clear escalation paths to engineering with feedback loops
-
Reliable support tooling (chat stability matters)
-
A rollback option when firmware updates break working devices
Wyze built its reputation by doing things better than the incumbents. But gaps like this are exactly how companies lose that edge over time.
Wyze’s core advantage is price, not engineering rigor. Once you move up even slightly:
-
Firmware quality improves
-
Support improves
-
Failure rates drop
…but you’ll usually give up:
-
ultra-low cost
-
free cloud features
I hope this gets fixed—not just for me, but for everyone relying on these devices.