Error Code: No fragment

@lupitatg
Thanks so much for posting your solution, it worked for me also :+1::+1::+1:

both of our camera’s are now experiencing this starting today:

MAC 2CAA8E9B0E0E & 2CAA8E81BF90

I was having the same problem, I just used the “restart device” button in settings and it seemed to resolve itself. I can watch my recorded events again. Didn’t have to mess with my cam plus settings.

1 Like

Restarting my camera/power cycling helped mine too. But I’m not holding my breath. :sweat_smile: This fragment error has been frustrating.

Nice that restart works for you. For me, not so much.

Have you tried manually power cycling the camera instead of using the rules feature? The app restart doesn’t completely turn off/on the camera is the only difference.

Yes sir, tried that with no luck. Only cams that are on Plus do this. The error actually stopped for a week and then returned yesterday.

1 Like

That’s a bummer.

I hope Wyze can find a fix for this bug soon. It is causing a lot of problems for everyone. I don’t like paying for Cam Plus when it doesn’t even work like it should.

thanks, restarting our 2 seems to have fixed it for now. Hopefully wyze offers a better fix

1 Like

Been happening for a month now! Why am I paying for a service that’s unusable? If this persists for a week longer without any formal response or acknowledgement you have lost me as a customer.

Seen a notification today from Wyze (not sure how long it’s been out there) they’ve identified the root cause for the “No fragment” error and are coding a software fix for it, no ETA just yet but I reboot the camera with using the restart button and it solves the issue in meantime for myself (no loss of data - can view all the clips)

1 Like

We’ll see…they said the same thing back in June :neutral_face:

Interesting, did they indicate in June the root was from an API issue? This notification states root is from a discovered API issue and they are coding a fix but don’t have a release timeframe yet

WyzeKyle didn’t specifically mention it was an API issue, only that it was CMC related. So it it probably was an API issue as well.

1 Like

Thx for reply :+1: fingers crossed they have a handle on root now and can fix it (the frequency of how often my camv2 gets is increasing)

1 Like