Floodlight Pro no longer recording Smart Detection Events as of 12/28/23

As of 12/28/23 my Floodlight Pro, with Cam Plus, is no longer recording any Smart Detection Events. Firmware and app are up to date and I have performed troubleshooting per this troubleshooting article, with no luck.

However, in Event Recording, when I select “All Motion Events”, which automatically unselects “Smart Detection Events”, it starts recording “motion” events (not Smart Detection Events). When I switch this setting back to “Smart Detection Events”, the issue continues and it does not record Smart Detection Events or any other motion events.

I have two other Floodlight Pros with the same settings as shown below, which are only recording Smart Detection Events, with no issues.

App Info:
v2.48.0 (379)

Device Info:
Firmware 2.2.1.1083
Activation Date 11/16/2023
Plugin Version 2.48.0.1

My settings which worked fine for over a month, until 12/28/23:

Detection - 100/High
Detection Zone - Off
Record Motion Events - Enabled
All Motion Events - NOT selected
Smart Detection Events - Selected
Smart Detections - Person, Pet, Vehicle, & Package selected

If you followed that entire support article including all the way through power cycling the device and factory resetting the device and setting it back up and it’s still not working for you, I would suggest contacting support. I have six of these flood light pros and a little while ago I did have a couple stop doing detections, but all I needed to do was power cycle them and the detections all started working again. All of mine are now doing detections.

If you haven’t tried restarting the flood light, or doing a factory reset as stated in that support article, I would really try that, because that is what resolved the detection suspension for me. If that didn’t work I would try clearing the cache from the app, then loading the app back up and try toggling the detections back on again. Then walk in front of it and see if it detects you as a person. If it’s still not working I would definitely call support. They may ask you to do some of those same troubleshooting steps again because it’s something that they have to do to be able to verify that you indeed did all those things and they can vouch for you that it didn’t resolve the issue, so just be patient and do them again anyway if they ask. But worst case scenario, you should still be qualified under the warranty since these haven’t been out for more than a year.

3 Likes

Thank you @carverofchoice. Power cycle fixed this issue. Obviously, lied - I skipped step 8 for the power cycle, thinking if I factory reset it and set it up again, that would be better and have more likelihood of solving this particular issue than power cycling. Goes to show that most issues can be solved by just turning something off and back on :man_facepalming::man_shrugging:

3 Likes

That’s GREAT!

Your logic was not entirely misplaced since a factory reset should also make the device reboot. I totally understand skipping the step. But since I experienced something similar I wanted to mention that is all it took to resolve it for me and hoped it would be sufficient for you too. :slight_smile: I’m glad you didn’t need to do more. You are 3rd or 4th person I know of who experienced this. The others of us noticed detections stopped on a couple of FLPros on December 6th around 3:30pm PST. But it only happened to a couple of my FLPros, not all of them, so that was weird. Thankfully, they only required restarting them to start doing detections as normal.

Just to clarify, are you absolutely sure that your detections stopped on 12/28/23 and not earlier than that? Do you see AI detections from the 27th or earlier still? Or is it possible you just didn’t notice until the 28th?

2 Likes

Yes - I went back as far as it would let me go, 12/22/23, and verified that I was getting smart detections and then they stopped on 12/28/23, with the last recorded event being at 5:35pm EST.

1 Like

Interesting. Thanks for verifying. That indicates it might have happened at least twice. :thinking:

I’ve been keeping an eye out for reports like this to see if there is any common cause/pattern. It seems fairly rare right now, like it only affected 2 of my 6 Floodlight Pros when it happened to me.

Anyway, I’m glad you’re up and working and appreciate your follow-up and checking. :+1:

1 Like

Just saw Wyze is releasing an update that might fix this “event tagging bug”:

It’s possible it’s related to this. I know I did report this to Wyze back in mid-December, so maybe they figured it out and got a fix in. :+1:

2 Likes

It is very possible that it first happened in the beginning of December, like you, and I didn’t notice. During that time, I was adding more FLPros (I have 3 now) and I’m sure I flipped the circuit breaker to FLPro in question when trying to find the right circuit for the others I was installing, which would have power cycled it and fixed the issue temporarily.

1 Like

Hmm… interesting, indeed. Thanks for sharing and thanks again for helping!

1 Like