Scenes sometimes does not work

Ideas & Suggestion
1

I can see sometimes scenes does not work as should be:

Today, for example Act. INTERIOR ACE ( a virtual switch) was OFF but scene RAN

1
11378×204 13.8 KB

And this scene does not work. This scene turns ON between 0:00 and 1:00. Luz escalera is a SONOFF S60 and is ON. Mov Planta2 Botón 1 is a PIR sensor that goes to RF BRIDGE. This scene is for turning OFF lights after 0.00 hours but when PIR triggered scane does not RUN. Wireless is fine

2
21411×225 16.7 KB

Anyone has experimented scene execution sometimes not accurate?

2

Going deeper in this question, i asked CHAT GPT what could go wrong with this question and CHAT GPT say something like if i buld a scen with

S60 ON

mov sensor (via RF bridge) ALL CONDITIONS MET

EWELINK fails because the sensor is like a “flash” and wuen cloud verifies if both parameters are ON, RF even PASSED… ¿This is a joke?

I put chat gpt opinion, but I can not believe it. If i make a scene with a S60 On state AND water sensor goes ON, I can not understand scene does not work. water sensor LOG is registered in RF bridge. I put this and I wait for an answer, because I only want ONE THING: REAL SCENE WORKING. Nothing else

eWeLink RF Logic Needs to Be Redesigned

After deep testing, it’s clear that eWeLink handles RF devices incorrectly in Scenes, especially when using All conditions are met.

:one: RF devices only send events, but eWeLink treats “ALL” as state logic

RF 433 MHz devices (like PIR sensors on RF Bridge) do not maintain a state.
They send a momentary event (a pulse) when triggered.

That is totally fine.

The problem is how eWeLink processes that event:

  • The RF Bridge receives the event correctly

  • The cloud logs it correctly (we see it in the event log every time)

  • But when a Scene with ALL CONDITIONS is evaluated, eWeLink does this:

:one: “RF event received”
:two: Immediately checks the other conditions
:three: :cross_mark: The RF trigger is NOT kept as a valid condition -----PLEASE CONFIRM THIS. IF THIS IS TRUE EWELINK IS A SIMPLE TOY FOR CHILDREN-
:four: Therefore the evaluation fails → Scene does not run

So even though the RF event just happened, the system does not consider it as an active condition.
This is a logic flaw.

:two: Evidence

Scenes where RF sensors are used with:
ANY condition is met
→ Work 100% reliably
Because RF is treated as a trigger only.

Scenes where RF is combined with another condition using:
ALL conditions are met
→ Fail randomly
Because the RF condition is not retained as a valid state.

But technically, at the moment an RF event arrives, both conditions ARE true, and the Scene should run.
The system should not ignore the event that just arrived.

:three: Logs prove the cloud receives RF correctly

The RF event appears every time in the device history.
So the cloud knows it happened.
The issue is purely in the Scene engine logic, which:

  • records events :check_mark:

  • but does not treat them as valid conditions :cross_mark:

This is inconsistent.

:four: Expected behavior

When an RF event arrives and triggers Scene evaluation,
the Scene engine should:

:backhand_index_pointing_right: treat the RF trigger as valid during that evaluation window
:backhand_index_pointing_right: combine it with the other conditions
:backhand_index_pointing_right: execute if all are satisfied

This is how every serious automation platform works (Home Assistant, Node-RED, Zigbee systems, etc.).

:five: Conclusion

This is not user misunderstanding.
It is a design limitation in eWeLink’s RF scene handling.

eWeLink should redesign RF logic so that:

  • RF events can be safely used with ALL CONDITIONS

  • RF triggers remain valid during evaluation

  • Scene behavior becomes deterministic and reliable

Right now RF + ALL conditions = unreliable automation.