Automation not triggering subsequent automation

Automation not triggering subsequent automation

Automation not triggering subsequent automation
Automation not triggering subsequent automation
2025-06-09 05:09:38 - last edited 2025-07-14 11:08:19
Model: Tapo P100  
Hardware Version: V2
Firmware Version: 1.2.5

Hello, I have an automation (for clarity below, lets call it "Smart-Plug-Trig") which is triggered by the T100 smart plug changing status (either On or Off). This works fine if the plug is manually switched on or off physically or through the Tapo App, and also when turned on or off via a Tapo App shortcut.

 

However when the smart plug is turned on or off via another automation the "Smart-Plug-Trig" automation does not trigger.

 

Can you please confirm if this is a Bug which can be resolved in the automation software or a deliberate feature as it is impacting some automations which I am building - refer below for use case.

 

Use case for background only:  You may think this is easy to work around, by having the original automation just trigger the "Smart-Plug-Trig" automation. However the reason I am doing this is to transfer state from one Tapo user to another. I.e. when my wife leaves home, the shared smart plug turns off which then should trigger an automation on my Tapo account to turn off privacy mode, if I am also away from home. This gets around the constraints of not being able to share automations across accounts and the inability of a shared camera being able to be put into/out of privacy mode. However if I use a Geofencing automation (on my wifes device) to start the process then the subsequent automation on my account will not trigger.

 

Note that the automation successfully triggers on my phone if my wife turns on/off the shared smart plug directly in the app on her device or via shortcut in the app.

 

Important to note the triggering also does not work if the above is all done on a single account. I.e. it is not related to an automation executing from one account triggering an automation on another account.

  0      
  0      
#1
Options
1 Accepted Solution
Re:Automation not triggering subsequent automation-Solution
2025-06-10 03:01:58 - last edited 2025-07-14 11:08:19

  @Rbuck 

 

That's the feature design, loop triggering is not supported -- device state changes made by smart action will not be considered as automation triggers.

Tapo P110M Matter 1.3 Release Energy Monitoring through Matter ▶ Smart HomeBase Tapo H500 - Even More Powerful Smart Hub ▶ First Smart Switch Module! Tapo S112 Smart Switch Module with Roller and Switch Dual ModesTapo Camera Image Style & Image Brightness Try out a different image style for your camera!
Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:Automation not triggering subsequent automation-Solution
2025-06-10 03:01:58 - last edited 2025-07-14 11:08:19

  @Rbuck 

 

That's the feature design, loop triggering is not supported -- device state changes made by smart action will not be considered as automation triggers.

Tapo P110M Matter 1.3 Release Energy Monitoring through Matter ▶ Smart HomeBase Tapo H500 - Even More Powerful Smart Hub ▶ First Smart Switch Module! Tapo S112 Smart Switch Module with Roller and Switch Dual ModesTapo Camera Image Style & Image Brightness Try out a different image style for your camera!
Recommended Solution
  0  
  0  
#2
Options
Re:Automation not triggering subsequent automation
2025-06-10 03:58:01

Thanks  @Wayne-TP , after sending this, I thought that that the reason this is blocked is that it could create recursive/infinite loops, so makes sense... I'll find another way :-)

  0  
  0  
#3
Options