My hub behaves exactly the same and I have also found that if you time it right you can get certain things to function like adding a sensor but you basically have to follow your exact steps.
The only problem is there is no way to tell when it will go back to doing the reboot cycle and it does happen. So just don’t rely on your system to much right now cause Iv seen mine report armed and appear fine on app but when I entered the home the alarm didn’t trigger and found the hub going through its rebooting cycle again and nothing was functioning. It eventually sorted itself out again and was working but it’s been repeating this cycle and going in and out at random intervals. Worse yet the app doesn’t report offline or anything like that and appears to function and arm/disarm. So just be aware that’s it’s still not reliable.
My biggest complaint is, not having the data to find a solution is no excuse for making us suffer and be stuck on this firmware with broken systems for this long. It’s made me realize that this system has a major design flaw since it doesn’t support firmware downgrading. If we could downgrade to the last firmware then our system would work perfectly fine and then wyze can do their own testing and get their own data instead of relying on us to do the work for them while the devices we paid for don’t even work.
I totally agree with you. I’m also frustrated by the excuse that they don’t have the data despite several reports on the forum citing this issue, which likely means many other users who don’t use this forum also have this problem.
At this point, though, Wyze and the forum moderators should not have the ability to make this excuse. As a result of my post (and other similar ones), they should have the logs and the repro steps necessary. If they still can’t identify the problem, that is very concerning re: the stability of this product, especially as a home monitoring device.
If it would actually help them diagnose the problem, I would be happy to send them my hub (assuming they first send me a new hub I can swap out and without needing to rebuild my sensor lists/rules).
Cameras do support firmware downgrading and even manually firmware flashing to new version and they provide the files online. The sense hub which has these problems does not support it and wyze doesn’t even offer the firmware files online so this is not an option with this device. Which just sounds crazy to even say considering we’re talking about a simple camera having the ability to downgrade but a device that’s sole purpose is to protect your home and family cannot downgrade. Everybody knows updates can cause problems, even updates from major tech companies with loads of money, so having a way and a procedure to handle such issues is absolutely critical.
The fact that this was not a feature that was designed into the sense hub before release is major design and security flaw and speaks volumes to how much wyze actually values your home and families protection. It also says that they find it acceptable to randomly leave you without protection for your home/family for extended periods of time. Especially considering the cams they make they always said we’re not for security purposes and the cams support downgrading. However the device they make which is specifically made for security does not support it.
You shouldn’t even have to do that. They are a tech company. They should be able to setup a testing site. Setup a hub and some sensors and whatever else they need and do all the testing they need to do and log all their own data. They are legit just relying on us to do most of that leg work for them while they sit back and claim they can’t do anything for us until we do that for them. Didn’t realize I was on the payroll……WYZE!
I actually now wonder (since it has been a month) if they haven’t broke their internal firmware. Perhaps they messed this up so bad they cannot get the Hub to load any new software. Otherwise, why wouldn’t they have just pulled the old version of software out of their GITHUB repository, change the version number, and then re-issue the new-old software so the problem would be fixed temporarily?
I am really surprised that no one has initiated a class action lawsuit over this Home Monitoring System from Wyze. As many have complained, this system has had bugs since it was released about a year ago and at times (like now) I have a system that is not securing my house as they promised when I purchased the system. I am not litigious, but just say’n.
What bugs were present when it first released? I was never aware of any and can’t find anything reported in the forums off hand.
I recall my system working basically flawlessly (bug free) for months using the original firmware, and don’t recall anyone complaining until at least July 1st when it had an issue with the V1 sensors locking up the hub. They fixed that and it was then basically flawless until the Septermber firmware that turned the hub volume to whisper mode. And the third issue was this March Firmware (which is ongoing).
You are correct and I stand corrected. I first bought the system when it was released in April but returned it because it was MISSING features like chimes and separate entry delays for door/window sensors that I was used to with my previous systems. But then I read that chimes were coming in an upcoming release so I repurchased in June - and then the problems started. From day one I had window and door sensors randomly showing up as offline in my notifications - and then they are magically back online. I suspect this was just an over-zealous reporting of signal loss between the hub and sensor, but try to explain that to the wife who is concerned about her safety. (never saw that with my Honeywell security system).
I consider the issue with my different camera’s showing up as Offline being an issue since day one. This is another one that I don’t understand - why do they randomly go “offline” and the only way to fix it is to go up on a ladder and unplug them? Maybe that is not technically with the HMS, but it is part of my security system and something I have to again keep making excuses for. That seems so simple to fix in software - they are not offline so why show me a cloud with a slash?? Oh well! Just another bug in what should be stable hardware/software.
Sorry for the rant!!
@TextMan thanks for the clarification, I understand what you mean now.
@Customer I was never happy with the risks that came from professional monitoring (using Noonlight and having law enforcement dispatched unless I explicitly said not to every time there is an alarm). I always wanted improvement toward self-monitoring (alert me and let me decide if I’m calling law enforcement or pressing the panic button…so active vs passive dispatching to reduce false alarm fee issues), but I wasn’t complaining about bugs (early on there was an Alexa trigger bug I advocated for though, but that got resolved) as much as I was begging for improved features. It worked pretty well as it was designed, I just wanted the design to be updated to be better. Here’s my original list of all the things I thought the HMS should consider improving since it launched. Almost all were feature requests, not bugs. So when I say it worked flawlessly at launch, I meant in the context of bug-free…the sensors triggered, everything was fast, great reception, very reliable and consistent and stable, that sort of thing. It needed more features to be highly competitive and prime time, including schedules (which it has now and I use every day), geofencing, rules, and many other things I listed in that link…there are still a lot of improvements that should still be made, but the only things worthy of Fix-it Friday (bugs not feature request wants) are 1) the ongoing low-volume bug and 2) the bugs introduced in the March Firmware (which I did not upgrade to and am not experiencing myself, but am still advocating for to be resolved) and have been reported in the previous fix-it-friday, but for which few people have answered all the questions for in Wyze’s response (the response of how to help them find what’s wrong went basically ignored by users as far as I can tell). I hope that clarifies.
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.