Several Wyze devices, some older. Plugs, Doorbell, Bulbs, v2 Cams, Sense Hub. AFAIK, all firmware current and most devices integrated into Google Home.
All worked as expected until recent mystery random activation of one particular bulb. So far, unable to identify trigger but last time a “Hey Google” to Mini seemed to be cause. Unable to reproduce.
Rebooted router, unLinked/reLinked Wyze to Google Home, Rebooted Mini.
Any thoughts - How to isolate, eliminate?
Thanks for posting about this. I’ve seen some Wyze and non-Wyze lights on at unexpected times overnight and in the morning, and I was thinking about it this morning and wondering if at least part of my problem is a rogue/hosed routine in Google Home.
My devices are linked to both Google Home and Amazon Alexa (though I’ve been a Google Home user much longer), and I have some routines that run overnight to reset lights for me so that, for instance, if I was using certain smart bulbs in a warm color and low brightness percentage in the evening, then they would be at their regular full intensity and color upon initial “turn on blah, blah” the next day. I think probably something is mucked up there with all of the changes Google has been making recently to Home and the way routines are created (new editor, etc.), but I haven’t yet taken the time to explore that properly.
I don’t know when I’ll have a chance to get to it (I have a lot of automations to check). It’s not a high priority for me, but it’s something I’ll try to get to by the weekend. That’s where I plan to begin my search, anyway, and I’d advise looking into something like that if you haven’t already.
Thanks for the reply and thoughts. I do have a few Google Automations and will experiment. Seems strange that a particular Wyze Plug appears to be the only mystery device. Other than Wyze Events and Google Home Activity (both empty) are there any “system” logs that track devices use?
The only other thing that occurs to me is if you have any Wyze Automations. You can see the Automation History by navigating in the app to the Automations tab and tapping the icon that looks like a house with a clock over it to the right of My Automations.
In my particular case, I have some automations that are running in a non-Wyze device-native app, even though those devices are linked to Google Home, because that was easier to do at the time, and that complicates my situation and may be part of my problem. I’m going to have to review what’s happening across several systems, but that’s a problem I created for myself. 
Do have a couple Wyze Automations and checked for activity as you suggested - Only one listed (garage door open/close) which seems correct. Rather than full delete, also tried edit of most used Google Automation thinking (re)Save might fix any corruption. No luck - Mystery Plug on again yesterday. No clues for this occurance other than On sometime mid day when Google Home is typically quiet.
Tempted to nuclear reset - Full Wyze & Google reinstall but installations and setup goes back a long way and worried about getting everything back to normal. More disruption hassle than needed. Anyhow, the Mystery On is not that big a deal, just annoying to not be able, or at least have debug process, to solve.
Thanks again for trying to help.
I thought it was a bulb. Now I’m really confused. 
Sorry, I did somewhat misspeak in original post but got it right in 1st reply to you. Anyhow, it’s a Wyze Plug connected to a lamp.
Thanks for the clarification. I still haven’t set aside time to go through all my automations, so I don’t know if that will yield anything that might be useful to you. I have another thought, though: Do you share this Plug with anyone? I think it’s possible for shared-access users to create Wyze Automations, and that’s another possibility if this Plug is turning on at the same time each day.
Also, is it possible that you’ve enabled Vacation Mode for this Plug? I don’t know about the newer Plugs, but my experience with the original Wyze Plugs is that Vacation Mode turns the Plug on outside the expected times, as if it “thinks” the Plug is in a different time zone than where I actually am.
Simple Plug (model WLPP1-1) with one related Wyze Automation - Turn ON when garage door is open based on Wyze Entry Sensor v2 connected to Sense Hub - Worked perrfectly for literally years and continues to operate as expected. Plug not shared and not configured for Vacation Mode. Mystery ON is very random, somewhat infrequent - Anytime of day, maybe three to six times per week. Trigger time is unknown because I don’t necessarily frequent Plug room often.
I want to make sure I understand: You did check Automation History and didn’t see any unexpected entries there? I don’t have any hands-on experience with any of the Sense Hub stuff, but I’d want to make sure that you’re not seeing evidence that your Entry Sensor v2 is malfunctioning and triggering the Plug somehow since that’s part of the system.
Is it possible that something funky is happening within the Plug itself or with the outlet or wiring where you have it plugged in? If there’s a problem in the circuit, then maybe the Plug is seeing intermittent power fluctuations and then reverting to an “on” state when its power is restored? I’m just grabbing at straws here now. What does Support say?
Everything looks as expected everywhere. Wyze Entry Sensor works with Plug (lamp) reponding ON/OFF to indicate garage door Open/Closed. Wyze. Including actual length of time Door Open/Closed under Sensor; Garage Door Events detail.
Yesterday tried to exercise various Google Home commands, Automations, Wyze devices etc. Could not reproduce problem. Physical wiring issue is low probabilty. Power fluctuations would likely affect additional devices. Plug flaky is possible but difficult to prove as issue is very sporadic.
Wondering - I do have a Wyze Bulb that refuses to stay on WiFi because of physical location weak signal. What if the Plug was occassionally losing network connect? Hmmm… Need to somehow test this.
Thought I’d try to get a little smarter, collect more data, before contacting Wyze support.
Thanks again.
That seems possible, but I wouldn’t expect it to switch the Plug on unless the Plug is just acting goofy or something is wrong with it. 
I understand that. I usually try to do all the troubleshooting I can think of before contacting them. (Then they tell me what steps to take and I tell them that I’ve already done those things. 
)
Mine always turn on when there is a power bump.
I see that happen sometimes with some non-Wyze smart Wi-Fi bulbs that I use, but my Wyze Bulb Colors have been pretty good about respecting the Maintain previous state I’ve chosen in Power Loss Recovery settings. That’s not my particular issue here. I think I’ve got some problematic Google Home routines that are acting up because of all the changes Google has been making lately.
I have something similar happening. i have a outdoor plug that gets trigger and turns on randomly. The plug triggers different groups of lights and switches to turn when it does and when it gets triggered it shows up in the automation history but i’d love to know if there are any other logs i can look into. I’d like to find what is sending the original trigger the plug to turn on. I’ve removed it made it do different functions changed the plug and still the same group of lights turn on randomly.
Welcome to the Forum, @zitro! 
I’m not aware of any other user-accessible log unless you have your Plug Outdoor integrated into another system (like Google Home, as this topic is tagged). That’s been part of my search, and I think in my case disabling some routines that were running overnight has maybe (
) taken care of my issue. I think Google may have botched some routines with their recent changes to Home, but that’s just speculation on my part, and I haven’t checked into the Google Nest Community recently to see if others are reporting issues like this there.
Seems similar to situation here. Only difference, AFAIK, is your Plug is outdoors and I have no indications within the Automation Log. Mystery On was absent for a few days, yesterday several activations. Also tried everything I know to solve.