Have you got any ETA for official release? Will it solve my current problems between Kasa and Tapo automations and smart actions? In Kasa app I have geofencing routines with KE100. I can see this action in Tapo app, but it is invalid (probably invalid trigger or unsupported device).

Hi,

Could you please confirm why the beta functionalities have taken away?

I'm unable to manage the automations that I had created before the beta as well as during the beta.

I've just seen in this post that I have lost access to all my automations because I was in the beta version.

Why we haven't been advised the date when the beta was being removed? 

I have now automations that I need to delete or manage and I can't do any of my 12 automations. 

Normally, a beta version is not discontinued but developed further and becomes a release version after successful testing. Were there any serious problems with this one?

More than one week and still not a word. No explanation or a solution for the beta testers.

@Solla-topee @Wayne-TP someone, please say something. 

Hi Konrad44,

perhaps i have a workaround for you.

This one works for my home.

I have ten KE100 wich i want to use only via tapo app.

with the newest update it works, but the automations wont work anymore.

So i downgraded to the beta app an disabled automatic update in playstore since a solution is found.

In the beta app i tried much, but here is how it works.

I have got a picture for you, the text is in german.

I will translate and explain it for you.

You have to do your actions twice. The original action is done in the Kasa app. Here are your actions defined.

For me, i have the temperatures for every thermostaic valve set (4).

The apps are synced together, but you are not able to use the Kasa actions (2) in Tapo app directly.

It says the devices are not present.

However, you can create an action (1) in wich you start the Kasa action (2) within the Tapo app.

I think the arguments will be given to the Kasa app and then it starts.

You can check the correct functionality in Kasa app.

Sometimes you have to tap the action twice, because you get some errors from Tapo app.

But for me it works.

And you can open the Tapo action (1) in your automatios as well.

Hi @PeterKarch ,

Thanks for your recomendation and workaround. It is a very good idea for the temperature sensor (included among the Kasa app devices).

However, this procedure is not valid for my T100 motion sensor, since it is not included in Kasa, it can only be managed from Tapo.

Regards.

I was looking for a solution to the same problem, i've jsute discovered that i can't modify my automation created in the beta ! that's a very strange way to thanks beta tester.
That's the fist time i see a beta discontinued like this, i hope final version will be available very soon

Hey djinet,

what do you want to do with your motion sensors?

Perhaps is it possible to get them work via the workaround too.

And i'm with you, this is not a solution!

I am an it-technician but for tp-link only a user!

I like these products, goog price and good quality.

I think they made a mistake in update policy.

The downgrade to version 3.2.204 beta works very well.

I hope there will be a solution soon...

Looking forward!

Regards

Hi @PeterKarch 

What I would like to achieve is that when my T100 sensor detects movement, the recording action of my C420 cameras will be triggered.

I already know that the cameras have a motion detector, but since I have them about 12 meters high, the T100 detector works better. I have done the appropriate tests and the T100 scope works much better, but the automations do not allow a recording action.

Regards