@Runner61627 

Interesting! Can you tell me how you contacted Amazon to get a ticket? I've just been using the forum but I don't think they're that interested in taking the informations seriously there. Maybe if I do whatever you're doing they'll actually try to be helpful.

  @Tyraelos 

go to "Help" in the Alexa app. Go to "Contact Us". Click on "speak with a representative". Put your phone number in and they will call you back immediately. 

You'll get a first line customer service person who will run down their rudimentary checklist. I would tell that person all the troubleshooting you have done. Tell them the problem started immediately after downloading the Alexa app update (version 2026.2). Insist that the problem be escalated to the technical team/engineers. Insist on getting a trouble ticket number. 
I had to call them three separate times to get the problem escalated to a trouble ticket. Be insistent, let them know you are tech savvy and this is a known problem. 
Good luck

  @Runner61627 

Thanks. I'll give it another week and if I hear nothing from/through Tapo Support I'll send something directly to the Amazon/Alexa team. 

  @Tyraelos 

I called Amazon/Alexa today, looking for status on the Alexa routine problem with Tapo "Person" detection not triggering Alexa routines. To my surprise, the customer service agent stated the update in their system says the problem was resolved with Alexa app update 2026.3 

I had already downloaded the latest version of Alexa app update (2026.3) a couple of days ago. 
It still doesn't work, so they reopened the trouble ticket. I once again provided a detailed description of the problem.
My advise for you is to contact Amazon/Alexa right away and start a trouble ticket so they realize the problem isn't just limited to one individual. 
 

  @Tyraelos 

Appears Amazon/Alexa is not fixing the problem with their App update 2026.2 

With Tapo "PERSON" detection not triggering Alexa routines, and "MOTION" detection causing too many false alarms (I live in a rural area with lots of animals), I went with IFTTT. I've got back the Tapo PERSON detection triggering of Alexa routines.

To do this, I created accounts with IFTTT and also  Voice Monkey. Took a little bit for me to understand how to get the triggers designed, but after learning how to set it up and using them to initiate my existing Alexa routines, I'm back to full functionality of my Tapo Camera/s PERSON detection triggering Alexa routines. 
Winning! 

  @Runner61627 
I called Amazon and we did no less than about 45m of troubleshooting. She even removed Alexa+ from my account to test but alas, Alexa+ isn't the issue. 
She told me she saw no reports of an issue with Tapo so I don't know if Tapo is lying to me about having contacted Amazon/Alexa, not sure what's up there. Then again, she should have seen yours as well so...not sure. Maybe she's just not searching for the proper terminology to pull it up.

Anyway, to summarize the session:

We deleted and recreated the routine - issue still occurs.
She disabled Alexa+ (for routines) on her end - issue still occurs.
We deleted and recreated the routine - issue still occurs.
We set the device/camera to "person detection announce enable" - this fixed the issue. I had known about this before but it causes echo devices to announce and even if you turn announce off in the setting, it will sometimes force at least one of them to announce, which is almost worse for me.

In the end, she escalated and says she'll call back if/when she hears back.

I used to use IFTTT years ago when it was free. Now I think they charge for more than 2 applets. If I get desperate I may go there. I did set up a Home Assistant server on a Mini PC. I'd halted further usage because:

1. I'm lazy and it's more work than it was worth for me, since it's MAINLY for people who want to not have cloud hosted Smart home stuff, which I didn't care about.
2. It's ugly if not set up properly and this requires a bit of code but again, lazy, lol. 

But if Amazon can't get their stuff together soon, I may use it to automate these connections instead.