Automations Error

[munkiinut]

When trying to edit my Automations, I just get an error page saying “ Incorrect Product Model selected”

I have to delete and redo the automation.

[Crease]

More details might help shed some light on this, for instance:

• What are the specific steps you take to (re)produce the error message?
• What Automation or Device types generate this error (i.e., is it all of them?)?

If you haven’t already, I’d be inclined to reproduce the error, immediately submit a log, and then open a ticket to connect it to the Log ID.

For what it’s worth, I haven’t seen this on Android, but I also don’t know exactly what steps you’re taking to produce the error.

[munkiinut]

I submitted logs already. Log ID: 1529266

I have 4 color bulbs in a group.

I have 3 automations.

1- Turn on brightness 100, color Daylight

2- Turn on brightness 1, color soft white

3- Turn off

If I open the automation and press the little icon to edit, I just get that page. This happens on all 3 automations.

I also have an automation to start my robot vacuum. I can try editing this one without any problems.

Currently it’s only happening with the grouped lightbulbs.

iOS 17.6.1
App 3.0.0 (16)

[Crease]

@munkiinut

I submitted logs already. Log ID: 1529266

Did you also submit a ticket, though? My understanding is that having a ticket with Support that can be connected to the log is helpful to the engineers when trying to identify bugs:

Support log - do you ever get a communication of help in your issue

The other guys summarized this really well! I just barely posted this quote directly from one of the engineers in another thread, so might as well share it here too…basically the engineers say they never look at the submitted logs unless you send it to them through a support ticket or community manager: And the engineers almost never respond. If they do, they will tell support what to tell you or have the community manager ask you for more details. but 99% of the time, they don’t respond in…

[munkiinut]

I did submit a ticket. But to be honest. It’s not worth my time to email them back and forth with their “update your app” or “ force close the app” trouble shooting responses.

Then after 3-4 emails they might forward it to the engineers.

I can delete and create my automations quicker. I mainly posted it as a bug I ran into and o see if anyone else had.

[Crease]

I dig. At least it’s (hopefully) in Wyze’s system and being tracked by engineers now.

I totally understand what you mean about the back-and-forth with Support, too. Some of the Wyze Wizards seem to border on competence…sometimes.

I’ll be interested to see if anyone else chimes in with this issue, even though I often find myself vicariously frustrated when I read about iOS-specific bugs here.