If this is your first Fix-It Friday, welcome! For background, while our communities are not designed to be a replacement for Wyze Support , our community members and community managers do our best to help you out here. As our communities scale up, we want to make sure that any outstanding bugs or issues that you folks are facing are on our internal radar and that weāre transparent in our process of working on them.
Hereās how this works:
Weāll make a post on the first Friday of the month in every community (Core Community on Facebook, Forums, Reddit, and Discord).
Check the comments. If you see any other comments with issues that youāre facing, vote for them with a like (the heart button at the bottom of their reply)
Got something new? Reply to our post with the top issue that youāre facing this week with your Wyze products to help loop us in.
Weāll grab the top comment from each community and make a follow-up post on Monday to detail what those issues are and how we plan to fix them. If we need more info from the community to help figure out whatās going on, weāll let you know on Monday - so please make sure to take a look!
The following Mondays in the month, weāll be posting updates about our progress on Fix-It Friday submissions.
Sometimes Mondays are actually Tuesdays if we donāt get all the info we need on time for posting on Monday. Our apologies!
Remember, this is for existing things that arenāt working right. If you are looking for a new feature or for us to add functionality thatās not already available, please use our Wishlist instead!
Weāre constantly working on improvements for everyone. But we hope that this process will both help us prioritize issues that are important to our communities and help you feel more in the loop.
Got a request for something new or an additional feature? Check our Wishlist to see if itās in the works or has been requested.
If you want to see how this works, you can check this previous Fix-It Friday post:
Dad!@Crease keeps hogging the first three posts again! Make him stop!
Son, we cannot fault Crease for being Johnny-on-the-spot. He is setting a standard of alertness and alacrity you must simply strive to beat. Everyone stands to benefit by that.
I donāt know about that; however, I appreciate the āvoteā of confidence. Sometimes I feel like Iām the only one really using the Watch regularly and wanting to see it improved (including one from last month that I intend to re-post). Iām posting and voting for things that have the potential to benefit me-ME-MEEE!!!
@Letsgowize, I havenāt experienced that issue, myself, but Iāll read the topic and see what happens when I dig into it. If I can replicate the issue myself, Iāll be happy to give this one a . (Unfortunately, I donāt have any Cam v2s to be in @peepeepās boat, though I certainly commiserate with the frustration.)
Wyze App for Android is Still Telling Me About iOS
This persists into the latest Android app update, v2.50.5 (449), which finally became available in Google Play Store today.
If youāre going to be making actual functional changes to the app from time to time, then adding some grammatical/cosmetic (minor) changes shouldnāt be a problem. Just put 'em on the list, including this (if it hasnāt already been done):
***When clicking on microSD from the Event Tab it says there is no microSD installed
The engineers are looking into this. If this is happening to you, can you submit a log and let me know the log number?
In the Wyze app, go to Account > Wyze Support > Submit a Log. Select your device from the dropdown menu. Then fill in the description box with the date, time, and time zone of the most recent time you noticed this issue and a description of whatās happening. Make sure the Send Logs option is selected and then submit your log. When you have the log number, please post it and tag me so I can get it to the right folks.
I wanted to make sure this got moved from the April to May Fix It Friday so it is still on the Wyze Engineering Teamās radar.
This has been an annoyance for as long as Iāve used the Watch, but the only mention of it Iāve found so far is here:
When I receive a regular SMS message on my phone, the Watch thatās paired to it shows a notification that I can glance at to see the content of the text message. This is the expected and desired behavior.
When I receive a Skype IM on my phone, the Watch shows two notifications in rapid succession:
a notification with the text content of that message, followed immediately byā¦
a second notification with the meaningful information being only the senderās name.
In experience, it looks something like this:
Others [Message Sender] [Message Text]
ā¦immediately followed/overridden byā¦
Others
1 new conversation
Last message: [Message Sender]
That second notification overtakes the message that I actually want to see. If I want to read the actual message on my Watch, then I have to swipe this second notification away, swipe down to show the notifications, possibly scroll to the notification with the message text in it, and then tap to select that previous notification. This behavior is neither expected nor desired.
Iām fully aware that what Iām reporting and asking to be fixed isnāt where Wyzeās focus is right now, but I do wear this thing almost all the time and interact with it multiple times per day. Iād hate to think that at this point itās become a piece of abandonwareāor abandonwear, as the case may beāand Iād like to see this very useful little gadget get some love, too! Iāll keep my that someone will want to bundle up a bunch of Watch fixes at some point and release a firmware version that doesnāt start with zero (and, yes, Iām fully aware that different developers use different versioning schemes, but something thatās v0.xx.xx still leaves me with a pre-beta feel).
07:00
Dad! 
Son, we cannot fault Crease for being Johnny-on-the-spot. He is setting a standard of alertness and alacrity you must simply strive to beat. Everyone stands to benefit by that.
. (Unfortunately, I donāt have any Cam v2s to be in 
Others
that someone will want to bundle up a bunch of Watch fixes at some point and release a firmware version that doesnāt start with zero (and, yes, Iām fully aware that different developers use different versioning schemes, but something thatās v0.xx.xx still leaves me with a pre-beta feel).
