I try create a test application for EweLink.
I used Postman and everything matches the description until the moment
I want to change the state of the switch using
The protocol of this device is multi-channel protocol, so you should pass the parameter control like this, you can try:
“params”:{
“switches”: [
{
“switch”: “off”,
“outlet”: 0
},
{
“switch”: “off”,
“outlet”: 1
},
{
“switch”: “off”,
“outlet”: 2
},
{
“switch”: “off”,
“outlet”: 3
}
]
}
This situation can happen if there are fluctuations in the network. These disconnections are usually very brief — lasting just a few tens or hundreds of milliseconds.
Please observe whether the issue happens repeatedly with specific devices or scenes. If you find that the same devices frequently fail to execute due to being offline, it might be a device-side firmware issue.
In that case, you can take note of the affected devices and the scene names, then submit a support ticket through the eWeLink app via Profile > Help & Feedback > Feedback (top right corner). Our team will look into the device logs for further analysis.
I see that Scenes fail many times, wheter manual or automatic.
If I activate manual scene of closing all curtains, many times I find one or several that didn’t work
Also automatic scenes. For example I have light sensor to close the curtain. Today the ligt sensor gave the order of closing. The first time failed…second time succeed.
See pictures below. The mouse is pointing the first time (failed). Next time, 5 seconds later succed.
Always when selecting the module in the app, it takes quite long to load, most of my scenes fail with error 4002. But at the same time the devices are online. For instance I have a scene which is disabling a device at specific time and sending a message. Unfortunately it fails in 99% of the cases. For test purposes, I have set a schedule for this device at the same time as the scene and it never fails to switch it off for few weeks now.
@eWeLink, please check the method used for module Scenes as it is causing all these troubles to all users and practically makes the scenes option useless. Note that I have multiple scenes with the same issue, but currently turned off as they do not execute properly due to that error.
We currently suspect that there may be an issue with the scene activation functionality, but we have not yet been able to reproduce the situation. Could you please provide us with your logs for analysis? If your device is synced as an add-on to the ihost, we would also appreciate it if you could share the add-on logs.
Thank you for your feedback regarding this issue. We are taking this matter seriously! Could you please also report this issue through the app? This will help us investigate whether the problem is occurring on the app side.