In the smart button settings when I go into the smart action for turning off the lights it is greyed out stating "invalid triggers"  when I click into the smart action it then states "double tap feature not enabled" but when I look at the device settings for the button the double tap is definitely showing as on.  If I then go into the double tap setting and change it to "off " then immediately turn it back on again - then navigate back to the smart action it all looks correct again.

 

It appears the smart action keeps thinking that double tap is off when in fact it is on.

 

Please can you fix this bug?

Definitely a bug here - just re-done a smart action and even when the double tap is enabled in the button's device settings, the smart action that uses the double tap as a trigger shows as greyed out and obviously thinks double tap is off and displays "invalid triggers" and "double tap feature not enabled".  When I physically test the double tap on the button it does actually work however it appears this bug then creates a conflict with the other smart action that uses the motion sensor as a trigger to turn off the same devices.  This prevents the motion sensor from being able to turn off the devices.

 

Not sure why there needs to be any link whatsoever between a motion sensor trigger and the button?  Surely they should operate independently of each other anyway?

 

For context this is a relatively simple objective whereby some lamps plugged into P100 smart plugs are turned on and off via a smart button and I have simply added a motion sensor that turns them off if no motion sensed after midnight for a period of 15 mins (so if I leave the lights on and go to bed they don't stay on all night).

 

I see no logical reason why this basic smart programming will not work reliably.  Seems to work sometimes but not always.  Please help.

I see this exact same issue has been raised previously about a year ago...

 

Tapo S200B double tap feature does not stick - Smart Home Community

 

Very disappointing that you have not resolved this yet.  If I can't get this to work properly (ie as advertised prior to purchase) I will need to return quite a few hardware items!

 

And to top it off the link to your recommended solution in that earlier thread doesn't even work!  Here...

 

TP-Link

 

 

  @Wayne-TP I've done a bit more testing and reading of your previous replies to similar threads and I believe the display issue in the app regarding the double tap setting may have clouded the issue I'm having.  I think I have reproduced the issue I have but it is probably not related to the double tap display bug.

 

I think my issue is this...

 

If devices (P100 plugs in my case) are turned ON by a smart button single tap action they are not subsequently turned OFF by the PIR related smart action.

 

If the P100 devices are turned on by the PIR smart action they can be subsequently turned off by the smart button action but if the P100s are turned on by the smart button they cannot be turned off by the PIR smart action.

 

Logically my smart action with the trigger of no motion detected for 15 mins should still turn the P100 off even though it was turned on by the smart button and not the PIR but it does not.

 

Hope this makes sense.  Not logical so definitely a bug worth fixing I hope.

  @Wayne-TP let me try and clarify the issue via a question...

 

Does the automation in the app 'see' the actual status of the device in real time (ie whether a P100 is switched on or off at any given time) or does it simply assume the status remains at whatever previous status that automation last changed it to?

 

My issue is that I have created an automation to turn off my lamps when no movement is detected for a period of 15 mins.  I also have an automation that turns the same lamps on when movement is detected.  A smart button is also occasionally used to turn these lamps on.  The PIR automation to turn the lamps off works perfectly UNLESS the lamps were turned on by the smart button in which case it does not trigger (as if it thinks the lamps are not on in the first place).

 

I'm pretty sure my logic is not in conflict at all between the separate automations but something is preventing the PIR no motion to trigger the off command unless the PIR motion automation was the trigger that turned it on (as opposed to the smart button).  Surely it should not matter which other automation turned a P100 on - ionce that has happened it is history and if the device is on when a different automation is triggered to turn it off it should simply work.get to

 

Hope this makes sense.  I'll keep testing to try and get to the root cause but it's quite confusing.

 

 

I'm also exploring other available functions in the app to achieve the same outcome such as using the PIR to only trigger lamps on for a fixed time period of 15mins instead of using a trigger to turn them off.