@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).