No effect on WLPP1 with firmware 1.2.0.80 - Githubissues

elahd / esp2ino

OTA Third Party Firmware Flasher for the original Wyze Plug (WLPP1) and Wyze Bulb (WLPA19).

MIT License

53 stars 4 forks source link

No effect on WLPP1 with firmware 1.2.0.80 #12

Open mwhdc opened 3 years ago

mwhdc commented 3 years ago

Thanks for publishing and improving this package!

I have been trying 0.3 with two original Wyze Plugs without success. They have static IPs and connect to the Wyze app without issue. Running wyze_updater_macos authenticates and lists devices successfully, and appears to push the bootloader to the plug, but the plug doesn't reboot - its status in the Wyze app changes to offline, but it can be pinged, although it's not serving the esp2ino GUI on port 80 as expected. After a minute or two, without unplugging/rebooting, it shows as online in the Wyze app again and can be controlled.

Has anyone had success with firmware 1.2.0.80?

elahd commented 3 years ago

Just tested this on my end. GitHub forces the browser through a few behind-the-scenes redirects when downloading the binary. It looks like Wyze firmware 1.2.0.80 doesn't play well with redirects. The plug will try to download one of the initial empty pages for a few minutes, then gives up and reverts to factory firmware.

Give me a few hours to spin up a server.

mwhdc commented 3 years ago

Hmm, I just uploaded esp2ino.bin to a web server on my LAN and tried pushing the URL to a plug. Same outcome as the Github URL. Tried URLs with hostname and IP address, confirmed the URLs started a download in a desktop browser.

elahd commented 3 years ago

The Wyze firmware will only download over SSL/TLS. (It only checks that a cert is present—it's doesn't look for a specific issuer.) If your local server was insecure, that may explain why the file wouldn't download.

I'm hosting the binary on my own server and confirmed that this URL works with my development device. Can you give it a try?

https://ota.elahd.com/esp2ino.bin

mwhdc commented 3 years ago

That looks like it worked. Unfortunately it also seems to have bricked the plug. The plug didn't rejoin my network and it's not advertising its own SSID. Pressing or holding the button doesn't engage the switch or flash the LED.

elahd commented 3 years ago

Shoot. The firmware doesn't use any of the IO devices, so not responding to button presses is expected, but it should broadcast an SSID after 2 min of trying to connect to Wi-Fi. Can you try power cycling and waiting a few min? You can also try the "Manually Connecting to Wi-Fi" steps in the troubleshooting guide.

mwhdc commented 3 years ago

I tried a few power cycles last night and again this morning, same result. Did a Wi-Fi site survey in case the SSID was hidden and didn't find anything. The ESPTouch UI isn't super intuitive but I didn't get anywhere there either, on iOS or Android. I may have to pop this one open to get Tasmota on it. I have one more plug on the same firmware for future testing.

elahd commented 3 years ago

If you're already popping this one open, would you mind sending over a flash dump for analysis?

elahd commented 3 years ago

I'll test on a fresh plug over the weekend, as well. If I can load esp2ino onto that plug without opening the case, I wouldn't mind exchanging it for your bricked one. I'm going to want to break open a new plug, anyway. Might as well be yours. I'll keep you posted.

mwhdc commented 3 years ago

I'd be happy to send the brick. Let me know. I've serial flashed a few easy Sonoff devices, but this plug is getting above my pay grade. I'll try to unglue it over the weekend.

elahd commented 3 years ago

Haven't forgotten about this. Looks like Amazon is commingling stocks of WLPP1 (ESP8266) and WLPP1CFH (ESP32). Waiting for another shipment to arrive.

elahd commented 3 years ago

@mwhdc Send me your mailing address. I'll send over a replacement with esp2ino preloaded. Contact info on elahd.com.

dpackham commented 3 years ago

can we also try your URL or will that still brick the device after? I have 4 plugs in the same scenario as the OP

elahd commented 3 years ago

@dpackham I pushed v0.4 (released today) to the OTA server, so you're clear to try again. The install workflow changed a bit with this release -- check the wiki for details.

mwhdc commented 3 years ago

I tried the 0.4 release with my other WLPP1 on 1.2.0.80 and it worked, with some caveats.

The plug wouldn't join the Wi-Fi network that had been configured in the Wyze firmware, but it did broadcast the esp2ino SSID, which I was able to join
When I entered Wi-Fi credentials in the esp2ino web UI, it couldn't join and went into safe mode. It would not exit safe mode via soft reboot
I finally cut and restored power to the plug, which brought back the full esp2ino web UI
I uploaded tasmota.bin from a local file. It installed successfully and began broadcasting a Tasmota SSID
The plug's MAC address changed from a Wyze range (2C:AA:8E...) to an Espressif range (BC:DD:C2...)
I had to manually update and activate the template on the Configure Other page of Tasmota's web UI

Thanks for the ongoing improvements! This release was a big step forward.

dpackham commented 3 years ago

ok, I tried it on 1.2.0.93 and it blinks for a minute then nothing. Do I need to reset the plug? default it?

sorphin commented 9 months ago

Just for reference.. I had/have some old pre 2021 plugs (that were running 1.2.0.56).. tried it, got the plugs to accept the firmware using --ssl, dns spoofing, etc... and.... they worked... with V0.4... (I thought they had bricked, but then when I hooked up after cracking them open, I saw the esp2ino AP)..

siretart commented 5 months ago

@sorphin I have two WLPP1CFH plugs with firmware version 1.2.0.53 around, but I can't get around #16 -- can you please share some updates how you got around that and got them to accept the firmware?