These devices don't have plugin, so you have to use IFTTT and Join together. Works reliably. My config has a task for each state, and I have 5 in use (one operates a garage door). They can also be operated via Alexa, google assistant, and cortana.
Make a POST or GET web request to:
https://maker.ifttt.com/trigger/{event}/with/key/bqL
With an optional JSON body of:
{ "value1" : "", "value2" : "", "value3" : "" }
The data is completely optional, and you can also pass value1, value2, and value3 as query parameters or form variables. This content will be passed on to the Action in your Recipe
Yep...I recall Joao advising me that it was the IFTTT-eWeLink communication issue. They work together to control the light, but the web request (at moment of switch state change) doesn't happen. I wonder if it is a timing/stepping on each other issue.
If you have a handful of old android devices laying around, you could charge one at each outlet and have it report a change of charging state.
So how do we get eWeLink to make a plugin for Tasker. Is this all about making the API public?
Not sure. I would imagine since these other apps have been granted access to it then they would be able to grant access to a Tasker plugin.