The people responding here are NOT Wyze employees. We are all users like you.
If a person says, “yeah, but you can run most of the tests automatically and fast for each test case instead of a human testing each case.”
A person saying this is also unaware of the complexities of testing programming. They probably never heard the phrase, “That test case isn’t loaded in Jenkins” Automation is only as good as the test cases loaded… and since test cases are based on inputs from people you can never account for each and every scenario. It’s why betas exist. As a way to capture scenarios and setups that no one lab could ever cover. This isn’t an exclusive “sneak peak” VIP experience for these devices, expect highly variant behavior while implementing new features.
Thus the “error code” was born to display when a process goes awry.
Not sure where to post this but my wyze cam pan on 220.127.116.115 has maybe double/triple speed playback. I’ve tried restarting the device but playback is still sped up. Anyone else have this issue or know how it might be fixed?
Well said. I was of course mostly trying to keep everything very simplified while still making a clear point that even if it was possible to run through every possibility in a number of cycles, it’s still impossible to provide any guarantees even for the simplest of programs.
Your explanations helps point out why it’s even more complicated than how I simplified it. Like you indicated, a lab setting can never possibly account for the differences of so many other things including environmental differences. Some obvious examples including internet ISP and router differences, interactions involving numbers of other devices, and unlimited other things that can potentially affect things that they have no control over.
Sounds a lot like what has been happening to one of my cams since November. I even had a Wyze employee who started to look into this issue, but we needed other examples of it happening, and usually when I found someone else this was happening to most of them just ghosted me and didn’t answer the questions I had, so eventually my post just closed up, and it went nowhere, and there was nothing Wyze could really do because too many people experiencing the problem wouldn’t cooperate or answer simple questions or submit logs. I think Wyze mostly just wrote it off as “you probably have a weak connection to your WiFi” which is 100% not the problem as I outline quite clearly in my original post.
Anyway, review some of the following threads and see if that is what you are experiencing. I am not sure if Wyze will do anything about it or not since nothing has been done about it since November, but if you do submit a log, I recommend referencing my original post or logs so they have a reference point with a good explanation and clear testing.
Thus the “error code” was born to display when a process goes awry.
I also love the fact that “computer bug” was a term created because an actual bug got into one of the first relay based calculators. A moth shorted a relay causing errors in the computations. The quote in the log book: “First actual case of a bug being found”
Had the A/C condencer fail couple years ago. Could here the contactor click but fan & compressor wouldn’t start. Opened the unit up and found ants crawing around the contactor. Hundreds had comitted anticide between the 240V contacts acting as an insulator. Guess they got a charge out of it. Still baffles me. . .
Ooo, person detection has returned on my v3s
Looks like we may have identified what the other v3 cam issue is… missing firmware libraries when 18.104.22.168 is “skipped”. Not good. 22.214.171.124 should include the 126.96.36.199 libaries. Some of my v3 cams jumped to 188.8.131.52 without 184.108.40.206. Most of my Alpha v3s are well past 220.127.116.11 and never had 18.104.22.168 either. All end up with no AI, no events, no notifications, app reporting cams offline yet able to live stream. Reference this topic:
Impressive work. Hopefully someone at Wyze is aware of and looking into both of these fairly critical issues.
I am getting person detection on 2 V3’s located outside. The other 4, also located outside, have not received person notifications. The version issue may explain this abnormality.
So, I don’t know if it was the 0.12.49 FW relase for my Watch 47 or whether it occurred with an earlier release but I see that incoming calls now show the caller’s name! And not only that, it shows it in nice LARGE WHITE font so it is easily readable, unlike the almost greyed out, difficult to read font when the name is displayed for incoming texts. GREAT JOB WYZE! This has been a huge complaint for me and now it is fixed! Now if you could sneak a fix for the hard to read name on incoming text into the next update, I’d be really stoked!
I’m not sure it was wyze specifically. A few weeks back I noticed a few of my contacts would show their name when a call came through and others didn’t so I started poking around. When I edited my contacts on my phone, I noticed some of my contact phone numbers weren’t formated the same way as the one that worked. When I updated those numbers so the contact app autoformatting worked, (xxx) xxx-xxxx if you’re interested, I suddenly started getting names when those contacts called.
@vaaish . Good catch! Most of the numbers in my contacts list (Android phone running Android 11) are formatted as 1-999-555-1212 and they do not show the incomming caller’s name. But the ones formatted as (999)555-1212 do show the caller’s name. Looks like it needs the parentheses around the area code. Seems like a bug that Wyze needs to squash, but at least there is a workaround. Assuming, of course, that I want to go the work of reformatting the numbers in all of my contacts, since most are using the dashes rather than parentheses…
And you’re right that it probablly had nothing to do with the FW release. I just tried the same experiment on my wife’s Watch 44, which runs a completely different FW, and the same formatting issue exists on the Watch 44 as well.
I wanted to update you on my issue with streaming. After digging into the issue and trying to isolate he problem, I have come to the conclusion that the issue was basically my network, Let me explain why:
I have / had the TPLink x60 Mesh Network which provided me with awesome speeds and connectivity. All of my network devices worked flawlessly, until my wife started to tell me that she had issues using an iPad in a certain room. That room gets 100% signal, so it did not make sense. Consider it was streaming video’s for my grandson. So to do the test, I removed or disconnected power to all but 3 cameras and did my test and it seemed to work fine. I then started to add the cameras back and started ot experience the issue again. Still made no sense because if no events were going on, the stream was fine. However, I decided the best way to test was to replace my Mesh Network, knowing I could return it if it did not work. So after a lot of research and knowing I wanted to stick with some form of WiFi 6 Mesh Network, I ended up getting the Asus ZenWifi AX (XT8).
I hooked up these new Mesh devices on Sunday last, and ensured they were set up as close to the TPLink’s as I could get. Since they I have had no problem with streaming. I had 6 Cameras with Live Events being recorded and could still connect to each camera and stream live if I wanted to. In addition, my Notifications have increased on all cameras with the exception of my Patio and Porch cam. they catch motion but for some reason CamPlus is not reporting a person. I have sent WyzeShawn a DM on this issue.
But in any event, I wanted to thank you for your diligence in testing and support. I also wanted to keep you up to date on this. This was obscure and something I would not have figured out if it was not for you and others in the community pointing out things to look at and consider.
I will say though, that the flipped V3 issue (inverted) was not just a network issue. There was most definitely a bug that was stopping Person Detection for a while and you both were MAJORLY helpful in getting that identified and resolved. My inverted V3’s have been working great for a while now after someone resolved it. So at least that one can’t be blamed on your network.
Still, I am happy to learn that your other issue was resolved with a new system. I look forward to hear your long term analysis of your new router. Maybe in a few weeks I’ll go buy one of those myself if it’s still working out great! I just dismanted 90% of my Smart home devices while packing up to move to my new house! Now I have to figure out where I’m putting everything…Keypads ripped the paint off my wall, though I was expecting that, they did say they were permanent and would do that. I will have to get a bunch of new adhesive for mounting things at the new house. Fun stuff. Still leaving up a few critical security cams with cam plus until I leave on Friday/Saturday.
Yea, I updated my post to @WyzeQi, I indicated that I am getting notified on upside down camera’s but there are 2 upside down camera’s not alerting on person. I ordered more Mounts so I can mount them non inverted and and will see what happens. They will be herein a few days, so will post an update. I also indicated that I am being notified a lot more and faster on the one Camera mounted right side up. So I do think there is a issue with the Camera being inverted, but have not figured out to what extent. I also sent a DM to @WyzeShawn on this as well as it may be CamPlus related.
It is amazing how that sticker is permanent like that. I have had to repair many spots in the past. Now I use a different sicker until I am sure it will be staying there. Can’t wait to hear about your move and how you have things setup, I will keep you posted and provide an update on the new Router setup.
I jus looked at my Watch 47 and don’t see those numbers. where are you seeing that? Which app is being used to display this info in this format?
Might be an issue with the Syncronization.