Got it. thank you.
Thanks for your patience while we chased down various team members for info! Here are our top issues (plus a bonus) for this week!
The low volume is due to a hardware limitation. We’ve heard your feedback and are working on supporting Wyze Home Monitoring audio on Wyze Chime. This will allow you to decentralize the audio and have it in the rooms that you care about. We’ll share information about it when it’s ready!
This is a bug! And we’re looking into it. Please send in logs if you reproduce this bug. Logs can be sent through Account > Wyze Support > Submit a Log. Please be detailed in the description and post the log numbers where we can get them!
You may have noticed WyzeQi working on this before we started the summary here! We’re investigating it now.
EDIT 2/22/22: We have a fix ready for testing!
We’re aware of this issue and we’re working on it! We’ve identified the root cause and are building a fix.
This is the end of the first cycle of Fix-It Friday! We’re talking internally about what worked and what could use improvement. We may make some changes to how the program works based on your feedback and how things went from our end.
We’ll continue to provide updates on the outcomes of Fix-It Friday. We’re always working hard to find and fix issues every day! The feedback from our engineers, testers, and members like YOU make such a difference in this venture. We hope these Fix-It Fridays will help shine light on the bugs you have top of mind and prioritize them for our teams. Look out for more from us soon!
And if you need help with a misbehaving Wyze product, please don’t hesitate to reach out to Wyze Customer Support.
Have an excellent week, everyone! Thanks for putting together these amazing reports. I felt so proud of our community as I read through these!
Gwendolyn, thank you for addressing the issue of the low volume on the HMS Hub.
I do not see Chimes being an acceptable solution. I have a chime for my doorbell and it is about as loud as the hub.
You stated that this issue is being caused by a hardware limitation. When I first installed the HMS hub the contact sensor chimes, the voice response, and the siren were very loud. I could hear it from anywhere in the house. It was a firmware update that changed this. I still have the same hardware I installed that previously performed at a much higher volume. As such, it is not the hardware that is limited as it performed out of the box perfectly. It is the firmware that is now limiting the hardware. Or, more accurately, the installed firmware cannot support the capabilities of the hardware.
Also, unless the chimes are going to provide an intruder deterrent level siren alarm, the solution is moot. This is a home alarm system, not a smart speaker.
Lastly, since this issue reflects a change in the original product caused by a firmware update after it was shipped, installed, and operated successfully, I would expect Wyze to provide any additional hardware solution at no cost to existing customers. I purchased a functional HMS Hub. The firmware update changed that.
What this person said. Worked fine when I got it, stopped working. Needs to work again without me having to invest more money. At the moment the alarm system is not fit for purpose. Shouldn’t really be sold until it is.
Hi @R.Good we’ll fix it in v2.29 which will be released in the middle of March.
Perfectly said by @SlabSlayer.
@WyzeGwendolyn The hardware limitation was only a thing once the September 2020 update was introduced. That’s not the same operating item that we once paid for. It’s speaker functionality has been altered through SW to become what is NOW being called a limitation.
Serious question: Who’s idea is it to STILL stand their ground on this liability issue? I mean just revert the freaking SW back to where it once was where everyone was happy.
I wasn’t aware of any major thread where folks were complaining about blown siren speakers from the volume being too loud. If I missed something, please share that discussion here.
Also this issue is going soon on 6 months… when does it take a serious priority to the @WyzeTeam being how long the issue has been already ongoing for.
Thanks for the feedback, everyone. I’ll get these links over to the team for consideration as well.
For the bugs that were not addressed since they did not make the top 3, can they still be fixed since they are still bugs?
I reported those to the team, too.
I missed out on participating in this Fix-It Friday, as I was out of town for a funeral. I probably should be waiting a month or so until Fix-it Friday rotates back to these forums, but thought it prudent to state for the record that LANDSCAPE MODE on iPads and Android Tablets is indeed a BUG worthy of being discussed on Fix-It Fridays.
I consider the Landscape issue on iPads to be a Bug, and also to be a Bug that has been ignored by Wyze for over Four years. (And I can’t get a straight, honest answer out of anyone at WYZE on this question, as to why does this BUG continues to be ignored)
For anyone interested, It’s in Reddit this week:
Looks like Fix-it Friday will be available in all Wyze Communities… a welcome change, I pretty much stay here in these forums, and rarely venture over to Reddit or other places.
Does anyone know what the Window of opportunity is to post in Fix it Friday?
My understanding is that it opens sometime on Friday, usually the last half of the day (based on what I’ve seen), and for the rest of the weekend it seems anyone is allowed to post bugs and vote on posted bugs. It seems that votes count up until sometime on Monday when they collect the highest voted on bugs and then write up and post a public report on those.
Unofficially, in practice, the bugs that are posted the earliest get the most exposure, and therefore the most votes for the most part and are thus the mostly likely to be chosen. So the earlier you post a bug the better because those posted on Sunday are already far behind the ones posted on Friday, BUT Gwendolyn did say that all the other bugs were reported to the team even when they weren’t the top ones being reported on, so don’t feel like it ever too late to report a bug (or vote on the other ones up through Monday), it just might not be one of the top few that gets a detailed action plan or explanation, and someone might add it in earlier to the next time. For example, I took a couple of the bugs from this list and reported them in Reddit, hoping they would get more votes this week so we can get a report on them.
I mostly stick to this forum too, SJ, but once in a while I will venture into Discord to Reddit for a few events if something special is taking place like an AMA or a Fireside or something.
Latest: Fix-It Friday 2/25/22
Thank you !!!
I have also been wondering about this.
How do we enable them?
@WyzeGwendolyn , any update on this issue?