As far as I know, the Cloud Lookup function logs into your Tuya account on the Tuya IoT portal. In order for the app to then use the required API to obtain your device details, you need to have an active (free) subscription. Otherwise the API won’t work.
I start to use this app, just a question: it’s necessary a DHCP reservation for every device? I try to find answer but I don’t find it
How to fix the “your ip(xxx.xx.xxx.xxx) don’t have access to this API” error?
I get it from within the app, and also when I try the API Explorer.
I’m using the same project I’m currently using for the Tuya app (cloud), but I would like to migrate to local since the cloud app has been really unstable the past days
You’ll have to wait. In my experience extensions are approved within hours.
I am not sure whether you can look-up the local key and data points of each device manually in the mean time via the IoT portal. I think that also uses API calls.
It’s not required, but if the device’s IP address changes, you’ll need to update the new IP address in the device configuration as well.
Hello, my 4 fans are working perfectly. I’m keeping the Tuya app, though. However, do I still need to keep extending the trial period for the Tuya IoT platform?
No,
it doesn’t use any cloud service in daily use mode;
Please be specific (there’s several Tuya apps);
Anyhow, you only need this Tuya Local app to control your local connected Tuya wifi devices.
Yes,
for adding new devices:
In case you want to add new devices, you’ll need a working iot subscription in order for the “Fetch devices” to be functional:
I just renew the subscription twice a year.
When I recall correctly, Tuya sends you a reminder
Since the last update, the night light works, but the ringing still doesn’t. I’d appreciate your help.
TürklingelLokal (doorbell)
Last update: 13.8.2026, 17:00:45
DP Value Type
4 false boolean
6 false boolean
Türklingel
DP 1 doorbell_list_data Raw AgQCAQwIXgD/FgBUAPwAcgBrAGwAaQBuAGcAZQAgADE= maxlen 128
DP 2 doorbell_ring_value Integer 8 0–32 step 1
DP 3 doorbell_volume_value Integer 94 0–100 step 1
DP 4 switch_night_light Boolean false {}
DP 5 alarm_message Raw AFQA/AByAGsAbABpAG4AZwBlACAAMQ== maxlen 128
DP 6 alarm_propel_switch Boolean false {}
DP 7 disturb_time_set Raw PMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD/zzDPMP/PMM8w/88wzzD maxlen 128
DP 10 doorbell_call value 1 1–8 step 1
Thanks for the DP table, that pinned it down.
Look at what your device actually sends over the local connection:
DP 4 false boolean
DP 6 false boolean
Only those two. The longer list you posted is the cloud specification — what the device is capable of — but DP 10 (doorbell_call) and DP 5 (alarm_message) never arrive locally at all. So no ring data point is reaching the app, and no setting can make the trigger fire: there is nothing to fire on. The night light works precisely because DP 4 is one of the two that do arrive.
The likely cause is DP 6. alarm_propel_switch — “propel” as in push — is the switch that controls whether the unit reports alarms at all, and yours is false. With it off the chime rings physically but stays silent on the network. Worth noting: on another unit of the same family that reports ring events, DP 6 is true.
Please try this:
- In the Tuya / Smart Life app, enable notifications (or the alarm/push setting) for the chime — that is what sets DP 6.
- Press the doorbell button.
- Open the app settings → DP Debug tab, select the device, press Refresh.
- Tell me whether DP 10 or DP 5 now shows up in the table.
If either appears, we are done — the ring trigger just needs dp_doorbell pointed at whichever one moves, and I will tell you which.
I found this:
{
“devId”: null,
“uid”: null,
“t”: null,
“t_local”: null,
“cid”: null,
“updatedAt”: “13.8.2026, 19:34:25”,
“dps”: {
“4”: false,
“5”: “AFQA/AByAGsAbABpAG4AZwBlACAAMQ==”,
“6”: true,
“10”: 1
}
}
I’m talking about the Tuya Android app, not the Homey app ![]()
Yes you do get an email notification. I would do it again although I’d do everything I could to avoid getting Tuya products again ![]()
I have 5 ceiling fans with built-in lights from the brand Varin, across 2 different models.
When I add them as lights, they work perfectly as lights (without fan functionality).
When I also add them as fans, they start behaving strangely. For example, if I turn on the fan via the Homey app, the light turns on instead of the fan. How can I debug this?
P.S. Great app! I replaced the original cloud app with this one to avoid reliability issues.
Thanks ![]()
Could you please provide some logs and the device details from the app settings? Cloud DP Table and Local DP Table is required to check your issue.
Thanks
Thanks, can i get this from the Homey App or the Tuya Developer IOT site?
- Update the Tuya Local App to the latest test version Tuya Local | Homey
- check the Help page (under App settings of the Tuya Local App) to get the tuya IOT ready for you
- enter the credentials from the IOT site under “Cloud Lookup”
- send me the information
Afterwards you could as well try the new “Fix It” options
Hey Andi
I have installed the app and added a few lights; it works fine. Do I need to create a static IP address for the Tuya devices?









