Blitzwolf LT-21 Dead

Hardware
1

I just purchased one of these smart bulbs. It worked fine out of the box. I then decided to flash OTA with Tuya however this failed. THe bulb now appears to be dead. No Ip address, it wont come on with the on/off 3 times process, nothing. Perhaps my continually putting it into pair mode (on/off three times) caused it to die. Any ideas at all please…

2

I have noticed a SSID of vtrust-recovery which I guess is promising, but I have no idea what to do from here?

3

Unplug the device, run start_flash again, and plug it back in.

4

I followed this guide http://www.thesmarthomehookup.com/tuya-convert-walk-through-february-2019/#comments THere is no run start_flash. Appreciate your help.

5

I type this:

pi@raspberrypi:~/tuya-convert/tuya-convert $ ./start_flash.sh
tuya-convert v2.4.3
AP mode not supported!
Please attach a WiFi card that supports AP mode.
======================================================
Cleaning up...
No screen session found.
No screen session found.
No screen session found.
No screen session found.
Closing AP
Exiting...

Do I also need the RPI to have a wireless connection?

6

The pi needs to be connected with both cable (working) and wireless (not assigned). Tuya-convert creates an AP in order for your device to think it is connected to a tuya-server.

Edit : read this :

I use an old raspberry pi 1 with a wifi dongle :slight_smile:

7

Many thanks. I’m now making progress. I think it was stuck in first stage. I started this six months ago but got stuck and left it, now got time to burn! I also obviously forgot the RPI needed WiFi as well as cabled ethernet. To be fair I don’t think the article I used this time was clear on that point. Really appreciate your help though.

8

Hello,

I have installed both kali and ubuntu on pi3.

Both connected with a TPlink TE7WN725N wifi adapter. all running fine but I get:

ubuntu@ubuntu:~/tuya-convert$ ./start_flash.sh
tuya-convert v2.4.4
AP mode not supported!
Please attach a WiFi card that supports AP mode.
======================================================
Cleaning up...
No screen session found.
No screen session found.
No screen session found.
No screen session found.
Closing AP
Exiting...

What can be wrong?

Edit: RPI connected via ethernet and SSH via that IP.

9

Seems the TpLink does not support AP mode.

On a Pi3 you should be able to use the built-in Wifi

10

I think my pi was a 2… :see_no_evil:. Would a pi 4 be ok?

11

A Pi4 would be ok.