Automations conditioned to device status (on/off)

I have an issue when programing automations that are conditioned to device status.
Specificaly, Im using an smart plug EU and I programed an automation with the following logic:

WHEN “event”
IF plug “is off”
THEN do “action X”

When the event is triggered, the IF condition is not evaluated and the action X is always performed (even if the plug was on)

I have tried with my two different smart plugs and with different very simple
automations, and same result.

Does this happen to other users? Any thoughts on the cause?

1 Like

any thoughts about the issue described above @AqaraBot ?

@Guybrush It sounds like you’re encountering an issue where the automation condition isn’t being properly evaluated—frustrating indeed! Let’s troubleshoot this step by step based on common automation-related checks for Aqara Smart Plug EU devices.

First, double-check the automation settings in the Aqara Home app. Sometimes mismatches or overlooked configurations (like incorrect condition logic) can cause the system to bypass condition evaluation. For example, ensure the “IF plug ‘is off’” condition is clearly selected and saved without accidental edits .

Next, confirm that both your smart plugs and Aqara Hub have the latest firmware updates. Outdated firmware can occasionally lead to communication gaps between devices and the automation system, which might prevent condition checks from working as expected .

It’s also worth verifying that the smart plugs themselves are functioning properly and their status (on/off) is accurately reflected in the app. If the plug’s status isn’t updating correctly, the automation won’t have reliable data to evaluate the condition .

Have you tried re-creating the automation from scratch to rule out any temporary glitches in the setup? Sometimes starting fresh helps ensure all parameters are correctly applied. Let us know if you’ve already checked these steps or if there’s more detail about your automation setup—other users might have encountered similar scenarios and can chime in

1 Like

Checked all of your suggestions but the problem persists

I also checked that the status of the plugs is correctly shown in the app.

The following picture shows the automation. (Im sure the problem is not in the WHEN clause, because I have tested the automation with the preview button)

@Guybrush It sounds like a tricky issue with automation condition evaluation—definitely frustrating when the logic doesn’t behave as expected! Let’s dive into this. First, to confirm: the Aqara Smart Plug EU does support “Is off” as a valid automation condition , so your setup logic should work in theory.

Since you’ve already checked device status accuracy in the app and tried multiple plugs, let’s explore a few deeper troubleshooting angles based on common automation hiccups :

  • Activation Time Check: Ensure the automation’s “activation time” settings (if any) align with when you expect the condition to trigger. Sometimes a misconfigured time range can cause conditions to be bypassed .
  • Hub & App Refresh: Even if other devices seem fine, try restarting your Aqara Hub and force-closing/reopening the Aqara Home app. Temporary communication gaps between the hub and app can occasionally disrupt condition evaluation .
  • Automation Re-creation: You mentioned simple automations, but it’s worth deleting and re-building one from scratch—ensuring each step (event, condition, action) is saved before moving to the next. Small setup glitches during creation can lead to unexpected behavior .

Have other EU plug users encountered this specific condition-evaluation quirk? It’d help to hear if this is isolated or more widespread! If these steps still don’t resolve it, reaching out to support might be the next best move—they can dig into logs or firmware specifics.

Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:


This will be more efficient. If you do not have an Aqara Home account, “Please click here” to create a ticket.