I would agree with the statement that HMS isn’t ready for prime time. The hub has been and remains unreliable. You may or may not be able to add new sensors. You may or may not be able to arm or disarm the system or get an accurate status of it. Motion sensors that trigger for no reason. Single PIN. Single locations/hubs. Single contact number. (I know, this one is under testing along with shared access.) Keypad may or may not arm/disarm the system. Low volume for the alarm feature (a hardware, incorrectable problem.) Inability to change the “Tunes” setting.
Forgot to mention no geofencing (for one or many) and no outdoor sensors.
This morning I reported in the Beta reporting system that I have noticed that the Home Monitoring “Tune Setting” menu item is gone. It must have something to do with the Chimes being off on the Hub so maybe it thinks that feature is unavailable. But when I look and it is there (I just reset the app, and now it is available as a menu item), I can turn “Entry Notice” back ON and the Chimes came back. How long it will stay is anyone’s guess. I’ve found that it randomly goes away 24-48 hours (in my experience).
I suspect someone (everyone?) has reported this already so it’s probably old news. But just in case they haven’t. (I tried going through the forums but there is a lot to go through!).
Wyze has also asked people to respond to the following questions and post them in the previous Fix It Friday thread (they even made 2 attempts to get interaction on this), and I don’t recall seeing [many responses] from people answering any their questions as they requested:
And again a second attempt to get some response from users that also went [mostly] ignored in that thread as far as I saw:
So far as I have seen, [few people have] responded to either response from Wyze asking users to answer all those questions in that thread so they can try to figure out what’s wrong. That may be why not much has been done. Everyone says there are problems, and granted there have been plenty of logs submitted before these requests went out, but [few people] ever responded to either post from Wyze asking for help so they can fix it. I’ve continued to see people say the problem still exists, but [fewa are] responding to those posts or answering the questions Wyze has said they need help with to figure it out. I would encourage people to go through Wyze’s steps one by one and give a detailed description and answer about each step and question so they can gather the info they say they need. I’ve been tracking and making suggestions to people about it, but again, so far, [few people respond] in that thread answering the steps or questions like they asked along with a log at the end. Not one since they asked for more information. I’d highly recommend do as requested so they can resolve it.
Edit: I stand corrected, originally I said there was not a single response in that thread since Wyze posted their response and as I just reviewed the fix it friday thread again and noticed that there were 3 in that thread:
My appologies for any offense from what I said. The response Wyze gave had asked that responses be posted in the Fix It Friday Thread, and I did not see a response from you there.
I tried to find it, and I know you corresponded in the firmware announcement thread about having problems with the firmware and said your main point was to request to be able to roll back the firmware. I am very supportive of your suggestion there. I apologize if I misunderstood anything that was intended. Regardless of any of that, you did a GREAT job here answering the questions above. It is much appreciated.
I also realized that I misspoke anyway. There were 3 other people who responded in the Fix-It-Friday thread answering all the questions thoroughly with logs included, so I appreciate you bringing that to everyone’s attention, especially me. I must have read them at 3 am while I was working and just forgot somehow. The current responses I’ve found since Wyze’s request now include:
You seem to be implying that Wyze will only recognize my response if it’s in the same (now old) Fix-It thread where the questions were originally posed. That seems odd but but in the spirit of attempting to try to bring this month-long issue to resolution … sure, I’ll repost my answers again in that thread.
I appreciate your updated comments. Let me try and explain our frustration.
I’ve been a Wyze customer for years and these hub issues have been the most disruptive problem I’ve had with their products. Their customer service response has been embarrassing.
In more detail:
Wyze releases firmware 126.96.36.199.
Almost immediately, users report issues with the firmware, spread across multiple threads.
Wyze pulls the firmware.
Despite multiple reports of issues, many with log submissions, Wyze states they can’t identify the issue and poses several (fairly basic) questions to the community.
The community provides additional information; in some cases, directly answering the questions.
Wyze provides no substantive update regarding this issue. The only response we get back is an experienced member of the Wyze community blaming users for not giving Wyze the information they need.
carverofchoice: I recognize you’re a user like us; but I don’t think the problem is the community not responding to a specific set of questions in a specific forum … the problem is Wyze has had a serious stability problem in their flagship security product FOR A MONTH NOW … and they either don’t have the expertise to identify the problem and/or they’re not being transparent with their customers about the severity of the issue.
Why does your screenshot seem to imply you don’t have the HMS or outdoor plug at the top? Are you slacking on me so I can win the badge contest between us?
Yes Wyze, please fix the badges to all work right. Some of us want to rub it in each other’s faces in friendly competition that we have more than R.Good… On a related feature request note, it would be awesome if the badges had a count number on them for how many of each we had… But please at least fix the bugs so they work in the first place.
On the bright side, with so many badges not working right, anytime @R.Good is beating me on badges, I can just blame it on the bugs and not reality, so I’ll call that a win-win for now.
@Earl.Automation I checked this out for you and you are right, it is not working.
Today was my first attempt at using a Person Detection trigger rule with the Video Doorbell Pro. I did have Cam Plus on it. I created a rule for it (to turn on lights), and then tested the rule multiple times. It did not function at all. It did not even show up in the rules history as attempting to run or failing to run. It’s as if it doesn’t exist. I’ve submitted a Log to help out. This is pretty far down the list now, but maybe @QiS can look into this for us anyway?
Should have occurred at 1:47pm MDT, 1:48pm MDT, 1:59pm MDT. I checked the events and they all detected a person (me) on the VDBPro, and the rule is set up, but the rule did not run, nor attempt to run and fail. It just did nothing.
That is correct., no friendly faces on the VDBPro yet, though I don’t think that is a bug. Wyze has stated that they are probably going to limit Friendly Faces to Cam Plus Pro soon, and Cam Plus Pro is intended to be for cams being used indoors, so I am not confident Wyze will make the extra effort to make it compatible on the VDBPro any time soon.
Several of us have begged them to at least make it available on Video Doorbells though because that’s one of the main places people want facial recognition, so we’ll have to see what they do. We’re also asking them to consider keeping it available for the regular HMS.
Right now we don’t really know for sure what is going to happen with Friendly Faces now that the pilot testing of it is basically complete. Hopefully they find a way to reduce their costs enough to keep it with all devices using regular Cam Plus, especially for the doorbell cams because I really like it.
The Fix-It Friday summary post will be going out tomorrow! Gathered all the info and just realized that it’s half an hour after I’m supposed to get out of here. So that’s my first priority for tomorrow. Thank you for your patience!
@milehiguy while it would seem that you may find your way to your six foot deep final resting place before me based on the amount of times the earth notates around the sun, there other factors in this game of life that might get me to that finish-line before you.
Either way, I think we have the potential to both be taking a dirt nap before the Feature That Shall Not Be Named ever finds it’s way to the Wyze App.