Tuya Smart automation problem: Scene only works with app and voltmeter on

Hello
Problem as follows.
Wifi smart plug socket, connected to home router,Tuya app on phone. The scene written: if the voltage higher than 245v and the socket off -> turn on the socket.
And that's it, after five minutes the timer turns off the socket measurement and so on over and over again.
The problem is that this automation works only when I have the application turned on and it is on the tab with the voltmeter just enough that I enter another tab or the application is running in the background automation stops working. Maybe someone of you has encountered a similar problem and has any ideas what could be the cause of this tragedy?

What socket is this exactly?

bolec310 wrote:

Scene written: if voltage higher than 245v and socket off -> turn socket on.

Insert screen of scene with voltage setting.

Photos of the socket and settings, everything works when I have that voltmeter on which is on the only one of the screenshots

There is no uninstalled software update for the socket?
Can you connect two sockets so that the first one measuring the voltage is always on and controls the second one? You can connect in series, for example, but you can also connect in parallel. It is important that the first socket is not switched off, which may set a "sleep state" on it.

No, the socket is original (this is the 2nd piece, I thought the first one was faulty) and the socket control I don't quite understand, anyway I only have one.

I have exactly the same problem, has it been solved somehow?

Check triggering after approx 30secs on zigbee, as for wifi it may be a longer delay.

when the voltage screen is not active, it will poll the status of the device less often (energy saving?),

I have the above scene working just with a delay.

I have a similar problem.
I have devices on the plot under Tuya control.

The Zigbee socket only reports voltage, power and amperage status when there is an active screen in the Tuya app (I have Smart Life specifically). Just change the view in the app to a different one and the socket stops reporting status. This prevents automation by state. I wanted to set the socket to switch off one minute after detecting electricity.
I have a Tuya WiFi socket set up like this and it works, while Zigbee doesn't want to.

I have a Home Assistant + Zigbee at home - not on the plot of land.
I plugged this socket into Zigbee under the control of the Home Assistant for a test and everything works OK, the socket reports states and you can do automation.

I just bought a second Zigbee Tuya gateway because I thought maybe the gateway was faulty, but I plugged this socket in and unfortunately the effect is the same.

I may buy another socket, just maybe I am just doing something wrong? Where do I look for the error??

Greetings, LP.

What are you using the scene for?

For momentary switching off the hydrophore on the plot.
Without going into a long story: the hydrophore stops drawing and switching it off for a few seconds after, for example, a minute of operation cures the situation - it starts sucking nicely.
I am going to have to rework the whole system, but to do it properly would be a bigger issue and for now the issue is taken care of by automating the socket.
I wrote: takes care of, because currently the hydrophore is connected to a wifi socket and here the automation works and the socket nicely reports the status of the sensors, but the wifi is capricious and once every few days, sometimes less frequently, you have to reset the socket because it loses the wifi.
Of course I can buy a repeater for the wifi and hope for an improvement, but I have Home Assistant & Zigbee at home (not on the plot where the hydro is) and various things work very stably, so I wanted to rewire the hydro to Zigbee and use the wifi socket for something else.
So I bought a Zigbee gateway to Tuya, bought a metered socket and thought I'd do the same automation as I did to the wifi socket.
Turns out there's a problem.
I really don't like to return purchased equipment if it's not faulty (supposedly I can because it's not 14 days yet) because it's a bit messy.

I would start by reducing the voltage value in the scene. You have it set at 235V, sometimes it is lower, as shown in picture 4.
.

Hello, I'm just going to link to the topic. I was also trying to do automation on a smart socket based but a different type of socket than above in the thread. The automation was supposed to be based on the socket reporting the power consumed by the device - e.g. that if it consumes more than a certain number of watts then the automation is supposed to run something else there. And I have the same - it doesn't work - sometimes only something "surprised" when I had the socket reading active on the mobile. I've tried various combinations of less than how many watts, more than how many watts etc. Anyone have any ideas why it doesn't work?

I read somewhere that in the case of Zigbee sockets the devices do not report on their own, but wait for a request from the app, because it is more energy efficient that way.
I still don't know what to do with this, I use a WiFi socket for automation, not Zigbee, but this is a worse solution because the WiFi socket once every few days requires a reset because it loses the network.

This is what it looks like, unfortunately.
I created the same automation with a socket instead of zigbee working over Wi-Fi and indeed in this case these rules/automations work.... at my place the Wi-Fi socket does not lose connection so basically it is ok.
Although as I'm building a network of zigbee-based devices in my home I would prefer these zigbee sockets to work as required....
Then I ordered two more sockets for Wi-Fi .

I am having an issue with my Zigbee devices. I created an automation for a Zigbee plug to turn off the charger once the power consumption drops. However, the scene does not trigger—when the charging finishes and the wattage drops to 0, the plug stays on.

Interestingly, even scheduled tasks don't always work reliably through the app's scenes, so I have to set schedules directly within the device settings instead.

Everything works perfectly with my Wi-Fi plugs, but the automations simply fail to trigger with my Zigbee devices, even though the app shows the power consumption has reached 0W