Good morning, I have a problem with scene triggers.
I have two devices A and B and two automatic scenes A1 and B1.
Scene A1 turns off device A when certain conditions are met, and it works.
Scene B1 turns off device B if device A is turned off and other conditions are met.
Scene B1 doesn't work if device A is turned off by scene A1, but it works if device
A is turned off manually.
So, the off state of device A isn't recognized if it's turned off by the scene.
Is this a bug?
Scene B1 is triggered by a state change when device A turns off. When you manually turn off device A, the system registers a user-initiated state change, which triggers B1. But when scene A1 turns off device A, the system might:
- Not treat it as a “real” state change (especially if the device is already off or the command is redundant).
- Not propagate the change in a way that triggers other scenes.
- Delay or batch internal updates, so B1 doesn’t see the change in time.
So it’s not necessarily a bug. Use explicit triggers instead of state-based ones and instead of triggering B1 when device A is “off”, trigger it when scene A1 is executed. Use manual Tap to run scene. It works. I tested it this way.
In general, using such “layered” automations (scenes) in the eWeLink cloud is not the best idea. If you have an iHost, try using Node-RED or radically change your approach by switching to Home Assistant (e.g., on iHost), where building automations with multiple dependencies and conditions is possible to a relatively broad extent.