KS-632-1 Smart Wall Socket Device did not appear with the intermediate firmware

This device came in a box like previous KS-621 Smart Wall Socket, which is possible to convert with tuya-convert. There is a template for tasmota, etc. The appearance of the devices are the same.

Using the factory recommended android program after paired it says the type is KS-632-1
The problem is tuya convert is not possible (for me).

Here are the logs:
[smarthack-mqtt.log](https://github.com/ct-Open-Source/tuya-convert/files/5879202/smarthack-mqtt.log)
[smarthack-psk.log](https://github.com/ct-Open-Source/tuya-convert/files/5879203/smarthack-psk.log)
[smarthack-udp.log](https://github.com/ct-Open-Source/tuya-convert/files/5879204/smarthack-udp.log)
[smarthack-web.log](https://github.com/ct-Open-Source/tuya-convert/files/5879205/smarthack-web.log)
[smarthack-wifi.log](https://github.com/ct-Open-Source/tuya-convert/files/5879206/smarthack-wifi.log)

```
The screen:
# ./start_flash.sh
tuya-convert v2.4.4
Checking for network interface wlan0... Found.
Checking UDP port 53... Available.
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking UDP port 6666... Available.
Checking UDP port 6667... Available.
Checking TCP port 1883... Available.
Checking TCP port 8886... Available.
======================================================
Starting AP in a screen
Starting web server in a screen
Starting Mosquitto in a screen
Starting PSK frontend in a screen
Starting Tuya Discovery in a screen

======================================================

IMPORTANT
1. Connect any other device (a smartphone or something) to the WIFI vtrust-flash
This step is IMPORTANT otherwise the smartconfig may not work!
2. Put your IoT device in autoconfig/smartconfig/pairing mode (LED will blink fast). This is usually done by pressing and holding the primary button of the device
Make sure nothing else is plugged into your IoT device while attempting to flash.
3. Press ENTER to continue

======================================================
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.
Resending SmartConfig Packets
.................
SmartConfig complete.
Resending SmartConfig Packets
.................
SmartConfig complete.
Resending SmartConfig Packets
..............................................................................................
Device did not appear with the intermediate firmware
Check the *.log files in the scripts folder
Do you want to try flashing another device? [y/N]
```

Please help, if you can.

Start with the linked smarthack-mqtt.log, smarthack-psk.log, smarthack-udp.log, smarthack-web.log, and smarthack-wifi.log, then trace the intermediate-firmware step invoked by start_flash.sh. Compare the KS-632-1 behavior with existing device support; done means reproducing the failure and documenting either a compatible flashing path or that the device is unsupported.

Written by the indexing model from the issue text.