Yes. Creating the need for Firmware Flash recovery or reversion updates is 100% on Wyze.
I have been posting for quite some time now that the high failure and Cam brick rates after firmware updates is being caused by what I imagine is a failure in the delivery and install mechanics, not in the firmware code. Else we would be seeing firmware failures across the board rather than only on a percentage of updated cams. However, local network connectivity efficacy does play a supporting role in the success of updates, and that is on the user. Where Wyze needs to grow to overcome this possible barrier to successful updates is in download package inspection after delivery and an abort sequence that returns the cam to prior firmware when errors are found on download or install. The OTA Update vehicle needs tightened up.
For some time now I have suspected that the Bulk Firmware Update procedure is blasting too much data across the network while trying to update multiple cams simultaneously and causing increased failure rates. I only OTA update single cams at a time and suggest the same to others. It also prompted this Wishlist post (unashamed self promo for votes): Progressive Bulk Firmware Updates.
I would put only a small responsibility for failed Firmware Flashes on the User. After all, Wyze did create the need.
Unless you have done it several dozen times, it isn’t intuitive and one must be really tech savvy at sussing out possible failure points to find out why Manual Flash Updates are failing. When all the moving parts do align, it does work.