# Http get/post…-card timeouts

**URL:** https://community.homey.app/t/http-get-post-card-timeouts/153946
**Category:** Questions & Help
**Tags:** flow
**Created:** [April 18, 2026, 5:11pm UTC](https://community.homey.app/t/http-get-post-card-timeouts/153946 "2026-04-18T17:11:54Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Jan-Erik\_Hallkvist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_hallkvist/32/79000_2.png) [@Jan-Erik\_Hallkvist](https://community.homey.app/u/Jan-Erik_Hallkvist)
#### Post date: [April 18, 2026, 5:11pm UTC](https://community.homey.app/t/http-get-post-card-timeouts/153946/1 "2026-04-18T17:11:54Z")

</div>

Question about using the ‘Logic’ http get/post… card.

When calling an address within the Homey subnet scope and the called device is offline, the get card times out ok in a few seconds. Likewise if the call is a bad/offline dns url on internet.

But if calling an ip-number in another local ‘visible’ subnet or an ip number on internet (when no response) the card keep waiting until the normal flow card timeout (approx. 60 sec) occurs.

I wonder if this is a flaw with the card or expected ‘ip behavior’ since a fetch in Homeyscript act likewise when called from a HS-card?

When used in an ‘Advanced Trigger’-card hierarchy, this sometimes makes that those cards might time out first, getting the error from the wrong spot.

Best regards, Jan