Delay in http get Action

[Chris]

I'm using MacroDroid to control my smart hifi system. It's done by sending with URLs http gets.

I noticed that sometimes there is a delay of a couple of seconds before the subsequent actions are executed. The delay is varying from 0...6 seconds. The log also shows this.

I've unchecked the 'wait until finished...' checkbox.

It happens especially when repeating the action multiple times in a row (i.e. when changing volume).

Not sure if it's related to MD or my device... Does anyone recognise this behaviour?

Thanks and regards Chris

 

[FrameXX]

I'm using MacroDroid to control my smart hifi system. It's done by sending with URLs http gets.

I noticed that sometimes there is a delay of a couple of seconds before the subsequent actions are executed. The delay is varying from 0...6 seconds. The log also shows this.

I've unchecked the 'wait until finished...' checkbox.

It happens especially when repeating the action multiple times in a row (i.e. when changing volume).

Not sure if it's related to MD or my device... Does anyone recognise this behaviour?

Thanks and regards Chris

Of course it takes a while to load the website.

 

[Elenkhos]

Of course it takes a while to load the website.

I think Chris is asking why MacroDroid doesn't advance immediately to the next action when HTTP GET is executed. It should wait only when the checkbox is checked.

My macros always wait for the HTTP GET action to be executed to check if it was successful so I can't comment on the main issue.

 

[Dm114]

I think Chris is asking why MacroDroid doesn't advance immediately to the next action when HTTP GET is executed. It should wait only when the checkbox is checked.

My macros always wait for the HTTP GET action to be executed to check if it was successful so I can't comment on the main issue.

Same for me

 

[Chris]

I think Chris is asking why MacroDroid doesn't advance immediately to the next action when HTTP GET is executed. It should wait only when the checkbox is checked.

My macros always wait for the HTTP GET action to be executed to check if it was successful so I can't comment on the main issue.

Exactly, thanks for clarifying.
There is not really a website opened, because it is basically only sending a HTTP-address and is receiving a string of HTTP as an response.

The reason I find the especially strange is that - I assume - the standard Yamaha app is working the same, and there I don't see such a lag. I'm not sure however if the delay is caused by MD or by something else (maybe MD<>device?). I already skimmed down my macro to make sure it is that action causing the issue, and that seems to be the issue.


Any ideas are welcome,

Chris

 

[FrameXX]

There is a great plugin HTTP request shortcuts that can also make an HTTP GET as an MacroDroid action. If MacroDroid delay really annoys you, you can try this plugin.

 

[Chris]

There is a great plugin HTTP request shortcuts that can also make an HTTP GET as an MacroDroid action. If MacroDroid delay really annoys you, you can try this plugin.

Thanks, I will try that!

 

[Elenkhos]

There is a great plugin HTTP request shortcuts that can also make an HTTP GET as an MacroDroid action. If MacroDroid delay really annoys you, you can try this plugin.

Yep, that's a handy plugin in some cases. It's really a shame that MacroDroid can't pass variables to it.

 

[Chris]

Yep, that's a handy plugin in some cases. It's really a shame that MacroDroid can't pass variables to it.

Hm, that's quite a drawback indeed, especially because I use the HTTP-response to update my current volume level in a variable.
Well, in the meantime I keep searching for the root cause. BEcause I'm not even sure if MD is causing the issue.

 

[MacroDroidDev]

I've just looked over the code and I don't see any reason why there should be any delay in running subsequent actions if you don't have the wait until complete selected. The HTTP Get is done in a background thread and the next action should continue straight away. I've done some basic testing just getting a web page many times and I couldn't see any delay at all.

 

[Chris]

I've just looked over the code and I don't see any reason why there should be any delay in running subsequent actions if you don't have the wait until complete selected. The HTTP Get is done in a background thread and the next action should continue straight away. I've done some basic testing just getting a web page many times and I couldn't see any delay at all.

Hi Jamie. Thanks for the check. Than I consider it a as a problem on my device. Not sure if I can do anything about it, and otherwise I need to life with it.

Thanks all for the input and ideas.

regards Chris