Scenes does not enabled or disabled from a manual scene or from auto scene

Hi. This is a major bug. Please fix it.

One simple example to demonstrate the bug is this.

Lets say that motion sensor SNZB-03 with the name “Motion 1 pc” is in “No motion detected” state and you set manual a Socket in ON state. All connected with hub Sonoff ZB Bridge-P.

Lets make one auto scene with name “Test”:

Motion 1 pc
No motion detected

Socket OFF
Delay 10 sec
Socket ON
Push notification

Lets make one manual scene with the name “Enable Test”

Tap to perform

Test enable

Lets make one manual scene with the name “Disable Test”

Tap to perform

Test disable

When you save the scene Test or enabled manual (toggle switch on screen), it reads the state of the sensor, Socket goes OFF, after 10 sec goes ON and receive the notification. Everything working just fine!

If you run the manual scene “Enable Test” the scene Test didn’t enabled at all. Problem!

If you disable manual the scene (toggle switch on screen), in 8 sec the scene stops and the socket remains OFF. The Delay stops and the Socket ON does not executed and you don’t receive notification. Everything working just fine!

If you run the manual scene “Disable Test” in 8 sec the Delay still counter and the Socket ON will executed and you receive notification. So the scene Test didn’t disabled at all. Problem!

Same problem if you make a auto scene that disable Test in 8 sec.

Please fix this.
The auto or manual control of the scenes is a very powerful tool and now is useless.

Hi there, could you please attach the screenshot of the scene log about this test?

Hello. Here the scenes log. All manual scenes are successful but they don’t work. They do not enable or disable the “Test” scene.
You can try it.

Auto scene “Test”:

Manual scene “Enable Test”:

Manual scene “Disable Test”:

In my experience an already running scene can not be disabled during that execution. The already running scene will finish the execution first. In some cases it might be usefull to have the already running scene aborted and in other case you don’t want to let that happen.

You say: “The already running scene will finish the execution first.”

No it does not finish the execution, if you manual disable it (meaning with your finger touching the slide icon.)

What the point of command “Enable/Disable auto scenes” if the command do NOT work?

For example, in my house if the front door is opened and stay opened, i want the light of the front door to remain on.

If the door closed, i want the light to close after 5 mins.

This simple task its impossible to make it happened, because if i close the door for 4 min and opened again the light will go off after 1 min. Problem because i want the light to go off after 5 min from the last time i closed the door.

Am i wrong?

Can you make one scene that works the way that i want?

This is the disadvantage of scenes. You need a more intelligent system. For example a variable that counts the amount of time between open and close and then decide on base of the value whether the light should stay on. Such intelligent automation can only be achieved with third-party software like Home Assistant and Node-RED.

The features I’m asking for already exist in the app.
The problem is that they don’t work properly.

When you enable or disable a scene manually, the process works correctly.
But when the same activation or deactivation is done through the command “Enable/Disable auto scenes” then a problem arises and must be corrected.
This is a bug and needs to be fixed.