-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
Cannot flash Topgreener TGWF115APM #1057
Comments
I am experiencing the exact same issue attempting to flash TopGreener Smart Plug: TGWF115APM. I also have the same version 1810 Ver 1.0.1 printed on the device. I am using a Rasberry Pi 4 running the tuya converter using docker. But seeing the same issue with smartconfig procedure looping with no success. |
Same here though I have a 1906Ver1.0.1 but the wifi chip has the same markings. console.txt |
I tried an unused one that I bought a year or so ago, that had never been connected to the app, and it didn't work either. Since it was never connected to wifi or the app I don't think it was a recent update that prevents this |
Hi, In the end this modified procedure allowed me to flash my devices: Regards - MacSass |
I'm able to connect to the vtrust-flash SSID from the 2nd computer (Android tablet) and I can see that my TopGreener device also connects to it.
When I put the device in pairing mode before starting tuya-convert here is what it happens:
|
I had exactly the same issue for 3 of my 5 devices ... |
where can i get appconfig.py? I don't see it in tuya-convert folders |
Hi, Good luck, it worked perfectly for my devices that I had not been able to flash for weeks trying everything I could think of! |
Topgreener TGWF115APM, device is printed with "1810Ver1.0.1" on it. Using a Raspberry Pi 3B V1.2 to flash
There seems to be a fault in smarthack-psk.log
edit: cracked it open and here's the markings on the chip.
PN - TYWE2S
Code: TWF15PM
Console.txt
smarthack-mqtt.log
smarthack-psk.log
smarthack-udp.log
smarthack-web.log
smarthack-wifi.log
The text was updated successfully, but these errors were encountered: