Bulb unresponsive, talking to Wyze cloud, shows up in app

I turned my WiFi network off for about an hour because I moved an access point to a different room, and then decided to move it back to its original location.

This access point was for my main WiFi network. All my IoT devices are on a separate physical network with different access points, different network cables, different switches. I turned ALL the access points off for testing purposes, and then powered them all back on when I was done.

When I turned everything back on, all of my devices (2019 Wyze bulbs, Wyze color bulbs bought in 2020, Wyze color bulbs bought in 2024, Wyze indoor plugs from 2019 and 2020, Wyze outdoor plugs bought in 2024, and Wyze smart switches bought in 2023) came back on and started working immediately EXCEPT for the four Wyze bulbs from 2019.

I went through the trouble shooting steps of doing a factory reset on the trouble bulbs, deleted them from the Wyze app, and left them in a drawer for three days. Then I went through the steps of adding them to the Wyze app.

Each bulb connected to the app. The app showed them to be online. I could turn them on/off, adjust color temperature, and adjust brightness, from the app, HOWEVER the bulbs themselves would do nothing.

Eventually the bulbs would pulsate as though they were ready to be paired, despite still showing as online in the app.

I assumed a network issue, so I ran tcpdump on my firewall to generate packet captures, and look at them in Wireshark. I also used tcpdump to view the network activity of the bulbs in real time.

What I found is twofold :

(1) The working bulbs have almost zero network traffic, except for when I issue a command from the app, which is the expected behavior

(2) The trouble bulbs have nearly constant traffic to the Wyze cloud (api.wyze.com hosted at Amazon AWS). In Wireshark, I was able to see that the connections to Wyze were being rejected by the Wyze cloud.

So unless my eyes deceive me, it looks like Wyze rejects connections from old bulbs once those old bulbs have a significant network interruption, but the bulbs are otherwise in working condition.

If I were a nefarious person, what I would do is set up some sort of logic in my cloud servers that would reject old bulbs that had lost connectivity for more than 30 minutes because most customers would assume the bulb stopped working for reasons related to whatever caused the network outage, and not because Wyze decided it was time for those customers to buy new bulbs.

I’m not trying to uncover any grand conspiracy, I just want the light bulbs that are still in working condition that I already paid for to continue to be allowed to function properly by the company I bought the bulbs from.

4 Likes

Interesting findings and conclusions.

Adding the bulbs fall short of seeing the temp network for me.

2 Likes

please ignore my last response - it was for a spam bot on Instagram and I pasted it into the wrong window :sob:

This seems to be a pattern by now. There are at least two recently updated threads (here, here) where folks are dealing with an identical issue. @WyzeDesmond indicated that he was looking into it but there haven’t been any updates in the last few days. I had the same problem with my 2019 bulbs, except that strangely, one of them works as expected.

2 Likes

@NozeDive @ssummerlin @nathan.rein Yes thanks for the waiting and sorry for the delay. We are still investigating the issue but getting close. Could you please do me a favor and submit applogs after binding fail? (There wil be no bulb to choose when submitting logs but please choose app&service and then fail to setup) Thank you so much!

1 Like

Hi @WyzeDesmond ,

I tried as you said but I get a screen where submit is not working. I tried a few times. What am I missing?

Thanks.

Try typing something in the Details area?

1 Like

Thanks. Sorry I missed that
I tried clicking the + sign but never thought of text.

2 Likes

No problem… it happens. :+1:

2 Likes

Thanks we are checking with this log.

Just to confirm, All the issues currently are “fail to bind”? Are there any issues like “binding successfully but fail to send any action/command to the bulb, and bulb is showing “offline” after binding”?

2 Likes

Facing this exact same issue, binding successfully but fail to send any action/command to the bulb.

The bulb was working previously and upgraded to the latest firmware 1.2.0.384 but now when I try to set it up again the app says binding complete but is unable to communicate with the bulb. The bulb also exits setup mode when binding is complete but in a while reenters setup mode. I can see the bulb on the wifi network so it’s definitely connected to the wifi at least.

I also submitted a log with the bulb: 1513514

2 Likes

WyzeDesmond -

Thanks so much for looking into this issue! I joined the forums just to share that I’m experiencing the same problem many others have reported. My situation closely matches NozeDive’s experience.

For me - I tried moving my working 2019 bulbs to a new VLAN on my network. When I added them, I received a “binding successfully” message, but then the bulbs couldn’t be controlled from the app. Thinking the bulb might be the issue, I tried it with a second one and ended up with the same result. Both bulbs reset after a delay. Both worked before resetting.

It’s really clear from the behavior (and my network traffic) that this is an issue on Wyze’s end.

I’ve submitted a log to support, which can be found here: log ID - 1506342. I’ll confess that I was very disappointed to be told by a Wyze support representative that I just needed to update my app and hope for a fix at some point.

Given the number of posts on this topic (which likely represent only a fraction of those affected), I’m also curious why this isn’t acknowledged as a known issue here: https://support.wyze.com/hc/en-us/articles/360032747431-Wyze-Software-and-Firmware-Bugs-and-Known-Issues.

Please advise and thanks again for your help on this issue!

3 Likes

As mentioned in another thread, I am having this exact same issue now. App log submitted: 1526224

2 Likes

Having the same issue with two bulbs. Submitted a log. 1537128

1 Like

I am facing this same issue. Hooked up 4 bulbs (all 2019 version) and 2 show to be online but unresponsive to commands.

Here are the uploaded log file numbers:

1543902 - DR 2

1543904 - DR 1

1 Like

I have 4 2019 bulbs, hooked them all up, working, updated to the latest firmware. Decided to segregate my network and upon resetting these 4 bulbs they complete the setup and the app sees them but you can not control them at all, what is the resolution here Wyze? This is your firmware that is causing the issue.

Send in a log and copy @WyzeDesmond .

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.