FAQ
TL;DR: Zigbee scenes often trigger only when the Tuya/Smart Life device screen is open; background polling is ≈30 seconds—"it will poll the status... less often." Use Wi‑Fi or local Zigbee, adjust thresholds, or a two‑plug workaround. [Elektroda, 12robert12, post #20613633]
Why it matters: This FAQ helps Tuya/Smart Life users fix or work around voltage/power-triggered scenes that don’t fire reliably.
Quick Facts
- Typical Zigbee background polling ≈30 seconds; Wi‑Fi may delay longer, so scenes can lag or miss triggers. [Elektroda, 12robert12, post #20613633]
- Some Tuya/Smart Life Zigbee plugs only update volts/amps/watts while their device page is active. [Elektroda, ciarek999, post #20634608]
- The same Zigbee plug reports continuously and automations work when paired to Home Assistant locally. [Elektroda, ciarek999, post #20634608]
- Several users found identical scenes reliable on Wi‑Fi plugs after switching from Zigbee. [Elektroda, pigwoz, post #20658005]
- Keep the metering plug always on; switching it off can push it into a sleep state—use a second controlled plug. [Elektroda, freebsd, post #20480284]
Why do my Tuya/Smart Life scenes only work when the voltmeter screen is open?
Because the app polls the sensor faster only when that screen is active. In background, polling slows and triggers get missed. One member noted, "when the voltage screen is not active, it will poll the status... less often." Expect ≈30 seconds delay on Zigbee, and longer on Wi‑Fi. That explains why switching tabs breaks your scene. [Elektroda, 12robert12, post #20613633]
Does Zigbee report energy data continuously on Tuya gateways?
Not consistently. Users observed Zigbee plugs reporting volts, power, and current only while their device page is open. Leaving that screen stops updates, so state-based automations don’t run. The same plug reported continuously and allowed automation when paired to Home Assistant locally. That points to Tuya hub/cloud behavior. [Elektroda, ciarek999, post #20634608]
Why does my automation stop after about 5 minutes?
The original report says “after five minutes the timer turns off the socket measurement,” and the loop repeats. That suggests a metering timeout or sleep when the plug is power-cycled or the app idles. Scenes depending on live metering then fail until you reopen the device page. Keep the metering device on and avoid switching it off in the same scene. [Elektroda, bolec310, post #20479392]
Will lowering the voltage threshold help my scene trigger?
Yes, a high threshold can prevent triggers. One member advised reducing the setpoint because observed voltage dipped below the configured value. Lower the threshold to match your actual line voltage and add some margin. This small change is often enough for the scene to fire. [Elektroda, emariusz, post #20640037]
Is this a device fault or a Tuya platform limitation?
Evidence points to platform behavior. A user tried a second Tuya Zigbee gateway and saw the same issue. The same plug worked flawlessly when paired to Home Assistant using local Zigbee. That combination indicates the Tuya hub/cloud path is the bottleneck. [Elektroda, ciarek999, post #20634608]
What delay should I expect before a Zigbee or Wi‑Fi scene fires?
On Zigbee, expect roughly a 30‑second trigger delay when the device page isn’t open. Wi‑Fi can be slower. This reflects how often the platform polls devices in the background. Plan your automations with this delay in mind, especially for voltage/power triggers. [Elektroda, 12robert12, post #20613633]
How can I make it work today without changing platforms?
Try the two‑plug method and avoid metering sleep. “It is important that the first socket is not switched off.” How‑To: 1) Keep one metering plug always on. 2) Create a scene: if its voltage/power crosses threshold, switch a second plug/relay. 3) Never power‑cycle the metering plug. Also check for any pending firmware updates in the app. [Elektroda, freebsd, post #20480284]
Will using a Wi‑Fi plug instead of Zigbee solve it?
For several users, yes. They recreated the same rules on a Tuya/Smart Life Wi‑Fi plug and automations ran reliably. One user, building a Zigbee network, still ordered two more Wi‑Fi plugs after this success. Consider Wi‑Fi for critical power/voltage triggers if coverage is solid. [Elektroda, pigwoz, post #20658005]
My Wi‑Fi plug drops connection every few days; what can I do?
One user reported needing a reset once every few days due to Wi‑Fi loss. Improve signal with a nearby Wi‑Fi repeater or access point. Better coverage often stabilizes links to outbuildings or distant sockets. If resets persist, consider a local Zigbee coordinator instead of cloud paths. [Elektroda, ciarek999, post #20636023]
Why do power (W) based automations fail too?
They rely on the same telemetry as voltage and current. If the device page isn’t open, the plug often stops reporting power. Scenes don’t see changes and never trigger. Users observed these rules only “catch” when the socket reading is active on the phone. [Elektroda, pigwoz, post #20656405]
Does changing the Tuya Zigbee gateway help?
A user replaced the Tuya Zigbee gateway and saw identical behavior. That rules out a single faulty hub and suggests a broader platform trait. If you need prompt telemetry, consider moving the device to a local Zigbee coordinator. [Elektroda, ciarek999, post #20634608]
Can Home Assistant with a Zigbee coordinator make these automations reliable?
Yes. The same Tuya Zigbee plug reported states continuously and allowed reliable automations under Home Assistant. Pair the plug directly to a local Zigbee coordinator. This avoids cloud polling delays and restores timely triggers for voltage/power scenes. [Elektroda, ciarek999, post #20634608]
.
