Let me inform @WyzeJasonJ of this issue because they thought they fixed it back in October when they said they found what was causing it and corrected it. If it’s reappeared, they should at least be aware of what was causing it and be able to fix it again now. Here is the last time I heard of this happening and them announcing they fixed it:
Jason will see this and pass it on, but just to be sure, can you check what firmware version your camera is on, and can you submit a log for that camera and post the log number in here so he has something to pass on to the devs so they can look into it?