I’ll answer the direct questions first:
- Not generally, no, but for some specific use cases I might want to enable notifications on a particular Automation. This should not be an all-or-nothing feature.
- If I have to choose between those two, then I’d say Schedule Automations, though I could imagine situations where Device & Service Trigger Automations could benefit from this as an option. I could also imagine a Shortcuts use case.
- If I have IFTTT turn on a Wyze Bulb Color because of an expected freeze notice or other weather event, then with a feature like this I could also set a Device & Service Trigger to generate a Wyze push notification so that I have an additional means of receiving the message. For certain Schedules or Shortcuts, I might want to know that something executed successfully or that a shared-access user ran a Shortcut.
Here are some my questions with this topic:
- What are users actually requesting with regard to notifications for Automations?
- How does this fit into Wyze’s 2026 plans for “[f]ixing notifications for real”?[1]
- The recent Founders e-mail goes on to say this about notifications: “They should be shorter, smarter, and more meaningful. The technology is there, and we made progress this year with the NoBigDeal Filter, but we’re not done yet.” Wouldn’t this just have the potential to add to notification overload by adding another stream (Automations in addition to devices) for pinging users’ mobile devices if not implemented thoughtfully and carefully?
- Why is Wyze asking about this instead of asking about input about things many users are publicly requesting, like Wishlist topics addressing other Automations and notifications areas (noted below), or providing insight into Wyze’s plans for Home Assistant and/or Matter support?
As I said in my first answer, I wouldn’t generally want to see notifications for Automations unless there’s a problem, and this is how the Google Home model seems to handle it. Within that ecosystem, I might see a notification on my phone if a routine fails in some way (unresponsive device, etc.), but otherwise the system doesn’t bother me with unnecessary information.
Also, something like this should be completely optional and something that a user could enable or disable on each individual Automation’s creation/edit screen, such as a line like one of these:
- / Notify me when this runs?
- Notify me when this runs? /
- Send this message when this runs: {user-input-message-here}
There could also be an Automations line or section within Account ➜ Notifications ➜ Push Notifications with a global/default setting like “ / Enable for Automations”, but the user’s individual choice for a specific Automation should always have priority and override this global setting.
Where I would really want to see Wyze prioritize development resources, though, would be existing Wishlist items related to Automations and notifications:
- Add More Actions for Wyze Automations (Rules) — This is a big one with a broad scope, so I don’t know how Wyze would select priorities. Perhaps another poll like The Rule Team would like you to vote on some Rule Actions if Wyze intends to follow through with acting on user input?
- Add More Triggers for Wyze Automations (Rules)
- Individual Camera, Sense, Doorbell, AI detection type, etc. Alert Notification Sound and/or Color — This is one that I’d like to see implemented across platforms and within the app. Android users have been able to employ third-party notification managers to have some degree of notification customization, but iOS/iPadOS users don’t have this option, which really should be native to the Wyze app itself.
- Customizable notifications (Incl: Android Notification Channels) — I’m particularly biased toward this one as an Android user, but I’d want iOS/iPadOS users to have a comparable experience.
- Multiple Users' Permissions for Shared Users — Shared-access users should be able to enable or disable notifications independent of a device owner’s choices, and that’s one of the repeated requests in this topic. I was hopeful when I saw a co-founder’s message about this over a year ago, but I haven’t seen any public mention about action on this since then.
I agree. I don’t know what Wyze has in mind for an implementation related to the questions above, but a customization option would have the potential for a lot of flexibility in terms of what users might be able to do with this.
I’d like to see this, too, and it’s on the request list in “Add More Actions for Wyze Automations (Rules)”.
Source: “A Letter From the Founders” e-mail from 19 January 2026 ↩︎