Problem between eWeLink-Macrodroid webhooks calls

Advanced Plan
1

Hey @ward , can you ask the team if they observe any problems on the cloud side for the action call webhook to trigger.macrodroid.com?

Unfortunately, webhooks from ewelink web to macrodroid have stopped working. I checked and the problem is on the ewelink-macrodroid line for 100%. I just can’t determine whether it’s on the ewelink or macrodroid side…
eWeLink-other webhook works. Other-Macrodroid works… so it’s something between ewelink-macrodroid.
Theses… it’s some problem on the ewelink side, maybe some timeout or a problem on the macrodroid side in the form of blocking your servers, but that’s just a guess. Any other combination works, so it’s not a fault of the entire webhook. But something is clearly wrong because 99.99% of webhook calls do nothing.

Before I break through the walls of communication with macrodroid, I’d rather ask ewelink first. :slight_smile:

2

Thx for the message, let me check this.

1 Like
3

We found timeout errors on requests to trigger.macrodroid.com.

But we just found it should work now with testing; there could be temporary issues with Macrodroid.

Please try again and let us know if your scenes work.

1 Like
4

I check and I think the problem is still there…

Macrodroid seems to be very overloaded but it responds so I guess that on the ewelink side the execution time may be too short or something and it ends with a quick timeout. Manual execution of the same webhook in the browser works although it is clearly very slow even up to a few seconds (10s) but it will execute in the end so the execution time on the ewelink side may be too short. In a sense it is probably normal but it does not take into account extreme situations. :slight_smile:

The fault lies in the load of Macrodroid itself which produces extreme delays but maybe something could be changed in the settings on the ewelink side so that the timeout occurs much much later…

Theoretically it is doable because I currently use sequematic.com as a proxy. Yes it is slow, very slow but through sequ, webhook is executed after time. In the case of eWeLink nothing happens because probably everything counts timeout. :slight_smile:

But eWeLink->SEQU->Macrodroid itself is not very efficient. :slight_smile:

5

Apparently someone is spamming the MD server and that’s why there’s an overload and with a slightly shorter timeout on ewelink this problem was born. :slight_smile:

… oh well, there’s always some scumbag who’ll mess things up for others.

6

So MacroDroid Dev was informed about the situation and blocked the specific IP and for now it looks like the situation is back to normal… time will tell for sure. :slight_smile:

7

That’s a lot :exploding_head:

Glad it settled down in the end.

1 Like