ct-Open-Source/tuya-convert

Timed out while waiting for the device to (re)connect

ajvisser99 opened this issue · 3 comments

Hello All,

I have been trying to flash some light bulbs using this, and seem to be running into some challenges. I looked through many other similar issues posted, but have not found one that seems to be exactly the same as mine. I am running the most recent version of Pi OS on a pi 4b.
I am getting the follow.

Starting smart config pairing procedure
Waiting for the device to install the intermediate firmware
Put device in EZ config mode (blinking fast)
Sending SSID vtrust-flash
Sending wifiPassword
Sending token 00000000
Sending secret 0101
................
SmartConfig complete.
Auto retry in 2s. .....................................................................
Timed out while waiting for the device to (re)connect

Attempting to diagnose the issue...
An ESP82xx based device connected according to your wifi log.
If this is the device you are trying to flash, another issue may be preventing it from
Otherwise, it could be that the device does not use an ESP82xx or it did not connect.
For additional information, check the *.log files inside the scripts folder.
Please include these logs when opening a new issue on our GitHub issue tracker.

smarthack-mqtt.log
smarthack-psk.log
smarthack-udp.log
smarthack-web.log
smarthack-wifi.log

Appreciate the help in advance :)

I get the same while trying this on my Tuya GU4 wifi bulbs. The vtrust AP starts, sometimes I can connect to it on my phone, but the bulb doesn't connect to it. I get the same repeated SmartConfig attempts as above and after a while it fails suggesting my bulb isn't vulnerable to the PSK attack that's being used to flash this firmware. Is there a fix for this?

kueblc commented

I see that this is a first generation Tuya device, there is hope yet!

As shown in your web log, it does indeed connect successfully and issue the upgrade command. At that point, the firmware loader is never requested.

I have seen this reported before. It may mean we are missing something in our mocked API responses. It varies between device models and firmware versions. More research is required.

@velkrosmaak without your logs, I can't confirm if your issue is the same or not. Repeated smartconfig is a catch all symptom.

I believe I am seeing the same thing with Techin SP10 plugs

smarthack-mqtt.log
smarthack-psk.log
smarthack-udp.log
smarthack-web.log
smarthack-wifi.log