Could you please check the new TEST version? Tuya Local | Homey
The connection could fail for one of three reasons:
1. Wrong Local Key
Even one incorrect or missing character causes an instant disconnect.
Re‑fetch the Local Key from Tuya IoT to be sure it’s correct.
2. Another system is already connected
Tuya devices allow only one local connection.
If SmartLife, Home Assistant (LocalTuya), ioBroker, or any other integration is connected, Tuya‑Local cannot connect.
Close all other apps and try again.
3. Wrong protocol version
Auto‑detect sometimes fails.
Try protocol 3.3, then 3.4, then 3.1 manually.
Additional minor causes: unstable Wi‑Fi, device rebooting, DHCP changing the IP.
I don’t know what’s going on with me, but none of the sockets are adding. I added two light bulbs without any problems and they work, but the sockets don’t. I guess I’ll have to stick with the cloud 
Could you change the Nous A8M to DP Instruction?
Hi,
Got so far that I can fetch my devices but gets stuck on the IP adress. When I search it finds around 8 Tuya IP-adressen, but how do I know which on is this particular light for example? I can not see the IP-adressen in the tuya app either.
You can view the used IP adresses at the DHCP section of your router.
My advice is to always reserve IP addresses for IoT devices & Homey.
With phone apps named (something like) Network Analyser / Network Scanner / Wifi Analyser / Wifi Scanner, you are also able to view all devices & used IP adresses on your network.
@Damian_Surma
Please check the Availability via Port Scan
Tuya devices communicate locally using specific network ports, most commonly 6668 (and occasionally 6667).
Step-by-Step Instructions:
- Get a scanning tool: Download a tool like Advanced Port Scanner (Windows), Network Analyzer (Smartphone), or use the
nmapcommand in your computer’s terminal. - Target the device: Enter your Tuya device’s specific IP address into the tool.
- Scan the port: Run a targeted scan specifically for port 6668 and 6667.
If the port status shows as open, the device is actively listening for local control commands via the Local Tuya API.
Please let me know your results.
Note that you can also find the Tuya device MAC in the device settings in the Tuya mobile app under “Device info”. You also need this, since Tuya devices show up as either ESP_<last 6 chars of MAC> (for older ESP-based Tuya devices), “wlan0” for newer TuyaMCU-based devices and the newest devices now use “lwip1”. It’s not possible to find the device by just your DHCP leases since the only thing you’d see are 8 identical “wlan0” hostnames. You also need the MAC.
For example, this is a part of my Nebula client list:
You can’t determine which device it is by only the name.
So there’s nothing you can do with these plug?
Are there any other open tcp ports? Could you make a full port scan?
all closed
In that case, I’m afraid my app won’t work for them — sorry about that.
Ok, but thank you very much for your help
Hi eveybody, sorry if my question is not at the right place here.
I wanted to use the TuyaLocal app, because i wanted to be able to control my devices drectly.
But somehow i’mn not able to retrieve the LocalKey(s) of my devices.
I have created a new smartlife account, moved one lightbulb to it, went to the iot site to create an account there and add my device, but I dont get itwworking, it wont let me add/retrieve devices on the iot site, i always get the wrong region message, and I have tried all of them.
According to chatGPT, If i go to the iot site, I get forwarded to a different site that doesnt have the correct options that I need.
I don’t know what to do anymore to get it working (i have read the messages here and it didn’t get me to a solutio, except that I now know that one light listens to 6668)
