If Google is anything like Alexa, it is not Wyze automations that signal it, it is Alexa skills that pull the Wyze automations.
That might be the issue. You need Google or Alexa powered devices for it to work.
If Google is anything like Alexa, it is not Wyze automations that signal it, it is Alexa skills that pull the Wyze automations.
That might be the issue. You need Google or Alexa powered devices for it to work.
well, since you cannot add the nest as a device, then there is no way for an automation in WYZE to signal it. that suggests that the automation has to be created in google home.
At this point - we’re way off center from the original simplicity of flashing a light bulb I think.
Also - the additional complexity makes it more likely to be prone to fails.
I also seriously think there are limits of what can be done with external assistants when the source of the notification comes from another household - eg across the internet.
As to being confused by something in a UI - that happens, and i usually can figure stuff like that out.
In practice i find that detections are fairly accurate. the signalling of events however - can be lost. especially if the camera is busy, or if the internet is slow… Cameras seems to be rock solid for local recording, but that might be their highest priority task. as for intelligent detections - only some of that appears to be done locally by the camera. 'person detection i sense - requires a check in with the wyze server - so that’s a point of potential failure. The light bulbs - are especially weak when it comes to losing a signal. it’s a little hard to troubleshoot those since the automation history only indicates the device was online and ‘maybe’ it was signalled, and 'maybe ’ the device got the signal. using an external device with more sophisticated automation than wyze would be fruitful, since i suspect that the assistant could act as a surrogate device manager and poll the signalled device for it’s state, and do things like looping on condition etc. the native wyze app as well as the device processing have inherent limitations.
going back to the OP - the usefulness was in both the simplicity. it’s rather reliable and takes no interaction on mom’s part. Those things are pretty fundamental in elder care and monitoring solutions
I don’t know as I don’t own Google or any nest devices. From what I’ve read on this forum Alexa and Wyze are pretty well integrated. I have three Alexa devices but I haven’t any Wyze automations linked as here in Canada, Alexa and Wyze integrations are not supported without a US account. In my case, I don’t need any so I haven’t bothered to integrate them. I use my Alexa devices for simple tasks, turning lights on/off, listening to music and such. I was just trying to shed some light as to how you can integrate them in your scenario if you ever needed them.
I was looking for a way to monitor my partner while I not at home. She had mobility problems due to many years chemo.
When Wyze added smart lights and the V1 Sensors, I was able to add more ways to help her. I put a contact sensor on the cabinet door that held her meds. I set it up so I would get an alert whenever the door was opened. If she was asleep or forgot, I would get her attention to remind her. I put a couple of Wyze Bulbs in a floor lamp and built a box with a couple sensors so she could slide the knob one way to turn them on to 30%, slide it the other for 100% and put the knob in the middle to turn them off.
I also made her a “big red button” device if she needed me for anything. When she activated it, smart lights and plugs would flash on and off 5 times in various rooms in the house: my bedroom, bathroom and basement.
And it all started with a $20 camera! Thanks Wyze! ![]()
That’s correct as I understand it. The Wyze app also doesn’t know about Alexa via Automations, either. Actions with Alexa are handled on Alexa’s side via the Wyze skill and/or enabling the Alexa integration in the Wyze app as @habib indicated.
Google Home and Amazon Alexa can perform some actions on connected Wyze devices through their own routines if they “see” something happen to a Wyze device, but they don’t have access to the full range of Automation Actions available to Wyze devices in the native Wyze app, which is why a lot of community members will use things like Wyze Plug as a logical switch or bridge to hand off control from one thing (say a Wyze Automation) to another (say a Google Home routine).
I think that’s correct, as well. My experience with smart home devices started with a Smart Light Starter Kit that included a Google Home Mini (1st Gen smart speaker) and a C by GE smart Wi-Fi bulb. The Mini was necessary to get the bulb to work, because it acted as a hub or bridge for the Google Home implementation, and I think something like that would be necessary if you wanted to explore these kinds of cross-ecosystem automations and integrations.
This is also my understanding.
This would depend on what you want to accomplish. You can’t add a Nest device directly to the Wyze app, but a Nest device could certainly work as a hub for other smart device control if added to a home in the Google Home app, and other devices (like a Wyze Plug) can act as an intermediary signal between the two environments, allowing an automation from one to trigger an automation in another.
I’d think that Echo devices (in your home and your mom’s home, if you wanted to expand the automations that you’re doing) might be a better fit, though, because of the “Drop In” feature that works as an intercom, though it’s not something I’ve ever personally used, and I’m not sure how effective that would be with someone who has a hearing impairment (unless you maybe used Echo Shows and had an automation to flash the lights a certain color when calling your mom on the display).
If you’re accomplishing everything you want to do at this time, though, then I agree that adding complexity to the system has the potential to add more problems and points of failure.
Just to be clear… the integration of Google or Alexa is seen in Google Home or the Alexa app.
Once you have your devices integrated, they show up in your HOME to organize into rooms and use Google’s version of smart Automation with Triggers and Geo-Location Events. Google also is “Family” aware and will only do things if both persons are not at home.
Google Home is just like the Wyze App and just like the Alexa App. If you buy 3rd party lights or cameras, you “link” those accounts in Google Home and then Google can manage those too. Govee, Lifx, etc…
Everything I said is the exact same for Alexa App. But the automation stuff, like voice commands on Wyze triggers, is really good. I would suggest investing in 1 or 2 Alexa speakers and playing with it. It’s worth your time.
I have the driveway cameras blink my family room light strip and a color light bulb and increase the brightness of my front door light.
The thing is, I normally have these lights on in the evening and after they blink, they are turned off, instead of going back to their previous color and setting. I would like the blink action to return the device to it’s previous state.
Does anyone have a way to do this?
I have blinks on both color bulbs and light strip and they return to their prior state
My lights go back to their previous state after blinking. Do you have the power settings of the bulb to “go back to previous state” after a power outage?
I wonder if that is the setting?
All of the affected devices were set to power on after a power loss. I changed it to return to previous state and will see if that makes a difference.
A unique feature of Wyze switches is that they can be set to allow smart bulbs to not lose power when switched off. Use like a regular switch: on/off, but the app program can be optionally set to leave enough power to keep the bulb settings. So grandma can turn the lights on/off in the bathroom as normal, but the bulb can be flashed regardless.
That’s pretty cool. I’ve thought about it for some non-light applications but haven’t yet gotten my hands on any Wyze Switches.
“So grandma can turn the lights on/off in the bathroom as normal, but the bulb can be flashed regardless.” - the power switch has to be on for the lights to flash.
As the bulb remembers the last state, then if the bulb is “on” in wyze, then mom ( grandma died in the 90’s) can use the bathroom light like normal - it’s on or off at the switch.
So, when mom is in the bathroom, she has to turn on the light at the switch in order to get a blink when someone is in the driveway.
Conversely - the light on the clip light in the computer room - is always on at the switch, but is ‘off’ in the wyze app. so if someone comes into the driveway - it flashes.
Again - the intent is that mom doesnt have to know anything except that the blink means someone is in the drive. she uses lights normally from the wall switch.
I also get a blink when a person is in her drive at my house two miles away. i use blue for her house. red when someone is in my driveway and green for my fiance’s driveway.
The wyze switches are like regular switches, but they also have double tap , triple tap ( which i can never get right) and long press . so you can one tap - click on the bathroom light with normal bulbs… i use long press to turn on the dresser lamp and bedside lamp at 30%… you could make the siren go off on a cam if you wanted or use your imagination… it’s a switch plus a three way remote sort of… too bad they dont make a hand held programmable remote, huh?
I’m aware of the additional tap and hold features with the Switch; I’ve just never had any to use myself.
It’s too bad they stopped making the Watch. I still wear mine and use it for launching app shortcuts, so it’s kind of like a wearable remote.
My problem with the lights getting turned off is that it is not consistent.
It seems like the light strip is most susceptible to being turned off after the blink event caused by a camera notification. The light bulbs only get turned off, sometimes.
I also had that problem with another non-Wyze product: I grouped some switches to all turn on/off when I command it. Trouble was, two devices integrated into the same switch behaved irregular. One or the other would often fail to respond. I would get a message that the Wi-Fi was weak, but they were built into the same device, so why did one work, but not both? I figured out that the message was too fast for the devices to respond.
I resolved it by adding a 1second delay to the automation command betwixt devices. Problem solved.