tuya-convert icon indicating copy to clipboard operation
tuya-convert copied to clipboard

Stuck at Starting AP in a screen

Open andrewprime1 opened this issue 3 years ago • 5 comments

I am somewhat of a noob with regard to the command line, so I am going to just give as much detail as I can as I don't know what is pertinent. Running Tuya Convert on a Raspberry Pi and have successfully flashed several devices with this setup over the last 18 months. Followed this guide initially for the setup. Just today, before attempting a flash, I ran the get update, get upgrade commands to make sure everything was up to date. Connecting to the Pi via PuTTY

After starting Tuya Convert with sudo ./start_flash.s I am getting stuck at "starting AP in a screen". It just freezes up there and the terminal will not accept any other commands and I have to go unplug my device to reconnect. It may be worth noting that the vtrust-flash wifi network does come up and I am able to connect to it with my phone. I tried reading through the issues section here and doing some Googling, but I haven't found any solution. Any tips?

andrewprime1 avatar Jan 13 '22 22:01 andrewprime1

Did you find a solution for this issue? I am having the same problem.

xbavnu avatar Feb 26 '22 16:02 xbavnu

Very late response, but the issue (at least for me) was that I was only using wi-fi. Since it starts a hotspot, it ends up disconnecting from the wi-fi network. This would break the SSH tunnel, which lead to it being stuck at that stage. It either needs to be controlled directly (keyboard/mouse) or connected to Ethernet as well.

AritroSaha10 avatar Apr 08 '22 03:04 AritroSaha10

I had the same issue today. The problem seems to be the SSH connection. The terminal did freeze. But when I connected the Pi directly to monitor + keyboard it worked.

BJDayzz avatar Nov 24 '22 01:11 BJDayzz

i have the same issue with 2 separate raspis... both are connected with WIFI, could this be the Problem?

luckiesdavid avatar Jul 19 '23 21:07 luckiesdavid

I encountered this issue on my laptop+docker. I resolved it by disconnecting from my wifi network and disabling auto connect on that network.

dominicdoty avatar Sep 20 '23 03:09 dominicdoty