I don’t know if that gets you exactly what you’re seeking, because it includes topics in the results that aren’t actually app releases, but it does allow you to combine categories into a single search, so maybe that’s helpful. I think what’d be even more helpful is if every Beta and Wyze News topic was tagged appropriately by whoever posted it, but I don’t think that’s likely to happen any time soon.
Thanks for the update. I didn’t know if it was a bug or some kind of update to protect voter privacy (which would seem weird on a platform like Discourse, which has a goal to promote engagement) or something else.
When composing the reply, I used the ™ HTML entity, and this rendered correctly in the preview pane on the right, but then when I submitted the post it looks like Discourse is trying to replace the Unicode character with its emoji shortcode, and I suspect this may be related to some recent changes discussed elsewhere, starting here:
Why do we have wyze-video-doorbell and wyze-doorbell tags, especially when the former apparently has only a single use (from me ), and wyze-doorbell doesn’t seem to follow the naming convention for tagging most other products?
I wonder if they’re intended to be synonyms for video-doorbell (which I interpret as being the “v1” wired product, but I don’t really know how Discourse tag synonyms function with respect to usage tallies) or if they’re more of a catch-all for general tagging of any Wyze doorbell product or something else. Most other product tags don’t start with “#wyze-”, so I’m trying to understand this situation better.
wyze-video-doorbell is already a synonym for video-doorbell. Use of the former is replaced with the latter. I’m not sure why you’re seeing them separately in the list you posted.
I think I need to go through he doorbell tags and possibly consolidate when compared to the product list. Honestly, I’ve lost track of how many different doorbell versions we have. I’ll put it on my never-ending list.
I’m aware of four doorbell versions, but there are six tags for doorbells, which is part of what prompted the questions. I think parity with the product list and other tags makes sense, but I don’t think it’s a high-priority issue.
Has there ever been any consideration to restricting the creation of new Beta topics to Wyze Team members, much like Wyze News? I ask because every once in a while new user-created topics show up in Beta (often with a bug tag), and they frequently don’t mention a beta app version. I’m not sure how helpful those kinds of topics are, because they seem to clutter the category, which I understand is one of the categories Wyze officially tracks here in the Forum (or at least that’s what I’d expect when a Wyze employee creates a topic there).
If new topic creation for that category was restricted, then any user who wishes to post in that category should have to find the topic that corresponds with the app/firmware version that is giving the user problems, and that might help with organization and issue tracking (and hopefully remediation). Maybe. I’m trying to think positively, anyway.
I believe that the bug tag can’t be applied to other new topics in categories like Wyze App or Cameras or Services & Integrations, so if Beta was restricted then it might be useful to open up bug’s availability to other categories.
I like being able to see the category (it’s one that I have set for Watching First Post in Tracking) even though I’m not always using the public beta app or applying beta firmware, because it gives me visibility to some potential problems before they make it to production. I like that Wyze Team members post topics there, because I see those as kind of heads-up announcements and feedback solicitations. Where I think it could be improved is limiting who can create new topics in that category, because I think when regular Forum users have the ability to do that their problems can get lost, don’t have the best visibility, and may not be tracked and addressed before a given firmware or app version advances to production.
If a Forum member is going to choose to participate in beta testing, then I think that member should also try to post any problematic findings to an appropriate existing topic in the Beta category, and my hope is that restricting topic creation in that category would assist with that.
You’re welcome, @peepeep!
), and 
