Hi Robin
Please check the latest TEST version Tuya Local | Homey
and
Send the DP Table from your device (under app settings / cloud …)
Thank you
here it is:
Pool Mini
DP 1 switch Boolean true {}
DP 2 temp_set Integer 34 0–40 step 1 °C
DP 3 temp_current value 34 -20–45 step 1 °C
DP 4 mode Enum Heat Heat, Cool, Auto
DP 13 temp_unit_convert Enum c c, f
DP 14 temp_set_f Integer 32 32–104 step 1 ℉
DP 15 temp_current_f value -4 -4–122 step 1 ℉
DP 21 fault bitmap 0 maxlen 30
DP 101 aux_manual Boolean false {}
Great news — the Cloud Lookup confirms your device does have a mode DP (DP 4) and also a current temperature sensor (DP 3) that we weren’t using before. I need to correct my earlier answer.
The reason mode switching doesn’t work: the enum values are capitalised — Heat, Cool, Auto — but the Mode Values setting likely has lowercase heat,cool,auto. The device rejects the unknown value and snaps back.
Fix: Go to your device → Settings → Mode Values → change to:
Heat,Cool,Auto
Also update your full configuration while you’re in Settings:
| Setting | Value |
|---|---|
| DP On/Off | 1 |
| DP Target Temperature | 2 |
| DP Current Temperature | 3 ← add this, was missing |
| DP Mode | 4 |
| DP Fault (0 = disabled) | 21 |
| Temperature Divisor | 1 |
| Min °C | 0 |
| Max °C | 40 |
| Step °C | 1 |
| Mode Values | Heat,Cool,Auto ← capitals |
DP 101 (aux_manual) can be left at 0 — there’s no matching Homey capability for it.
After saving, the current pool temperature should show on the device card, the fault alarm will work, and mode switching should respond correctly.
Done and it works! But if you set the mode to eg cool in homey and set it back to heat in SmartLife it does not synchronise the homey device anymore. Is that expected behaviour?
Hi Bruno
I’ve checked my access and it works so it looks like an issue with your configuration.
The API call succeeded (no auth error) but returned zero devices. Two most common causes:
1. Wrong Data Center (most likely) “Central Europe” only works if your Smart Life / Tuya Smart account was registered in the EU region. Many users — even in Europe — are on Western America? or India? depending on which region was selected when the mobile app account was created.
→ Try all data centers one by one
2. App account not linked to the project The IoT Platform project must be explicitly connected to your mobile app account:
- iot.tuya.com → Cloud → Project Management → open your project
- Tab Devices → Link Tuya App Account
- Scan the QR code with the Smart Life or Tuya Smart app
Only after that step will the devices show up in the project.
Hi Andi,
tried all of that but unfortunately it does not work. Some additional context:
when initially setting the heart pump via the homey device all functions well and vice versa. on/off, and temperature settings respond immediately all the time when set on the homey device or the smartlife device. They act seamless.
however when you set the auto, heat, cool setting on homey. All seems to work fine. However all three settings have their own stored temperature setting. When setting the device from homey to another mode, mode is set and the temperature changes. The mode is set from homey to smartlife, but the change of temperature happening automatically by changing the mode in the smarlife device is not synchronised back. When you then set the temp in the homey device it also changes in the smartlife device and the devices are synced again.
one note: the cool setting has its own temperature range which is different from the heat temperature range: something i think you cannot set in the homey device settings (2-30 degrees celcius). This makes that the temperature settings in the homey device for cooling do not fit the same settings in the smarlife device.
Lastly: when you set the mode setting from the smartlife app, the 2 devices get unsynchronised entirely. the mode is not set in the homey device and the tuya device becomes incontrolable from homey. Sometimes it works to set the mode back in smartlife to the same as in Homey. Sometimes i need to reset the tuya app entirely and the device gets synced.
Jacco
Hi Jacco
thanks for the detailed report.
Issue 1 (temperature not syncing after mode change) should be fixed in v1.0.103. Each mode stores its own temperature on the device, but after a mode switch the device doesn’t push the new temperature — it silently switches internally. The fix: whenever a mode change is received, the app now triggers a refresh 1.5 s later to fetch whatever temperature the device just switched to. That update then flows back into Homey automatically.
Issue 2 (cool mode range 2–30 °C) — go to the device settings and set temp_min = 2. This extends Homey’s temperature slider down to 2 °C so it covers the cooling range. The device still enforces its own limits internally.
Issue 3 (SmartLife mode change makes device uncontrollable) — this might be a firmware behavior on some Tuya devices: after a cloud command the device temporarily stops responding to LAN commands. There’s no reliable fix on our side. Best workaround is to use Homey as the primary controller and avoid switching modes from SmartLife. If it happens, use Force Reconnect from the device’s flow or settings — that’s faster than restarting the whole app.
1.0.103: Tuya Local | Homey
issue 1: fixed indeed!
issue 2: check! done
issue 3: seems better with your changes in the last update. only thin is: it now actively updates temperature after mode change, but it does not with the mode if set from smart life. it does however for the temperatures. So this probably is a solvable error.
Please update to 1.0.104 and let me know if issue 3 is resolved as well
I have two devices in the Tuya app: a light bulb and an outlet. Everything was done according to the instructions. I added it to Homey. The light bulb works without any problems. However, the outlet doesn’t display any errors, but it doesn’t physically respond to Homey commands. What could be the cause?
Tap Protocol Version → set to Auto-detect. The app will try 3.3 → 3.4 → 3.1 → 3.5 and lock in whichever one the device accepts.
Fault DP is -1 — should be 0
A value of -1 is not valid; it should be 0 to disable an unused DP. This probably doesn’t affect on/off, but fix it anyway.
Tap Fault DP → change -1 to 0.
After saving both changes, go to Apps → Tuya Local → Settings → Logs and look for the connection line — it will show which protocol version connected successfully. If it still doesn’t respond after auto-detect locks in, share the log output.
Yesterday I struggled a bit more, and as I wrote earlier, I added a light bulb and it works without any problems.
then I added the socket, used the search function, found the IP address of the device.
However, only after some time I realized that the device search option indicated the same IP as the light bulb, so it is quite possible that the socket does not work because it has an incorrect IP.
So I decided to check the socket’s IP and set it manually. Unfortunately, after entering the correct IP, there was a problem connecting and adding the device.
What’s the Brand and device name of the smart plug?
Are you able to ping the IP address of the Smart plug?
A8M is a Matter Device?
Yes
Nous Matter devices also work via Tuya. They use multiple protocols, just like how WiZ, Govee, Tapo and others can be added using both the official mobile app and Matter at the same time
