The thing here is that Wyze rules/schedules/triggers are cloud-driven and not local device driven. I fail to see how rebooting any Android or iOS device would have any impact.
I’ve got Wyze on both my android phone and tablet. The idea that rebooting either would resolve something rules-based implies that one device is the ‘active’ device and the other secondary, etc… when in fact both devices can operate simultaneously.
Stopping the local service, clearing cache, etc only resolves things like local viewing trouble in my experience. Not saying it isn’t worth a try periodically, but I think its barking up the wrong tree in this type of circumstance. And it’s unacceptable as the norm.
Well, this here old fashioned Unix Systems Curmudgeonistrator doesn’t care much for the reboot fix or anything that resembles it
Apparently this problem is not caused by a corrupt profile, since I assume the force stop and cache clearing would have, but did not fix it for me. So we wait
What can I say… Been a Windows guy since 3.1. Just comes natural to throw in a restart.
The real thought was logging out of the account, then logging back in to goose the account, possibly resyncing the rules from the client to the host, The clearing of cache and force stopping the app was just a good measure to support the log out and log in. You never know when simplicity thrown into the masses of genius might be of assistance, and only because WYZE called the incident “resolved”. Which doesn’t seem to be the case.
I hear you. However, bear in mind that once you’ve configured Wyze and all of your ruleset, there’s really no requirement to even remain logged into the app for automation to run. The “clients” in this case are the endpoint devices themselves. Rules and such are fire & forget from their cloud and don’t require any logged-in smartphone/tablet in order to function, unless you need to modify.
Ah yes, the Windows 3.0 & 3.1 (DOS-dependent) “graphical operating environments”. I was an OS/2 guy thru the 90s and pretty much only run Linux nowadays. Didn’t want anything from Billy 6ate$ (or Ballmer the enforcer) back in the day or the present…
I have 6 wyze plugs. They have not been following their time delay based rules since yesterday to their last time to run today (10:30PM EST) that have been working just fine for a month. Not fixed.
I didnt think about the devices being a client of their own, thanks for that. You know what that means though? Reboot all the motion sensors and bulbs!!! Unscrew them from the socket and pull the battery:rofl:
Someone needs to change the title of this thread, as well as the top sticky message. Issue is clearly not resolved and, reading from the posts above, it’s clear that we will have a number of divorces filled once courts open tomorrow morning
No schedules/rules working for me and notifications are still delayed . Unfortunately this is not resolved, @UserCustomerGwen, might have to ping team again!
I will report back this evening if the rules fail again. I will know shortly after 6pm EST. This issue (and the lack of resolution) is at least weighing in on my thoughts of purchasing more plugs.
I understand that your main purpose is to make money but, your comment about different teams seems to not ring true. I have bought several Wyze products over several years and am still waiting (along with MANY others) for a viewing app for Windows 10. Using BlueStacks is a cumbersome workaround that takes loads of system resources and takes forever to boot. I have stopped buying Wyze products until the promised viewing app for Windows 10 becomes a reality.
