ct-Open-Source / ct-Open-Source/tuya-convert
Did I brick my GHome Smart Plug EP2-A?
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 523
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone,
the title says it already: I need your advice to find out if I accidentally brick my GHome Smart Plug EP2-A, and what I could do about it.
Here is what I did:
Started tuya-convert in docker. I used an external USB wifi Adapter (an old Ralink RT5370). It took several attempts to flash the intermediate firmware. Downloading the firmware backup timed out after some kb. I tried to flash tasmota anyway. This failed.
I then restarted the plug and found the vtrust-recovery network. I connected to it, went to `http://10.42.42.42/` and had this response:
> VTRUST-FLASH 1.5
> (c) VTRUST GMBH https://www.vtrust.de/35c3/
> READ FLASH: http://10.42.42.42/backup
> ChipID: f22890
> MAC: xxxxxxxxxxxx
> BootVersion: 7
> BootMode: normal
> FlashMode: 1M DOUT @ 40MHz
> FlashChipId: 14325e
> FlashChipRealSize: 1024K
> Active Userspace: user2 0x81000
I then tried to roll back by calling `http://10.42.42.42/undo` . The response was
> Rebooting into userspace 1
After that nothing seemed to happen. Eventually I power cycled the plug. Now the LED is on, but when I push the button nothing happens. Also when I push and hold it for 5, 8, or 15 or 30 seconds, nothing happens.
Any ideas what went wrong here? What can I try, apart from trying to open it and flash via serial interface?
Thanks for your help!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported tuya-convert Docker recovery flow and the vtrust-recovery entry points at http://10.42.42.42/backup and /undo. Compare the displayed flash state with the project's recovery documentation and determine whether the plug responds after rollback; the issue is resolved when a safe, documented recovery path is identified or serial flashing is confirmed as necessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100