-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Wyze Bulb Color #7
Comments
Hey: Unfortunately, "porting" to the ESP32 requires writing entirely new firmware that's specific to that platform. Wyze builds their firmware on Espressif's SDKs. The ESP8266 and ESP32 have different, incompatible SDKs with different APIs. I can't use a generic framework like Arduino or MicroPython, either, because those frameworks aren't compatible with Espressif's OTA framework. I do want to make a version for the ESP32 -- I just need to find the time. I also want to make the flashing process for this and the ESP32 easier than it is now. The ideal workflow would be a "single-click" python installer that directs the Wyze device directly to GitHub for the wyze plug flasher and Tasmota binaries. The current flashing process sucks. I have a copy of the firmware from an ESP32-based Wyze Plug. A firmware dump from the new bulb would be great for testing (if you already plan to crack it open). Thanks! |
Any details on dumping firmware from an esp32? I've got a couple of the color bulbs and I'd do what I could to get towards local control of them. |
Schematics for the ESP32-based Wyze Plug are here. The new Wyze bulb is probably the same. There are two options for pulling firmware. Whatever method you choose can also be used to flash Tasmota onto the chip, so this isn't a total waste of effort. For either option, use a brand new bulb or factory reset an existing bulb. This will clear the WiFi credentials and account data from the extracted firmware. You can post the firmware here to email it to me. (I don't want to post my email address to the crawlable web. Click on "Email Me" at elahd.com.) Extract via SerialThis is probably the easiest method.
Extract directly from flash chipThis method is a huge pain in the ass, but it was the only one that worked for me. I'm a mediocre solderer and burned off the serial pads on my Wyze plug.
Thanks for your help! |
I did open one of the bulbs. You will have to destroy it to get to the ESP chip. They filled it entirely with the gray epoxy that I have seen before on bulbs. I assume for heat build up issues. Other disappointing thing was no cool white channel. Only warm white. It would have been awesome to have 5 channels. |
How does the bulb do color temperature then? Are you sure they aren't using dual channel white LEDs? |
It was mixing in blue and green on the warm white. |
Impressively convincing, I could have sworn they were built like the cheap MiLights with dedicated white/warm white LEDs. |
Opening this issue for discussion more than anything.
What would it take to bring support to the new RGB+CCT Wyze Bulb? I know it has an ESP32 inside and (as per #5) I'm aware that the ESP32 isn't supported by this tool yet.
Any chance just changing the build target to the ESP32 instead of the ESP8266 would work? I know there is some cross-compatibility in the libraries available for both. I'm willing to break one open to get serial access and dump the firmware if that would help.
The text was updated successfully, but these errors were encountered: