Version: 2.2.1.1326
What’s New:
- Improved live stream stability and reduced connection failures.
Installed and connected fine. Will test and verify
1 Like
Installed on half my floodlights. We’ll see if I notice obvious differences
1 Like
I installed this on one of my floodlights and it no longer connects. It gets stuck on Step 2 of 3. The other floodlight pro on older 2.2.1.1223 firmware connects almost instantly, as do all my other cameras. The only things that seem to make it work are power cycling the floodlight or disconnecting my phone from my WiFi. Power cycling only works for about 20 minutes before it can’t connect, and using cellular data only works about 60% of the time.
Both of my Flood Light Pro’s on 2.2.1.1223 did not come back online after initiating the update to 2.2.11326
I waited about 5 minutes for them to come back.
Power Cycle of both did not being either back online.
logs: 2265157 & 2265158
Confusing with your numbering listed here…
Looks like you are going down in versions…
The newest beta is 2.2.1.1326
You went to 2.2.1.1223
That is backwards…
I came to say mine seem fine…
I have 3, and all seem to connect fast.
It shows step 1 of 3, then immediately connects.
BUT
But when showing in groups of 4 or 5, they can take a long time to connect, or fail.
Then minutes after them all doing fine, one fails to connect at all.
Log 2265367 (Viewing cam only)
Log 2265371 (Viewing in group)
Had to power cycle it.
Then a different cam wouldn’t load in the group view of 4 cams:
Log 2265377
And not connect in single view
Log 2265388
Have to power cycle this one too.
So…Darn…
I reversed the numbers, will edit that now, thank you
I factory reset both, and they are back online running 2.2.1.1326
It doesn’t show ‘beta’ next to the 2.2.1.1326, which I assume is by design?
PUBLIC SERVICE ANNOUNCEMENT:
When Factory resetting a Wyze Floodlight Pro, prepare for your heart to skip a beat or two or possibly even stop completely when the camera powers back up and BLARES “READY TO CONNECT” loud enough to wake the dead in the next state over.
Or, if you prefer to not risk your heart stopping, waking the dead, or alerting your next door neighbor of what used to be your discreet flood light (camera), you can hold your palm over the speaker, and wait until the camera gives up it’s existence to anything that has ears.
This might warrant a warning in the dialog with the suggesting to muffle the sound as described above.
3 Likes
This issue continues, still cant connect to these things after viewing them once or twice.
Radio silence from any moderators, mavens, or Wyze Team Members.
@WyzeAndy @spamoni @carverofchoice
1 Like
I have been checking, but so far I’m not able to replicate this on the 3 devices I updated to this firmware. I’ll go load it on the rest of mine to see if I can get it to happen when they’re all on this new firmware.
If anyone else can provide supportive logs for connectivity issues after this firmware update, please post them. It can help engineers to narrow down issues when they see the same thing in multiple examples.
Don’t give up looking when you can connect to a cam once or twice and think it is working.
View one, leave, view another, leave view another, leave, come back again.
Look at them via the web app,
Look again.
After a few times, they start getting unresponsive.
1 Like
Just made them do it again.
Log 2280993
Log 2281016
Two in one group of 4 cams, one in one group of 5 cams.
Only using the Android app to have it happen.
1 Like
In reading the posts, this has to do with the grouped camera’s, correct? I do see that occasionally on my Android Device. I corrected it by Clearing the app cache and then in app info, Clear cache there and do a force stop. I also restart my phone.
Can you try that to see if it fixes the issues? I know this is not a fix, but curious if yours start to work after doing this as well. It may be a memory issue and clearing the cache and doing a force stop seems to clears it up. Restarting the phone did not fix it for me.
At times, I have tried connecting to my Floodlight pro directly and not from the group, and it would connect as well. Then when I go back into the group, it would work most of the time.
1 Like
I didn’t try the web portal, just my android app, but I do have 3 floodlight pro models in a group with some other cameras and I spent several minutes switching between the FLPros, trying to get them too not steam.
I open the group, everything streams.
I open flp1 and it streams
I back out to the group and choose flp2 and it streams.
I back out to the group and choose flp3 and it streams.
I repeated this, switching between camerass at least a couple of dozen times straight. All cameras always streamed.
I wonder what else might be involved here. Spamoni mentioned cache. I am using a relatively high end phone: Pixel 10 Pro XL 512GB, plus a pretty high end network: 1gbps with uniFi dream machine SE & 4 U7Pro APs. It’s possible the new firmware or app update is sensitive to different environmental factors. If we can find similarities in those experiences these issues they may be able to find and resolve it with a firmware or app update so everyone can have a better experience. Please, anyone else experiencing this, submit logs and it would probably be good to create an official support ticket number so they know it’s affecting more people.
1 Like
Phone, Pixel 7 Pro.
Modem, Unifi cable modem
(Xfinity internet, 2 gig down, 400 meg up)
Router, Unifi Dream Machine SE
Main Switch Unifi Pro Max 24 PoE
APs Unifi U7 Pro Max (3, one on ch1, ch 6, and ch11, all 2.4 is running 20mhz width) on 2.5Gig connections.
(I had issues with using a 4th AP, because of channel overlap, so it is a spare now.)
I am happy to delete cache, but how would that affect the same cams not working on the webview on other computers…
As far as groups, my network has v2s, v3s, v3Pros, v4s, floodlight original (v3)s, and Floodlight Pro’s.
Along with a bunch of lightbulbs and various other things.
124 online devices at the moment.
Now I see the Webview gridview is unavailable, and there is no way to choose just one cam in the default screen. No checkboxes, etc.
Now,
I set the 3 floodlight pro’s as favorites so they would all be on my app main screen at the same time, but not in a group.(View) they were still in groups.
I went back and forth between them over and over, and they never messed up.
I went back and forth between the two groups, 1 in one group, and 2 in the other.
They never messed up.
I brought up the webview on my wired computer.
The app on the phone started having issues with the groups, first seeing the cams stutter, sticking on the time stamp and then catching up, having trouble connecting, etc.
Closed webview, and the app started doing better again.
Typed a bit more in this post, then went back to the app on phone…
One FLpro cam unable to connect.
Force closed the app
Went back in
Same cam unable to connect.
Force closed again.
Cleared app cache
Restarted app
Still unable to connect
Restarted phone
While waiting for phone to reboot, went back into webview.
Same cam unable to connect even in webview.
Back to phone, still not streaming after re-boot.
***Log 2284451***
While doing the log submittal and typing that here…
Went back to home screen, and the cam is now streaming again.
Back to webview, it is streaming there too.
I hope you can make sense of this.
I would venture to guess if there is a memory issue, it is with the cams and firmware, not the phone or computer…
My Unifi logs show this cam going to 30% transmit retries along this time or real close to it.
1 Like
We have pretty close to identical system environments as you can get. About the only difference I can see so far is that your cameras seem to work okay in the app until you tried using the web portal and then suddenly the phone app started having a bunch of problems for a while.
The main reason I think that can’t really be related to the issue is because you reported the issue before the launch of the new web portal UI changes. But it’s possible that it doesn’t matter whether it was the old web portal or the new web portal, maybe it has something to do with the implementation of Amazon. Kinesis (assuming that’s what they still use for the web portal) has some kind of bug that is messing up the floodlight Pro for a while, such as not releasing the connection for a while after you close the web browser or something. Who knows. I’m totally grasping at straw’s here. It’s just the one variable I can think of that significantly different between your environment and my environment as we have extremely similar hardware and everything.
I haven’t used the web portal in a couple of months, so maybe the next time I am near my computer, I will have to try replicating what you did and see if I can cause my my flood light pros to have the same issue.
While unlikely, It’s also always possible that they are doing some kind of A/B testing, and that could explain the difference.
I my did update all of the rest of my floodlight pros to the new firmware so that I have more of them to check this issue on for you. I will keep an eye on them and see if I can help replicate it in any way as well.
1 Like
Thank you for your insights!
It was nice to find that they did not falter on the app only for me yesterday (until I tried the webview).
But it is also dissapointing, as I work from home, and have multiple computers on my desk all day, company, client, and personal, and it is much easier to just open webview on my personal computer instead of taking out the small screen phone.
2 Likes