I have a Wyze Plug, and a Wyze Plug Outdoor. All are set to turn on at Sunset every day, however they are turning on at least an hour early.
All have been power reset, thanks to a power outage of several hours. The Wyze Plug Outdoor sensor is facing out and is not covered or obstructed.
Both devices are using the latest firmware
Any ideas what the problem is?
Welcome to the Wyze forum @nickmonaghan
Assuming your phone has the right time and time zone.
Do you have the home setting set in your account? If I remember correctly, it’s your location/address that determines sunrise and sunset.
This is in the Wyze App, Under Account, Home
Welcome to the Forum, @nickmonaghan! 
Maybe take a look at this topic:
I think Wyze has a history of some of their devices not handling time-based features very well, and this may be one of those cases.
That shouldn’t matter if you’re using sunset/sunrise-based schedules. That’s used only if you want to use ambient light to control the sockets, at least as I understand it. If you’re using both the Schedules and Brightness features with your Plug Outdoor, then I guess there could be some kind of conflict, but if this behavior is also affecting a regular Plug in the same way, then I’m guessing it’s a time offset issue similar to what was described with Lamp Socket v2 in the topic I linked above.
If you’ve confirmed that your phone’s time is correct as @R.Good suggested (and you can also try giving the app your location at Account ➜ Home; I would expect the app to use this information to determine sunrise/sunset times at your location, but I’m not convinced that Wyze is actually using this data that way), then you can add a 1-hour offset to your schedule as a work-around, but I’d also consider submitting a log if you haven’t already done that.
What did Support say when you contacted them?
One other thought: If you’re using Local Schedules on the plugs (present on Plug Outdoor and later generations of Plug; original Plug v1 does not have Local Schedules), then you could try creating Schedule Automations instead and see if that makes a difference in your experience…or vice versa.
R.Good, Thank you for the welcome and your reply.
I think I may have solved my problem, which appears to be a conflict between an automation schedule set up for the holiday, which I thought I turned off, and the usual schedule. Gotta love user error!
I’ll know more tonight!
@Crease, Thank you for the welcome and your reply.
I think I may have solved my problem, which appears to be a conflict between an automation schedule set up for the holiday, which I thought I turned off, and the usual schedule. Gotta love user error!
I’ll know more tonight!
Oh, yeah, I’ve had experience with my own user error and automation conflict. 
Good catch, and good luck! 