I’ve looked everywhere, and cannot seem to disable some automations. They show up in the log. The cams are not using the time feature. I just cleared the cache. I saw a 2023 post on this, but saw no resolution. Not sure where to look???
What other detail can you provide about what you’re experiencing and what you’re trying to accomplish? There are different types of Automations, and Shortcuts (which are designed to be executed on demand) don’t have an Enable toggle. If you can share specifics about what’s not working and what you’ve attempted, then that might help others in the community to provide assistance.
Welcome to the Forum, @murraymn! 
I’ve created my own “scheduled automations”. e.g. For outside and inside cams, inside cams sound alarms, so they only run during very late and early hours. Outside cams run from sunset to sunrise, and send notifications for person detection (plus trigger uploads from all cams). When we have company over night, I disable (toggle off the “Enable” switch on the scheduled automation) on inside cams, so sleep walkers (joking) don’t trigger the sound alarms.
When we’re away for extended periods I have “scheduled automations” that run 24x7, but do daily restarts in case of power outages at scheduled times. They don’t seem to have a problem.
Back to the problem, I check the logs, and I see some automations run despite NOT being enabled. I unplugged a couple of inside cams, and the log appropriately logged failures for these cams to start. I’m not sure why these scheduled automations are running. The cams are not individually set to run, just the automations. It’s as if I’m missing another way that they run. I cleared cache, killed and restarted the app…nothing helps.
Hope that clarifies it a bit.
I think it clarifies some things but muddies others, at least in my mind. For instance, I’m not sure what you mean by this:
Overall, the impression I’m getting is that what you’ve actually created are Device & Service Trigger Automations where you’ve specified a time based element (the WHEN section), and maybe sometimes you’re seeing instances of those executing on the Automation History screen when you don’t expect to see them. Is that accurate?
For one thing, if you feel comfortable sharing some screenshots of what you’re seeing—for instance, an Automation that you created but disabled and an example where you see it executing anyway—then that might be helpful in my understanding and that of anyone else who views this topic.
For another, I’d probably navigate through all of the cameras’ settings and make sure the times are synchronized ( Settings ➜ Advanced Settings ➜ Sync Time), reset the services on each ( Settings ➜ Reset Services), and then verify that the Smart Detections are set the way you want them. I’d probably also run through your Automations to verify that there aren’t any duplicates or anything else that’s enabled to run when it shouldn’t.
I think you’ve tried the right kinds of things by clearing the cache, stopping, and restarting the app. If you were an Android user, then I’d also suggest clearing the cache and data at the OS level to get a fresh login and force the app to pull down a new copy of your profile/settings from the server, but I don’t know if iOS allows that kind of thing. You should be able to do the same thing by completely uninstalling and reinstalling the Wyze app, but that might be overkill in this case.
If what you’re seeing is happening repeatedly, then I’d almost certainly submit a log and then open a ticket referencing the Log ID, because things happening out of their scheduled times shouldn’t be happening. Other users have been reporting funky time-based anomalies in the Forum recently, too (the day of the month and day of the week are mismatched on the Events tab, for instance), and since Automations run from Wyze’s servers (not locally), I wonder if what you’re experiencing is related at all to that mess.
From my personal experience, Wyze’s time-based features have frequently been unreliable. I have pretty much given up on Vacation Mode for their lighting products. My ticket with them was never resolved, and these things still turn on outside of their specified hours when Vacation Mode is enabled and I’m out of the house. (I know because I get motion notifications from the cameras triggering off the light changes.) I don’t know if what you’re experiencing with your Automations is anything like that, either, but I’d still be inclined to log and ticket it so that they’re aware it’s a problem.
I don’t know if any of this helps or not, but you’re welcome to bounce more questions off me, and I’ll try to answer what I can. Maybe someone else will have better ideas, ‘cause I’m kinda scratchin’ my head here about what you’re actually experiencing and trying to describe.
Screenshots was a great idea. I deleted the old automation, and created a new one. I also have two cameras deliberately off, to verify the automation is running.
In the screenshots you can see the current state of the automations. Notice, the old automation is NOT there. The second screenshot is the log. Notice the OLD automation is shown, and NOT the new one. Back to your question, you’re right, my bad. Each cam has a Device Trigger for person detection. Hopefully the screenshots are right…can’t see them till I reply (as far as I can tell). I’m going to reset services for each cam…hadn’t noticed that before.
Old: Inside Cams 11:30pm-5am
New: Inside Cams 11:30pm-5am II
I’ve deleted both of the automations now, and as hoped, had no phantom scheduled automation run. Now I’ll recreate it, disable it, and see what happens tonight.
Thx
I appreciate the update, and I’m glad you saw the result you expected following your changes. I’m still confused about what’s happening and why. Something isn’t connecting in my brain, I guess.
Thx for your input! Got me over the hump for now.
Long story short…deleting the Scheduled Automation seems to have solved the problem, of it running regardless of the Disable toggle switch being off. In my case it was easy to create a new one. I haven’t tested my “new” Scheduled Automation yet, it’s a bit of a hassle, but I plan on testing it over the next couple nights. (I have company, and an alarm going off in the middle of the night, because someone decides to get a drink of water in the kitchen, isn’t and is, funny). 
Thx
Any progress you’re making with this is all you, because I still don’t think I understand exactly what’s happening or what you’re trying to accomplish. 
Sometimes just writing things helps me to organize my thoughts, though, and bouncing ideas off someone else (in a thinking-out-loud kind of way) can be helpful, too, so maybe that’s what’s happening here and where you’re deriving some benefit. 
Well, I’ve determined the problem (sorta). The Scheduled Automations” disable toggle button doesn’t disable this automation. It runs regardless. The only way I’ve found to disable it, is to delete it. The odd thing is it appears to be only this automation, which makes no sense, since I have several automations, I’ll be putting in a support ticket.
I’m using the app on a iPad & iPhone.
IOS version 18.4.1 (22E252)
Wyze App version: 3.5.0.8
Cams in automation (4) are:
Three, Wyze Cam Pan v3, Firmware: 4:50:14:3339
One, WyzeCam Pan, Firmware: 4:10:9:3006
I think a Support ticket is a good idea at this point, and I’d probably log it, as well.
This is how I prefer to submit tickets (you can click/tap to expand this):
- Visit the Help Center: https://go.wyze.com/help[1]
- Click into the “AI-powered search” box in the middle of the page and enter
create ticket. - Click Yes, that is correct..
Repeat Step #3 or enter yes. (
UGH! 
)- When the “No, I want an agent.” option appears, enter
no. - Enter
product.* - Enter
other.* - Enter
ticket. - Enter your contact details and a brief issue description (include a Log ID if you have one) and click Submit.
* Make your own appropriate/relevant choices here.[2]
It doesn’t really matter how brief the description is. Wyze’s system will generate an e-mail message to you automatically with a Wyze Ticket number, and you can just reply to that message from your e-mail client and add as much detail as you want.
Note: A log is not the same as a ticket.
A frequent user complaint is the absence of follow-up from Wyze following the submission of a log from the app. If you choose to submit a log, then Wyze's system will generate an e-mail message to you with advice to contact Support if you need help, because the engineers will have access to the logs, but Support agents do not. You can include a Log ID when you create a Wyze Ticket in order to connect a log to an expanded description of an issue in a ticket, and that's information that the Wyze Wizards may be able to pass along to the engineering team, but those seem to be two separate systems, and it's important to understand the difference.
A relevant Help Center article goes into more detail.
It’s odd that it would be just this one Automation. I have several Automations (both Device & Service Triggers and Schedules) that I’ve created in the past (usually just for testing) and then disabled, and the system seems to be respecting that. I’m using Android, but I’m not sure if that makes a difference here. I suppose it’s possible, because I’ve seen that some issues affect iOS and not Android or vice versa, so I wouldn’t yet rule that out as a confounding factor.
I wish I had better information for you. I admire your persistence in pursuing this.
2025-05-23T17:47:27Z Edit: I know you mentioned clearing the cache and restarting the app a few days ago, but if that’s not something you’ve done recently, then I’d also consider trying that again. The steps below are what I suggest for Android because I’m not familiar with iOS’s OS-level caching (like how Android has separate app cache and app data clearing functions outside of what’s available within the app’s internal settings), so perhaps only steps 1-2 are applicable to your situation.
This is how I would get a clean copy of my account profile/settings on Android (click/tap to expand):
- Clear the in-app cache: From the Wyze app’s home screen, navigate to Account ➜ App Settings ➜ Cache File Size ➜ Clear.
- Navigate back one screen to Account and tap Log Out at the bottom.
- Swipe the Wyze app out of the running Android apps.
- Long-press on the Wyze app’s launcher icon (on the phone’s home screen or wherever you tap to initially open the app) and then tap App info in the pop-up menu.
- Tap Force stop on the App info screen (may need to tap OK to confirm) and then tap Storage & cache.
- Tap Clear cache and Clear storage on the Storage screen.
- Back up one screen (back to App info) and then tap Open and proceed to log back into your Wyze account/app. (Optionally reboot the phone at this step for good measure and then launch the Wyze app after the fresh boot instead of relaunching it immediately from this screen.)
Note: I don’t know what the options would be for modifying these steps on iOS since I don’t use that platform.
In your case, I might try it this way:
- Delete the problem Automation.
- Clear the cache and log out of the app (as described in the steps above).
- Reboot the phone.
- Re-launch the Wyze app and login.
- Recreate the “problem” Automation.
That might be a way to clear a lingering problem and get a really fresh copy of that Automation, but I’m just speculating at this point.
Well, the problem appears to have fixed itself, after I put in a ticket Friday am. Don’t know if it was deleting the original scheduled automation, or Wyze support.
Regardless, it’s working and worth noting for anyone experiencing the same problem.
Cheers
1 Like
I’m glad it seems to be working, and I appreciate your taking the time to post updates.