From the WYZE Socket features.
Welcome to the Forum, @jaimin007! ![]()
I think the use you’re describing illustrates another reason Lamp Socket v2[1] should have full Automations support along with the ability to assign device names because it uses its own Wi-Fi connection to communicate and function. If you’re using Lamp Socket v1, then that requires its special cable connection to a compatible Cam in order to work.
Note that you posted in a topic tagged for Lamp Socket v1, but you didn’t mention which version of Lamp Socket you actually purchased. ↩︎
Thank you.
This is a v2 socket. I did find a way around this. Without physically connecting a camera, I was able to “assign” an existing Wyse cam v4 as “connected” to the socket. This allowed me to get through the setup. Then I configured the v2 Lamp Socket to timer based schedule (and leave the camera motion sensing option turned off). For now, it is doine what I need it to.
Oh, yeah, for sure you can do that, and I think that’s one of the benefits Lamp Socket v2 has over the original version. ![]()
I didn’t see a mention in your previous post that you already had a compatible Wyze Cam, or I would’ve suggested that. I’m glad you figured that out.
So far, I’ve used them with Cam v4s and Cam OGs and found that they generally do what I expect them to do, but I think individual device naming ability and real Automations support would be a big improvement for these, especially since Automations was specifically mentioned in the product page’s FAQ at launch.
