Just checked my Wyze cameras V2 and Pan and the outdoor cam still not working with google hub now I am getting SORRY IT LOOKS LIKE THE STEAM IS CURRENTLY UNAVAILABLE FROM CAR PARK all the rest of my cameras say the same Wyze is not listing they have the problem they are not fixing the issue getting the cameras to work with google my cameras use to work with google right now I want be buying any products from Wyze because off this issue plus I will be canceling 2 off my pre-orders from them like the doorbell guarantee want work with google and the Wyze headphones Wyze wants our money and donât care if will have any problems with they products
All I want to be able to do is turn on/off my cam V2s and on/off notifications without using/paying for IFTTT Pro. I currently canât do this with my Google Assistant. I donât care to view a stream of my camera from my TV. If I need to view anything it will be from my phone when I get an alert.
I get that nothing in programming is simple and thus I have patiently waited for resolution. The addition of a cost to IFTTT has given rise to my frustration over the lack of Google integration. Not enough of a problem, I guess, because I pre-ordered the doorbell cam, though now I have to decide if I want to pay for person detection per camera on my growing number of cameras.
The primary reason may of us bought into the Wyze Community was because of the low barrier to entry. I have enjoyed the devices but my frustration with the services, or lack thereof, continues to grow. Please do more with Google Home Automation.
Yea Yea Yea We have only had over a thousand people on this forum already state that its now getting old just get use to it. Who knows if they will ever fix it
Over a year and a half just to find the problem? Thats just a way to say âwe will start to take this serious from nowââŚ
At least they made this problem official, but with zero extra or new info⌠we just have to keep waiting blindlyâŚ
Weâre sorry and we understand the frustration. This is one of those things that we wouldnât be able to find without the Google teamâs help. Now that we know what the problem is, it will hopefully be easier to fix. But this is still probably one we canât fully resolve without Googleâs help since there actually was a change on their end.
To all those complaining, what theyâre trying to say is that Googleâs prioritization of a third party companyâs one-off issue, whom they make no money from, is about as high as you having an issue with Gmail on your iphone and wanting the time of their development team, at likely many hundreds of thousands of dollars a day in labor and lost productivity; basically next to nothing. Wyze is basically willing to work towards redeveloping the basis for how their video feeds fundamentally work to resolve this issue for us all, and all so your subscription free $39 camera will support a feature outside of itâs primary purpose and which likely is only used by a very small niche of its user base. I think theyâre doing just fine personally.
I keep reading the replies in this thread and am astounded at how people are acting. Iâm sure that Gwendolyn and Frederick share your frustration in this not working. The thing is they are the face of Wyze here and itâs got to be very challenging navigating all of these negative comments and non-constructive posts. I am 100% certain with my previous interactions with both that they are doing everything they can to resolve the issue. It seems that some folks posting here believe itâs a quick easy fix, but at the end of the day, if it was it would already be resolved. A little patience will go a long way. Or move on to a new device. I agree that it stinks that works with google is claimed and itâs not actually working as expected, but at the end of the day, if thatâs the deal breaker for you then move on. Iâm sure that it wonât be the first time or the last time that you have had to take a bit of a loss to move on from something, and maybe thereâs a middle of the road solution that Wyze can offer to those who reported issues during warranty periods / return periods of GA not working, and that could help, but I just wish that some people would think before they respond.
Most users here have patiently waited over a year for a fix so they have had time to think about their comments.
My frustration lies in the way this was handled. Ignored and pushed off. There was no concern about this on Wyzeâs end, or at least the faces of Wyze didnât seem to show it here. I offered videos of why was happening (when we were told it was working) but I was not taken up on my offer.
Something like this should not have taken this long to:
A. Be acknowledged
B. Taken Responsibility
C. Provide accurate and timely updates
D. Be corrected
Iâve patiently waited just as long, and my use case is as a baby monitor. Iâve always received responses, and of course the issues escalated here to the point that weâre getting the responses on the specific project for fixing the issue. I really donât believe it was ignored or not acknowledged when I initially reported it, I got a response that it was under review and was definitely acknowledged at that time over a year ago. I donât believe Iâve seen a single lie from anyone on the wyze side, can you elaborate?
If this was a main feature of their product, Iâd agree with you, however thatâs not the case here. Wyze is clearly looking to broaden their market into other products, and redeveloping the basis for their video feeds so that you can âOk Googleâ it onto your 3rd party screens, a feature they never claimed to 100% support, is just not the priority theyâve chosen to pursue. What percentage of their user base do you think cares about this at allâŚ1%? 2%? I think even those numbers would be generous. You canât expect a company to devote more of itâs resources to an issue than it affects its user base, when the rest of the majority have equal interest in seeing their development cycles attend to other areas. Have you not been paying attention to the massive âperson detectionâ setback they experienced and have been working on, that affects the vast majority of their user base, which theyâve recently handed us all for free, as they said they would? Do you really think that your issue was more important than that?
As it has been said, if you donât like the fact that this issue isnât being given 100% of their attention, feel free to move on to another platform, but declaring that something was handled poorly from your own biased point of view doesnât make it so. I too am having this issue, but I realize that my $39 investment, for which all the primary functions theyâve advertised work just fine, doesnât give me license to tell them how to run their business. Take the silver spoon out of your mouth and realize that Wyze doesnât owe you a timeline or an explanation on this issue, despite them graciously trying to do so here in the comments to the best of their ability over and over again.
Agree to disagree here, but if you say I have a biased point of view, then I could say the same for you.
This was advertised to work, it was listed on each box of the 5 cameras I have purchased. So my investment was a bit more then $39.
Point is, it was advertised on the product, and here that it worked, and it doesnât.
I think part of the issue is the Wyze staff positing here was posting to try and keep people satisfied, not actually keeping us truly informed. Thatâs likely because they might not have been informed on their side.
Remember the few posts where someone would come in and say, âhey itâs workingâ then the Wyze agent would chime in and say, âyea! I will let the team know.â Even when it wasnât working. - That right there goes to show lack of communication.
I was a Wyze supporter for a long time, and have recommended it to friends and family.
I donât have a silver spoon, but if you would like to share yours without throwing a fit, I might see what itâs like to have one.
Many here already extremely patient and waited one year and a half for something so trivial that all other brands have no issue with. Please stop being defensive for a company that has no ability to fix a issue that are supposed to be working . I do sympathize Wayne who needs to deal with the complaints daily but hey this is real world . The amount of complaints shall be made known to upper management and not telling people to keep quiet .
[Mod Edit] The issue is completely dependent on Google and has nothing to do with Wyze. When people say it works in the comments, it may have started working due to a temporary change Google made on their end, and then stopped when they changed it back. Again, that has nothing to do with Wyzeâs internal communication, as they get more feedback from us here on this forum post then they likely do from Google, which Iâm sure is nothing at all.
They hooked into the âWorks with Googleâ API that every other company does in an effort to bring more value to their customers, unfortunately for them Google just isnât providing stability due to the way their video streams currently function, as Google could care less about fixing this in a timely manor. The silver spoon Iâm referring to is that clearly you have no appreciation for what a companyâs development time is worth, and given they have no ability to fix this without Google, but for the option to completely redevelop the way their feeds work, they have to carefully weigh whether or not it makes sense to devote such time & resources to an issue such as this over further progressing their company. They advertised the âWorks with Googleâ function due to having hooked into the same API that every other company does. If Googleâs API doesnât work or isnât stable, go bash Google and get on their case. Keep dragging Wyze through the mud over it and I think youâre going to get your wish that they simply drop support for Google altogether.
but hey this is real world . The amount of complaints shall be made known to upper management and not telling people to keep quiet .