I just applied the .50 firmware to several of my cam pans to observe. Has only been a few hours, but I already notice a reduction in recorded footage on the same camera I tested with last month. Made no other changes to sensitivity (still set to 51) or detection zone (full frame). I’ll leave it in place today and see if the trend continues + can send logs if necessary.
Curious to know if anything along these lines was discovered during the .46 firmware and addressed in .50 per this thread? I do have WyzeSense pre-orders on the way and would like to use them, but would still like to be confident with what might have changed to impact recording.
Thank you for bringing up this issue, we’ve let the dev team looked into the logs sent by our Beta testers regarding the record footage reduction issue. Meanwhile we will look into the statistic to check the alert video numbers comparing to the previous version.
It means that SD card recording in event only mode now respects the detection zone and sensitivity settings that are also used for motion event recording to the cloud. Previously, SD card event-only mode was full frame and fixed sensitivity.
I updated seven cameras at once. Two pan cams 1400 miles away won’t connect. They can’t reset and I tried logging in and out of both iOS and Android apps. These pan cams are new and put into service last week. I am not there to power cycle them. Thanks guys.
Hey there, ever since the firmware update, all 3 of my pans can’t hold a signal. No changes in network, and the only devices impacted are the cams. “Connection failed error code 27”. This has been going on for days. Please help!
Same, however I updated 4 remote Pan’s when I was on site and everything was working fine. This was this past weekend and ever since then I’ve had to restart all of them multiple times. Sometimes I wouldn’t be able to get past Authentication, others the stream rate would just drop to 0 and appear to hang. Luckily I was able to connect, so I was able to use the restart command.
Now, one of them went offline and even after having someone on location power cycle it, I’m not getting a response after 15 minutes. Will have to try again.
The cameras were definitely much more stable before the firmware update. I’ve had them running for months without needing to perform a single restart.
The key here is to first downgrade the firmware and then re-upgrade it. It’s a strange kind of bug where the firmware itself is not the issue but rather the initial upgrade that messed things up. This may be why it’s taking a while for the devs to come up with a fix.