Why Your eWeLink Scene Didn’t Run—and How to Fix It

Table of Contents

You set up a scene, but when the expected time or device event came, nothing happened.

In most cases, the problem comes down to the device connection, the trigger or conditions, the effective period, or another automation affecting the result.

Here are the most common causes and what to check.

eWeLink Scene

Cause #1: A Device or Hub Is Offline

A scene depends on the devices involved being available when they are needed.

If a trigger device is offline, it may not be able to report the status change needed to trigger the scene. If an action device is offline, the scene may run but the device may not be able to carry out the action.

For Zigbee or other hub-connected devices, check the hub or gateway as well. If the hub is offline, its connected devices may not be able to report status changes or respond to commands.

What to check

Open the eWeLink app and make sure the devices involved in the scene are online.

Try controlling the action device manually from the app. If manual control also fails, check the device connection first.

If a device is offline or keeps going offline:

  • Make sure it has power or enough battery.
  • Make sure the router or hub is online and the device has a reliable connection.
  • Restart the device or hub if needed.

Cause #2: The Trigger and Effective Period Didn't Line Up

If your devices are online and the scene settings look correct, but the scene still doesn’t run, check the scene’s effective period.

An effective period defines when a scene can respond to trigger events. It does not trigger the scene by itself.

If the trigger condition was already true before the Effective Period started, the scene will not run automatically when the Effective Period begins. The device needs to report a new qualifying change after the effective period starts.

For example:

If: Temperature is above 30°C
Then: Turn on the fan.
Effective Period: 10:00 AM–1:00 PM

If you save the scene at 10:30 AM

The temperature is already 31°C.

Because the scene is saved within its effective period and the condition is already met, the scene will run immediately after you save it.

If you save the scene at 9:59 AM

The temperature is already 31°C, but the effective period has not started yet.

When the effective period begins at 10:00 AM, the scene will not automatically run just because the temperature is still 31°C. Starting an effective period does not re-check an already existing device state.

The scene waits for a new qualifying device update during the effective period.

The same principle applies to other device-based triggers. For example, leaving a door open does not continuously trigger a scene configured for “Door opens.” A new device event is needed.

What to check
  • Is the event within the configured effective period?
  • Check the corresponding device logs, when available, to confirm that the expected event or status change was reported.

If you want the scene to run at a specific time, such as exactly 10:00 AM, use Time of Day as the trigger. An effective period only defines when a scene is allowed to run; it does not trigger the scene at a specific time.

Cause #3: The Time Zone Doesn't Match Your Location

If a time-based scene runs earlier or later than expected, the time zone selected in eWeLink may not match your current location.

This can affect Time of Day triggers and Effective Periods, causing scenes to run at a different local time than expected.

What to check

Go to Profile > Settings > Time Zone in the eWeLink app and make sure the selected time zone matches your current location, especially if you recently moved or changed regions.

Cause #4: Not All Required Conditions Were Met

A scene can contain multiple conditions using All or Any logic.

With All, every required condition must be satisfied for the scene to run.

With Any, the scene can run when any one of the configured conditions is met.

For example:

If All:

  • Motion is detected
  • The light is OFF

Then: Turn the light ON.

If motion is detected while the light is already ON, the scene will not run because the Light is OFF condition is not satisfied.

What to check
  • Check every condition in the scene, not just the one you expect to initiate it.
  • Make sure All or Any is configured as intended.
  • Check the relevant device states and time-related conditions when the scene is expected to run.

Cause #5: The Scene Is Disabled

A disabled auto scene will not run, even if its conditions are met.

Open the Scene in the eWeLink App and make sure the auto scene is enabled.

Also check whether another scene is configured to enable or disable it. If so, make sure that scene has not disabled the auto scene you are troubleshooting.

Cause #6: Another Automation Is Affecting the Same Device

More than one automation may be controlling the same device.

For example:

Scene A: At 10:00 PM → Turn the living room light OFF.
Scene B: At 10:00 PM → Turn the living room light ON.

If different scenes, schedules, timers, or third-party automations send different commands to the same device around the same time, the final device state may not match what you expected.

What to check

Review any other automations that control the same device, including:

  • Other eWeLink scenes
  • Device schedules and timers
  • Automations on third-party smart home platforms

Pay particular attention to automations that control the same device at similar times.

Cause #7: Scene-Generated Device Changes Don't Start Another Scene

To prevent automation loops, eWeLink does not treat a device state change caused by a scene action as a new trigger for another scene.

For example:

Scene 1

If: Light A turns ON
Then: Turn Light B OFF.

Scene 2

If: Light B turns OFF
Then: Turn Light C ON.

When Light A turns on, Scene 1 turns Light B off. However, because Light B was turned off by a scene action, that change will not trigger Scene 2.

As a result, Light C will not turn on.

How to set it up instead

If you want several actions to happen from the same trigger, add them to the same scene:

If: Light A turns ON
Then:

  • Turn Light B OFF
  • Turn Light C ON

Cause #8: The Scene or Device Configuration Has Changed

If a scene used to work but recently stopped, check whether anything in its setup has changed.

Open the scene and verify that the following settings are still configured correctly:

  • Trigger devices
  • Conditions
  • Actions

This is especially important if a device was removed and added again, replaced with another one, or the scene settings were changed after the scene was created.

Also make sure you are using the latest available version of the eWeLink app and check whether firmware updates are available for the devices involved.

Check Scene Logs and Device Logs

Logs can help you narrow down what happened.

Scene Logs

Use scene logs to check whether the scene execution was recorded as successful or failed.

If the scene shows as failed, check the devices involved, their connection status, and the scene configuration.

If the Scene Log shows a successful execution but the device is later in a different state, check the Device Logs and other automations that may have controlled the device afterward.

Device Logs

Use the corresponding device logs, when available, to check device events and status changes.

For example, if a motion-triggered scene did not run, check the motion sensor’s Device Logs to see whether the expected motion event was reported.

Together, scene logs and device logs can help you determine whether the issue is related to the device event, scene execution, or another automation changing the device afterward.

Quick Troubleshooting Checklist

When a scene doesn’t run as expected, check:

  • Devices: Are the trigger and action devices online? Can you control the action device manually?
  • Trigger: Did the expected device event or status update occur? Check the device logs when available.
  • Conditions: Are all required conditions met, and is All or Any configured correctly?
  • Effective Period: Did the trigger happen within the configured effective period?
  • Time zone: If the scene runs at the wrong time, check Profile > Settings > Time Zone.
  • Scene status: Is the auto scene enabled?
  • Other automations: Could another scene, schedule, timer, or third-party automation be changing the same device?
  • Scene chaining: Remember that device changes caused by a scene action do not trigger another scene.
  • Logs: Check the Scene Logs for the execution result and the Device Logs for relevant device events.

Still Not Working?

If the devices are online, manually controllable, and the scene settings appear correct, try deleting and recreating the scene.

If the issue continues, submit feedback through the eWeLink App and provide as much relevant information as possible, including:

  • Screenshots of the scene settings
  • Approximate time when the issue occurred
  • Relevant Scene Logs and Device Logs
  • Device IDs
  • eWeLink App version
  • Device firmware versions

These details can help narrow down whether the issue is related to the device event, scene configuration, scene execution, or device response.

What important features are we missing? We’d love to hear from you! Join our discussion here. 

Share the Post:
Related Posts

This website use cookies to ensure you get the best experience on our website.

ACCEPT & CLOSE
DECLINE