Wyze App 2.24 Beta Test (Android); Wyze Cam v3 Beta Test 8/23/2021

I did a force stop of the app this time and checked the connection. I could connect about 15 minutes ago. Just checked now and It is still connecting at this time. I will check later as well and let you know.

Is there something you would like me to try? I have 2 extra v3’s and was thinking of changing it out, but also don’t want to do this if there is an issue with the FW or App.

Thank you so much. Please let me know if the Driveway V3 disconnects again, which will be super helpful for us to investigate the connectivity issue on the new firmware. :handshake:

1 Like

Just one other note, forgot to mention, my apologies. I also tested to see if it would stream in HMS. So I added it as an available camera to HMS, then clicked on the “More” link. The Camera page was shown and the Driveway Camera was nothing but a Grey Box. If you want, I can take a screen shot and show you. May be related as well.

Thank you for the update! The screenshot will be helpful. BTW, do you also have the screenshot when the driveway V3 can’t connect to live stream?

Yes, just happened again… Did a screen shot and trying to submit the log.

Here is what Happened:

  • Tapped on Camera to load the Live Feed
  • Got to Step 3 of the process - Getting image (I think)
  • Timed out and restarted the logon Process again. This Time it got connected.
  • Then I just tried now at 6:05pm and it did not get passed Step 1.

New Log # is: 283492

HMS Issue with Driveway Camera:

  • Added the Driveway Camera
  • Image with it Shown in the main screen

  • Went into the Camera by Clicking “More” and thought it was going to work. 2 seconds of stream it stopped

  • Closed the App and went back into it to see what would happen. I get the Grey box

2 Likes

Here’s what I found…

When beta 4.36.5.58 was announced, all of my v3 cams were running beta 4.36.3.19 with no issues. I decided to update half of my v3 cams to 4.36.5.58. When I ran the individual firmware updates (not bulk update) on each cam, 4.36.5.58 was directly applied to 4.36.3.19 (no incremental staging). All of my v3 cams running 4.36.5.58 except two immediately experienced time stuttering, rebooting multiple time per hour and severe live stream issues. These issues occured only between sunrise and sunset. All affected cams ran perfectly between sunset and sunrise. Some of the affected cams autoswitch to night vision after sunset, some have NV mode off. Some run IR on at night, some don’t. All cams are running Cam Plus.

At sunrise this morning, all affected cams began having issues so I decided to flash two affected cams back to 4.36.3.19. I live streamed both cams for 3 hours with no issues encountered.

I decided to update both cams individually and found that instead of jumping to 4.36.5.58, the update applied was 4.36.4.4. I live streamed these cams for 1 hour and they were stable with the only problem encountered being that the time wouldn’t sync.

I decided to update both cams again, this time to 4.36.4.20. I live streamed the cams for an hour with no problems encountered. Time sync worked under this 4.36.4.20 update.

I decided to update both cams again, this time to 4.36.4.24. I live streamed the cams for an hour with no problems encountered.

I decided to update both cams again, this time to 4.36.5.58. I tried live streaming the cams, but both immediately suffered time stuttering, rebooting multiple time per hour and severe live stream issues.

After an hour of issues under 4.36.5.58, I decided to go back to 4.36.3.19 and incrementally update both cams up to 4.36.4.24. They have been running flawlessly for the past 4.5 hours.

It’s 15 minutes past sundown here and upon checking my problem cams that are still running 4.36.5.58… they are back to running perfectly… because it’s past sundown.

What have I learned?

  • The issues are somehow tied to sunrise/sunset. No issues surface between sunset and sunrise.

  • The issues are not related to heat. It is in the low 70s here at sunrise climbing into the 90s during late afternoon. Half of my affected cams are located indoors where it is a constant 72F degrees. The other affected half are outside in shade. Cams that I never updated are running 4.36.3.19 and in direct sun and have no issues. The 2 cams that I updated to 4.36.4.24 this afternoon ran flawlessly in direct sun at 95F degrees.

  • Other than being in the middle of a boot cycle, all affected cams write to the SD card fine and playback is not affected.

  • Other than being in the middle of a boot cycle, uploading Events and AI processing is not affected.

  • I have no idea why 2 of my cams are running 4.36.5.58 with no issues whatsoever.

  • The last known problem-free firmware version is 4.36.4.24.

  • When 4.36.5.58 was 1st pushed, we were at 4.36.3.19 so the update path was: 4.36.3.19 > 4.36.5.58

  • Today the update path is: 4.36.3.19 > 4.36.4.4 > 4.36.4.20 > 4.36.4.24 > 4.36.5.58

Summary of today’s testing:

  • 4.36.3.19 stable
  • 4.36.4.4 stable, but time sync fails
  • 4.36.4.20 stable and time sync successful
  • 4.36.4.24 stable and time sync successful
  • 4.36.5.58 severe time stutters, rebooting, live stream issues

Hopefully, you find something meaningful in this. I’m leaving all cams as is until the next update. I have indoor and outdoor v3 cams running 4.36.3.19, 4.36.4.24 and 4.36.5.58. If there is some scenario you’d like me run to help debug, please let me know. I’m online every day multiple times per day.

6 Likes

I am also seeing issues with continues recording not working on one of mine as well. Maybe it is also rebooting.

@WyzeBaohua , happened again today. Here is my log for the connection issue: 284044

Happened around 2:50pm Eastern Time on my Driveway Camera Again.

1 Like

I am flashed back to production firmware and one hour in so far so good I will report in 24 hours.

2 Likes

I agree, 4.36.4.24 was most stable release Beta of late. :slightly_smiling_face:

1 Like

How do I update to THAT version " 4.36.4.24" now?

Its not possible, you either have to run the current beta or the most recent (or earlier) production. They do not keep previous beta versions up for download.

2 Likes

Obviously they should so we can roll back when problems exist. And you should be able to pick firmware’s to install in the app.

All the best,

Joe

2 Likes

Happened to have kept a copy on a uSD card. Best suggestion is jump out of Beta for now and use the release production software (linked here)
You can go back to the newer Beta version once it becomes available.

3 Likes

It’s a bad idea to keep old betas up as they almost always have issues.

2 Likes

Many new error codes this afternoon with one of my V3(4.36.5.58). With so many reboots, I’m not surprised.:smirk: Log sent.

Since I tested betas, I would say this one is the worst of all






image

@WyzeBaohua

2 Likes

Yep this has been a bad firmware! Hopefully a new one will come out soon.

2 Likes

Remember guys, it is beta software, there will be bugs

4 Likes

Hi Seapup. Thank you so much! I really appreciate your testing and analysis. For your V3s running 4.36.5.58, could you PM me some SD card log after you see the rebooting issue with the corresponding MAC of that device. Also, could you send me a screenshot of the Playback page that shows the time periods of rebooting.

To get the SD card log, you can pop out the SD card and re-insert it into the camera. After two chime sound you can take out the SD card. On a PC/Mac with a SD card adapter, please put your card inside and send me the log_XXXX.txt file under SD card root directory.

Thank you so much.

3 Likes

Hi gyzmo. Thank you for posting the issue. Could you also send me a SD card log of that V3 after you see the rebooting issue?

To get the SD card log, you can pop out the SD card and re-insert it into the camera. After two chime sound you can take out the SD card. On a PC/Mac with a SD card adapter, please put your card inside and send me the log_XXXX.txt file under SD card root directory.

Thank you!

3 Likes