@bobradarbob I’d be interested to know what happens if you delete the bulb and then re-add it to your account. If it starts exhibiting the same behavior as the rest of us, it would confirm a few things. That said, I would hate for you to end up in the same situation as the rest of us, so only try it if you’re willing wait until Wyze gets this fixed. I’m still kicking myself for doing this to two of my most frequently used bulbs.
To reiterate, my experience is that the issue arises ONLY after a bulb is reset and successfully paired. I have 9 v1 bulbs and 7 continue to work without issue. All of them are on the latest firmware. But the two affected are the ones I deleted and re-added.
If @bobradarbob 's bulb can’t be operated after deleting and re-pairing it’s as if all v1 bulbs are “infected,” but they only become “symptomatic” under specific conditions—namely when they’re deleted and re-paired to the account while on the latest firmware.
@WyzeDesmond, as I mentioned in my DM, I’m not sure how often users encounter these conditions, but it seems unlikely there would be a noticeable drop immediately after a firmware release—most people don’t delete and re-pair their bulbs with every update.
I am generally staying out of this conversation/thread. My issue with the 2019 bulbs is different from everyone here.
I cannot get to the temporary bulb network, but let them (Wyze) focus on your problems. Maybe mine will fall in line. No sense in adding stray comments. I will be curious to see what they find out.
In the meantime, I went with Kasa but I can hold onto these bulbs just in case there is a resolution.
Same issue. New router installed, one v1 bulb working fine, several others no go. Go through pairing process, app shows paired, no control over bulb whatsoever. I have been a big fan of Wyze for years, have invested in numerous cams and bulbs. I’ve had issues in the past that were resolved in a positive manner by the Wyze folks. I do expect a fix for this or an offer to replace the nonfunctioning bulbs.
Today, the last of my 2019 bulbs disconnected and showed as offline. I am unable to add them back with the app control error as noted by various replies in this thread. This occurred after I made a DNS change on my network ( setting up pi.hole ) . Perhaps that may be useful to someone working on this.
@FrankyJ@WildBill - @WyzeJasonJ has said in a private message that: “from the numerous reports that have come in it is obvious something is going on that is NOT user error. I think, but am not sure, that part of the issue was the slow speed that this started to show up since it seems to take re-adding the bulb to cause the issue.”
They have also stated that they believe the issue is related to their firmware. I have sent my affected bulbs to @WyzeDesmond and the team to diagnose. They arrived, per USPS, yesterday.
I remain concerned because if it IS firmware related - then I don’t see a clear path to fix the issue for all those currently affected (how can you push a firmware update if the device cannot stay connected to Wyze’s servers?) For everyone’s sake, I hope it is not a firmware issue. While Wyze sent replacements for the bulbs I sent in - I still have seven v1 bulbs that are “infected”.
Regarding DNS sinkholes - I have one on my home network (pfblockerng in my case) and my issues showed up after moving my bulbs to a vlan where it is NOT enabled. Furthermore, my pcap showed that the bulb DID connect to Wyze’s servers before the connection was terminated (I suspect that’s why the bulbs can be added to your account before being rendered inoperable).
Quick questions regarding internet connection here. Are any of you currently using WPA2/3 or WPA3 only for WiFi encryption? We do find that 2019 version bulbs don’t support WPA3. We are still investigating other issues. Thank you for your patience.
And if you have an open support ticket please feel free to pass to me. Thank you!
All seven of my remaining v1 bulbs (you have my other two) are connected to these networks and working fine.
I have been thinking - if you all are relatively confident that the issue is with the firmware, have you explored reverting these bulbs to the prior firmware as a temporary measure while you diagnose further?
