Advanced Flow: HTTP Request Timeout

Hi,

I’m trying to integrate Homey Pro (2023) with MuteDeck installed on my laptop.

In PowerShell on another device, I can run curl ``http://10.0.0.113:3491/v1/status which returns the following:

StatusCode        : 200
StatusDescription : OK
Content           : {
“call”: “inactive”,
“control”: “system”,
“mute”: “inactive”,
“record”: “disabled”,
“share”: “disabled”,
“status”: 200,
“teams_api”: “disabled”,
“video”: “disabled”
}
…
RawContent        : HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Content-Length: 200
Content-Type: application/json

                {
                    "call": "inactive",
                    "control": "system",
                    "mute": "inactive",
                    "record": "disabl...

Forms             : {}
Headers           : {[Access-Control-Allow-Origin, *], [Content-Length, 200], [Content-Type, application/json]}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : mshtml.HTMLDocumentClass
RawContentLength  : 200

I’m trying to get Homey to do this same request in an Advanced Flow, so that I can use this to trigger other devices.

The test flow I have is as follows:

But as you can see, the GET request is timing out for some reason. The IP of the Homey Pro is 10.0.0.227 (ethernet) and 10.0.0.247 (WiFi), so on the same range as my laptop.

Not really sure where to go from here?

Any help is appreciated - thank you.

Kind regards,

Callum

Hi Callum, and welcome.

To see if there’s any network related issues:
Navigate to this URL in a web browser (of a device in the same subnet):

What is the response?

Hi Peter,

Thank you for the reply. You’ve definitely pointed me in the right direction - loading that page in a browser didn’t work, so I went looking in the laptop’s Windows Firewall and found that if I explicitly allow that port, the Browser and Homey immediately start working!

Thank you for that helpful nudge!

Kind regards,

Callum

1 Like

No problem!

It"s the first thing I try, to see if the issue is not in the request itself.

Firewalls and network tools (like Adguard PiHole) would’ve been in my follow up reply :wink: