Congrats. Alas, my V2 cameras do nothing. Google responds with ‘it looks like the stream is unavailable.’ Have checked the firmware version (up to date). Streams to the app OK.
All,
Some progress.
We have deployed a fix to production to address the cold start connectivity. Tests in and outside of the labs have shown serious improvement but I’m not ready to call it a complete fix.
Would you mind testing testing the streaming on the google Nest Hubs and Chromecast?
Everything should be working properly WITH sound.
Please let us know your experience.
Thank you!
5 Likes
That’s a negative here, after spinning for 45 seconds, I get this lovely screen on my Hub. I tried 5 different cameras.
I should add that none of them are Outdoor Cameras, even though that’s what is pictured.
Google nest hub cold start took 20 seconds. Hot start 6 seconds. This was after updating the camera firmware to the latest beta firmware.
Wow! That’s a new one. I will provide the feedback to engineering right now.
Thank you for testing!
Mine started streaming in about 10 seconds. Still getting streaming breaks every few minutes, but so far the steaming restarts within a few seconds. Whoops, just stopped steaming and lost connection. Had to manually restart the process.
I would say the connection is still not reliable. My nest camera can stream for 24 hours without losing connection.
1 Like
I tested with about 5 cameras using the cold start method. It took about 20 seconds to get up and running, but it did eventually start and was the standard ~10 seconds behind realtime. I wasn’t able to test sound because there was no sound on the cameras at the time. 4 out of the 5 cameras performed this way, but on one of them, it failed to load and I was given the same outdoor cam graphic that @wolfcorner was given above. I’d gotten that graphic multiple times in the past weeks when trying it as well so it’s not just new for me tonight. I’d say it’s overall more functional, but still not without its issues as you already suggested.
1 Like
All testing done on a Google Home Hub (7", not Max)
- My front V3 cam loads within 15 seconds (but couldn’t test the audio)
- Back of House V3 cam loaded in 22 seconds (but could not test the audio easily)
- Office V2 cam, and it failed (twice…once cold but also the warm start failed right afterward).
- Family room V2 failed
- I tried my kitchen pan cam - it loaded with sound (seemed like it took well over 15 seconds to load though…my wife and baby were distracting me so exact load time unknown…I just knew it loaded when he heard ourselves laughing through the Google Home Hub)
All tests were cold starts (except the one warm start that also failed).
I could test more later if needed (need to go do something right now)
Limited data conclusion: My V2’s are failing, my V3’s are working.
1 Like
Thank you for your very detailed explanation of what is currently going on in your software Department. I am running 11 Wyze and 5 Arlo cams at my home and 17 each at two other locations so I am a True Believer in your products, and have been with you since the beginning.
I am however GREATLY DISAPPOINTED in your programming staff and their continued inability to deliver error free updates, and in particular to understand how to write a simple interface for an application to view the cameras on a windows 10 computer browser! Clearly they came from apple and android environments and have no real knowledge about windows operating systems.
Make no mistake, I love Wyze and plan to continue with them on their journey, but it is very painful to see your programmers choking on quality control and lack of knowledge on industry standard browsers.
I would like to make a suggestion that a solution for Wyze would be to bring in a small team of very specialized programmers for a period of 3-6 months to work with your team in solving all your issues, including adding PC-browser capabilities. You have the income and client volume to justify it, and the possibility of doubling your sales. At the end of that contract period your product capability will be second to none in the industry, and google and alexis will be promoting your cameras to their clients.
In the 1980’s I founded a business software firm with 14 different products, and did EXACTLY THAT. In less than 6 months We had new contracts with 20 different hardware companies and went on to establish our own network of 425 dealers worldwide. Worked for me, and our programmers were able to greatly improve their capabilities.
Of course back then we had to switch out programs all within 64kb ! I also think that if you could get your suppliers to ADD 50-100% more internal memory for a couple bucks your code was not so limited, and your programming difficulties would disappear
It’s just a suggestion but I feel you might be able to clean up a lot of issues in a very short period of time
Best wishes for 2021…
2 Likes
So updated to latest firmware this am
tried 3 V2 cams
cold start 15-20 sec but stream after starts w/o buffering 10- 12 sec behind the app
hot start ~ 5 sec again with consistent stream
switch between cameras time depends on cold vs hot start same as above
all were viewed on original google home hub
biggest difference is consistent stream after start
really need to get this to work with the doorbell…
1 Like
took forever to load & is constantly refreshing
1 Like
Thanks for continuing to work to improve this and not giving up.
Tests here with a Chromecast (3rd gen?) gave a mixed bag of results:
Cold start to a V3 worked and started in about 10 seconds.
While that was still streaming I asked Google to stream a different V3. That other V3 didn’t start on the first request. It took a hot start to get it going on the 2nd request.
In general it seemed if I had a stream going from one camera and requested another, that switch took two requests to be successful. The first request stopped the preceding stream but failed to start the second. The second request successfully started the second stream.
I have a mix of V2’s and V3’s. The above behavior seemed pretty consistent.
As for latency, it seems to be about 15 seconds. Sounds is working. 
1 Like
My v2s and pan cams required hot starts on my Google Home display, but then they started streaming pretty quickly and the quality seemed to be good and included sound. My v3s required multiple attempts to actually start. Once started, the quality was not so good, and the stream would cut out every few seconds. The streaming experience on the v3s is still pretty terrible.
1 Like
Tried it again this morning with my v2 cam and all I get is the outdoor cam graphic. The camera streams fine in the app.
Hi just tried my V2 and V3 plus Pan they are not steaming on my google hub or my Amazon Alexa never had any problems with Alexa just happened today what a joke even the Chinese nock off work with google and Alexa Wyze can’t do nothing simple getting they cameras to work with google now Alexa
MR GIOVANNI TURCO
1 Like
So during the development, we could not use the default message and a picture of the outdoor cam has been inserted instead. We will create a new default screen in time but for the moment, seeing the the outdoor cam means that the stream cannot be loaded as you have already guessed.
1 Like
For people that had some issues following my last, message. would you mind doing a quick retest again?
Engineering found a certificate that was not right and was failing the connection.
thank you!
2 Likes
I just streamed all three cams too my 2nd gen chromecast with pretty similar results on each.
V3 - 20-30 sec cold start, no sound present at cam to test. good playback, about 10~s behind
V2 - 20 sec cold start, sound worked great, about 10~s behind
Pan - 20 sec cold start, sound worked great, about 10~s behind
I did have a few issues as I played around. Chromecast does not like to switch from cam to cam, it freaks out and stops all playback every time. My G Home mini gets the request right about 2 out of 3 times. When it goes stupid, it gives me YouTube video choices.
Overall, considering this is with ViaSat internet, I am impressed. The satellite must have been perfectly aligned and the frost must have given it enough boost to beat dialup…
1 Like
All of mine worked now, took about 20ish seconds to buffer and load. When it did load, the camera feeds were ~10 seconds behind real-time.
All tests conducted using Google Home Hub (7", not Max), saying “Hey Google, Show xxxx Cam” and pressed start on a stopwatch right as soon as I finished speaking the command, and here are the results:
- V3 Front cam Cold Start (SUCCESS) - Load time 27 sec. latency unknown (different room, sound untested) - Ended stream automatically after 52 seconds run time
- V3 Back of House Cold Start (FAIL) - failed to load, ended stream automatically after 40 seconds
- V3 Back of House warm start (2nd total attempt) (FAIL) - failed to load, ended stream automatically after 12 seconds
- V3 Back of House warm start (3rd total attempt) (FAIL) - failed to load, ended stream automatically after 49 seconds
- V2 Family Room (SUCCESS) - Load time 30 sec.; Latency untested (different room, sound untested) - Ended stream automatically after 47 seconds runtime.
- V2 Office Cold Start (SUCCESS) - Load time ~20 sec. 15 second Latency (sound working) - Ended stream automatically within 30 seconds runtime
- V2 Office first Warm Start (2nd total attempt) (FAIL) - Failed to load, automatically ended attempt after 44 seconds (returned to main screen).
- V2 Office second Warm start (3rd total attempt) (SUCCESS) - Load time 11 sec.; 15 second Latency (sound working) - Ended stream automatically after 1 minute 41 seconds run time.
- Pan Cam Kitchen Cold Start (SUCCESS) - Load time 31 sec - Ended stream attempt automatically within 33 seconds runtime (stream canceled within 2 seconds, so too short to test latency)
- Pan Cam Kitchen Warm Start (2nd total attempt) (FAIL) - Failed to load, automatically ended attempt after 32 seconds (returned to the main screen)
- Pan Cam Kitchen Warm Start (3rd total attempt) (FAIL) - Failed to load, automatically ended attempt after 33 seconds (returned to the main screen)
- V2 Den cold start (SUCCESS) - Load time 26 sec.; Latency = 11 seconds (Sound working) - stream lasted for 7 minutes and 50 seconds before the first buffer interuption (which only lasted 1 second before returning the stream), then it finally ended the stream automatically after 7 minutes 56 seconds total run time. A definite big success!
- V2 Piano room cold start (SUCCESS) - Load time 31 sec.; Latency = 14 seconds (Sound working) - stream lasted for 1 minute and 9 seconds runtime before the stream automatically ended.
- V2 Backyard cold start (SUCCESS) - Load time 26 sec.; Latency = 11 seconds (sound working - told car horn to honk) - stream lasted for 3 minutes and 48 seconds runtime before the first buffer interuption (which only lasted a second before returning the stream), then it finally ended the stream automatically after 7 minutes 36 seconds total run time. A definite big success!
That should be helpful for now, I do have more cameras and could always retest the same ones again too, but this gives a little bit of an idea. I do think the certificate update helped!
That’s a significant improvement, to be sure. Still some room for improvement though. Seems like the Web RTC you’ve been working on could make a significant improvement on some of it. I also have an older generation Chromecast I could test on, but I usually use one of my two 7" Google Home Hubs).
Another interesting observation is that it can’t be blamed on the signal strength/connection to the WiFi because the cameras that performed the best are actually the ones with the lowest connection to WiFi (I have used AR to map the WiFi signal strength to every area of my property, both inside and outside the home). It was the cameras with the strongest, best connection that actually performed the poorest in general, and those far away with the weakest signals (den and backyard) that lasted a long time with few issues…so it is not the signal strength.
Thanks @Frederik for updating us as to progress. That’s exactly why I’m subscribed to this thread. Happy to help.
2 Likes