This is a beta thread that came out over 7 months ago, so most employees won’t be following an old thread in this channel after all that time. Beta threads are even set to normally expire and lock after 3 months because they are really only intended to be short-term and temporary, for us to report bugs for them to relay back to the devs.
Wyze employees have responded many times over the summer in more relevant areas about what is going on with the Vacuum updates. The short version is that they have an update ready to go out and merge all the different beta firmware branches back together, but tests indicate that a percentage of units on some of the firmware branches will become non-responsive after the update goes public, so before Wyze pushes it out to everyone and suddenly has a bunch of people upset that their devices got bricked, Wyze is preparing the logistics. Per WyzeGwendolyn:
The reason we haven’t charged forward yet is because this is a fairly risky update for vacuums that are on one of the beta branches of firmware. Merging the code is expected to result in a portion of them becoming unresponsive so we’re making sure we have systems in place to take care of anyone impacted with a minimum of fuss on their part. At this point, I’m working with our logistics team on part of the plan.
Thanks for checking in and I apologize for the delay!
Our first goal is to mitigate the risk (the bulk of the delay on this). Our second goal is to make the best experience we can for folks that find themselves with a borked vacuum.
They’re not ignoring the Vacuum and they aren’t ignoring users asking about this, they just don’t usually respond in dead beta threads…but there is one of the latest responses quoted above…they’re just trying to make sure things can go as smoothly as possible for those who will be affected the most by the update.