Any issues with Wyze Switch and Automations today?

Power & Lighting
, , ,
21

@Seapup thank you for modifying the topic and tags! :+1:

I was thinking this should be done, because Iā€™m seeing it with Bulb Colors where Iā€™ve used Device & Service Trigger Automations, so I think itā€™s more of a back-end Automations issue than anything else.

I think thatā€™s right. I had some Bulb Colors set to turn on at 2026-02-17T06:10:00Z, and my Triggers shouldā€™ve turned them off not long after that, but none of those are showing up in the Automation History.

Welcome to the Forum, @blueshore, @this.guy, @theandychase, and @jsb! :wave:

1 Like
22

I am currently having the team look into these issues.

2 Likes
23

Thatā€™s the same thing I noticed.

1 Like
24

Donā€™t know what was fixed ā€˜service wiseā€™ but all my automations are now working again.

Would you mind posting what happened and let us all know?

4 Likes
25

FWIW, resolution is also being reported in Service Advisory - 2/17/2026.

1 Like
26

It appears that the issue was solved. Had to remove the workaround and do some minimal adjustments, but everything is working again. Thank you to everyone that created a ticket and reported the issue.

2 Likes
27

That will be great. For the way it happened it appears that it was a service-side issue that was unable to dispatch the proper messages after receiving the requests. Considering that most devices need to establish a connection to the service-side, we talking several thousand devices per instance (or serverless functions). At least my best guess is that several of those dispatchers were unable to send the commands back to the devices or the switch commands were receive but not processed, which makes sense for me since my pcaps indicated data exchange.