Aww…the sneaky Carver edited his post….
Found a good example of what I was saying as demonstrated in this thread:
Summary, User switched to “Smart Detections” but was still getting “Motion” Notifications and couldn’t fix it. I copied the user’s post into the AI search bar and it gave a completely wrong response:
The correct answer is this:
Explanation as follows:
Human Forum response beats the AI again.
Wyze should add a support article to explain this issue or better yet, resolve it so that smart detection automatically turns off motion notifications like everyone assumes.
@WyzeJasonJ consider passing this feedback example on to Bruce or maybe have Brenda or someone add a support article for this [semi-common] issue?

or better yet, resolve it so that smart detection automatically turns off motion notifications like everyone assumes.
Or maybe acknowledge the fallibility of AI because the camera is capable of detecting the Other Motion anyway, so just don’t hide that line from the user when Smart Detection Events is enabled, but that’s more of an app developer issue than a Help Center manager issue.
Naw, if someone wants to still view motion events they can just leave it set to show "All Events. Selecting Smart Detections was a long time requested feature from several users who hated having all those pointless events in their events feed. From their perspective, if they needed to review something that wasn’t detected by the AI, they can use the SD card.
I agree with the smart detection option only saving AI detections for those who only want to care about the most important events without all the figurative “noise.”
They just need to fix it so it works as intended. Anyone who doesn’t want that option can still use the “All Events” option like I do for those of us with that preference.

they can just leave it set to show "All Events.
Yeah, that makes sense as an option. I just tend to favor visibility into the options, and from my understanding of the situation, my perspective is that selecting Smart Detection Events in this case effectively hides the ability to disable the “Complete Motion Detected” notifications from the user, so that seems like a design flaw that should be remedied.

They just need to fix it so it works as intended.
Agreed.
Getting back to the topic at hand, I appreciate that you’ve illustrated a specific case where the AI-powered search needs work (in the form of articles in its official knowledge repository that it can assimilate), and I’d also really like to see a more efficient means for communicating errors in Help Center articles to the Web content team, because reporting them to Support via ticket is not a good process. When the proper articles don’t exist at all or are replete with erroneous or outdated information, then it doesn’t matter how good the AI is: It’s going to give wrong answers to users seeking help.
Yeah, I think I will post some examples like this either here publicly, or in non-public ways to give them ideas of common issues they can either fix or create new support articles that can address anything missing. That way the AI will be able to more accurately answer these common issues instead of wasting time either giving people irrelevant responses or sending them to a support human who likely doesn’t know the answer either if it’s not in the support articles since they are likely supposed to follow a script that is based on the support knowledge base.
So I’m kind of on the lookout for examples of new support articles they could add so that such things can be accounted for.

So I’m kind of on the lookout for examples of new support articles they could add so that such things can be accounted for.
Like the issue with iOS 18 and Error Code 22005? There’s a brief notice about it on the Help Center home page that appeared several days ago, but since there’s no actual article the AI search doesn’t “know” about it.

Like the issue with iOS 18 and Error Code 22005?
Looks like AI knows the reason and the solution:
The response appears to be query dependent, which is what I would expect from a simple traditional search facility, but apparently the AI isn’t “smart” enough to determine the difference between iOS 22005
and iOS 18 22005
. The first provides the correct answer, and the second returns this:
I think they’re both reasonable basic queries, and the second one is what I was trying yesterday (and today) because the issue appears to be specific to that version of iOS, so it’s something I’d expect another user to ask. I guess like with other systems, if you’re not getting the answer you seek from the Great Wyze Oracle, then ask a slightly different question.
Need to add a keyword as a preface to numerical strings, like “error”. When parsing out input strings, AI can assume 18 is associated to iOS and denotes version, but needs a hint with 2nd numerical string. AI should not definitively assume those 3 choices in your screenshot, it should ask user for “22005” context or ask if one of those 3 options is related to “22005”. As it stands, “iOS 18 22005” leads to a dead end. Maybe that LiveX AI Agent instance just needs some virtual Red Bull.