Wyze app 3.0 - Released 7/24/2024

[Crease]

@grapefruityoda

weird bug

So the path the user takes to get to modifying an Automation matters and can potentially break things? Yeah, that sounds like a .

@MisterB

At the very least, there needs to be filter options with checkboxes that allow you to show or hide all of the different types of devices including groups.

I like this idea.

@MisterB

Better yet, the groups could have their own tab

I like this idea less, mostly because adding another tab seems like it shouldn’t be necessary. The idea of using filters and/or sorting in ascending or descending alphabetical order—something that users are frequently presented and that makes intuitive sense and which would also conceivably sort/group items with emoji in their names^[1][2][3]—seems more workable to me.

@MisterB

Needless to say, every object that presents a power button icon needs to also present the user the ability to disable the power function for that object specifically. That or remove the feature altogether and force the user to first tap on the device, then tap on a power icon that then presented.

Another alternative might be the way some other apps handle a toggling interface. I’d like to see some options available to the user.

@MisterB

fix what they have already developed and sold to customers.

I agree. This is one of my major ongoing beefs.

@MisterB

These egregiously underperforming devices and application updates need to be slowed down and have more thought put into the impact it will have on customers.

I’d tend to agree with that, too. I never have been a fan of the “move fast and break things” philosophy espoused by Facebook. I want the function of my tech to be as stable as possible.

@MisterB

I still can’t put one device in more than one group which would make automations substantially more flexible and useful.

I want to do this, too. At least that’s still part of the future plan.

---

1. Creating More Descriptive Rule Names Using Emojis

   Rule names are restrictive in that you can’t use a lot of characters in the title. This makes it very hard to manage them, as you often have to open each Rule to see what it does, especially if you manipulate a lot of devices in the rule. I’ve solved that to a degree by using emojis. I put one as the first character of each camera name. When you get used to your selections, you can tell what a multi-event rule does just by reading the emojis. Here are the camera names I commonly use: [Scr…

   ↩︎

2. Rule Engine/Mgmt/Organization Changes Coming?

   Yeah, that’s one of the things I’d still really like to see, and I appreciate the desire for the other things you asked about. I can identify with this. The only other automation platform I’m using consistently is Google Home, and at least that one has the common sense to order my routines alphabetically, so I have an idea of where a routine is going to show up on the list when I name it. Because of that, my naming scheme for Google Home routines tends to start each one with 1-3 emoji, whic…

   ↩︎

3. I’m going to refer to this as emojibetical order. ↩︎