Added support for Person Detection on CMC videos using Cam Plus
FIXED ISSUES:
Fixed an issue which may cause pixelated videos
Improved Wyze Sense and Bridge stability
Reduced noise volume during live streaming
Changed the Wyze Cam Pan tracking to function like the 5.111 firmware version
Fixed an occasional issue that caused 12-second videos to be 13 or 14 seconds
Fixed an issue that could cause night vision to keep switching on/off during dusk
Other bug fixes
KNOWN ISSUES:
There might be video frame dragging during live streaming
SUGGESTED TEST AREAS:
Person detection with or without Cam Plus
Video quality
Wyze Sense and Bridge stability
Bulb:
Version: 1.2.0. 273
WHATâS NEW:
Added support for Sleep Routines
Added support for the Reconnect Button for offline bulbs
Improved logs
SUGGESTED TEST AREAS:
Sleep Routines
Reconnect Button when the bulb is offline
Band:
Version: 1.0.7. 44
NEW FUNCTIONS:
Added Google Fit and Apple Health data integration
Added a freestyle exercise mode
Added support for 12hr/24hr time format change
Added support for red dot notifications
Added support for changing screen light duration
Added a reminder for multiple device logins
IMPROVEMENTS:
Increased the number of available Shortcuts from 5 to 10
Improved the customized clock face
UI improvements
BUG FIXES (ANDROID ONLY)
Fixed a time zone bug
Fixed a crash issue when lacking location permission
KNOWN ISSUES:
Previously, if there were multiple phones logged into the same Wyze account and one of them is paired with Wyze Band, it could not automatically un-pair when the user used a different phone. With this release, there is a new popup that will allow users to pair the band to the current phone. However, it does not work if Wyze Band was connected to an iOS device. In that case, you will have to manually delete the Bluetooth connection from that iOS device and then it should pair to the current phone.
When the time format is set to 24 hours, it does not yet apply to other pages in the app (weather, heart rate, activity, etc.).
On Android only, authorizing or removing the Google Fit data sync does not trigger a popup when the phone is offline and the sync setting change actually failed.
This new Firmware fixes HALF of a previous issue, but not the other half of the issue.
I tested the Contact Sensor âis left open/closedâ Notification Issues from the previous firmware. See the following threads for more info on this issue:
This new firmware fixes PART of the issue. If you already set up and saved the âIs left open/closedâ notification while your camera was using a previous firmware build (ie: v.4.9.5.111), this new firmware (v.4.9.6.135) finally allows the notification to push to your phone! However, you can not make changes to it (you canât remove it, you canât modify the time, and if it isnât already set, you canât have it start giving any notifications for âIs left open/closedâ).
So for anyone who really needs to update/use the âIs left open/closedâ notifications, but still wants to use this newest firmware, your temporary solution is to do the following when you want to make changes to those specific notifications:
Take the Cam the bridge is connected to and temporarily roll back the firmware to 4.9.5.111 [or whatever other firmware you want that allows you to make/save those notifications].
a) To roll back firmware, click on the Cam that sensor is connected to through the bridge. Click Settings (the gear icon). Click Device Info. Click Firmware Version. Click âHave problem?â Select âRevertâ next to the desired firmware you want to roll back to (I recommend 4.9.5.111 which I previously tested).
After firmware rolls back on that cam, select the sensor you want to add or change âIs left open/closedâ notifications for and make your desired changes.
Go back to the cam whose firmware you previously reverted and update the firmware back to the newest version (v.4.9.6.135).
Test the sensor by leaving it open or closed for the set period of time and you will start getting a notification for those now. At least, I do for mine.
So, itâs not totally fixed yet, but at least now there is a workaround to keep using the newest firmware until Wyze gets around to fixing the issue themselves.
Hi All, we found a potential stability issue on the 6.135 camera firmware internally. We havenât seen reports yet but we want to take care of it proactively. We are working on a fix over the night and will re-release for tomorrow. Sorry for the inconvenience! Thanks!
So sorry! Do they show as âofflineâ in the app? Can you tell me the LED light status?
Can you still see livestream via âLTEâ mode? (Please switch to LTE mode since we want to make sure the connection is from outside).
In offline mode we have to use SD card to take camera logs. Can you take out SD card and re-insert SD card into your camera? After hearing two chime sound, there will be a log_XXXX.txt file in the root directory. I would like to take that file for investigation. Thanks a lot for your help!
This is what it looks like in offline/LTE mode, I donât know what the LED light status is because I currently have them both mounted. Also it doesnât have SD card.
@WyzeTao I updated the pan camera to the latest 4.10.6.136 and I am noticing several issues:
Severe pixelation whenever the camera moves
The camera movement is âsmoothâ to some extent. In theory I like it better than the abrupt movement of the 5.111 fw, but in the changelog you said that the tracking function is supposed to function the same as 5.111 (from which I just came) and they are definitely different.
The camera completely ignores the detection area I set and it starts motion tracking anything that moves. Also, this differs from the 5.111 firmware, where the detection area was honored.
I donât show as offline to any but have bad pixelation and canât connect to a few of my cams. I mean like it just loads and loads but doesnât connect. Please help
The pixelation issue is the video dragging issue in our release note. we are still working on it.
We will check the tracking difference. We set the settings the same with some code being rewritten. We will take a second check.
If you have detection zone set, the first movement will come from the detection zone. Once motion tracking started, we will âignoreâ the detection area. That is our current design. Think about the case you are monitoring your door. When someone comes into your door, it will have an event generated and then follow the person. Once pan starts tracking the previous detection zone is not effective anymore.
One of my v2âs were constantly rebooting (like only alive for a 5 seconds, reboot, repeatâŚ) with 4.10.6.136. I downgraded the firmware, upgraded again and now itâs behaving. Just FYI.
thanks! You are not supposed to power cycle it. If it happens again, It will be super helpful if you can check LED status light and use SD card to take a log. Thank you in advance!