# Web api issues?

**URL:** <https://community.homey.app/t/web-api-issues/112610>\
**Category:** Questions & Help\
**Created:** [July 9, 2024, 9:26am UTC](https://community.homey.app/t/web-api-issues/112610 "2024-07-09T09:26:36Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [July 9, 2024, 9:26am UTC](https://community.homey.app/t/web-api-issues/112610/1 "2024-07-09T09:26:36Z")

</div>

Are there any web api issues?

Trying to use the HomeyAPIV3Cloud command _api/manager/devices/device_ on Homey 2023 getting a json with all device info. Reply is “homey\_offline”. Have been using this command for months now.  
Using the same _[http://192.168.2.40/api/manager/devices/device](http://192.168.2.40/api/manager/devices/device)_ local api command: no problems and result as expected.

The Homey web app says: Cloud status: connected. Using wifi for allmost a year without problems (not moving Homey or wifi devices). Already tried:

- restart Homey (via app and via pulling the adapter)
- restart modem, router and wifi
- apps acting as expected
- Homey browser webapp and Android app no messages or errors
- [https://status.homey.app](https://status.homey.app) says no problems

Seems that the web api is not working. Is there a max. number of calls each month or a max number of Mb using web api?  
What can I check or test?

---

<div class="post-metadata">

**Author:** ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)\
**Post date:** [July 9, 2024, 9:59am UTC](https://community.homey.app/t/web-api-issues/112610/2 "2024-07-09T09:59:05Z")

</div>

Did the IP maybe change? If you didn’t assign a fixed IP to your homey in your routers settings the IP can change from time to time.

**EDIT:** Ah sorry local works, only cloud not, have misread that part.

How are you accessing the cloud? Maybe just your token expired?

---

<div class="post-metadata">

**Author:** ![diapolon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/diapolon/32/82612_2.png) [@diapolon](https://community.homey.app/u/diapolon)\
**Post date:** [July 9, 2024, 11:01am UTC](https://community.homey.app/t/web-api-issues/112610/3 "2024-07-09T11:01:30Z")

</div>

same for me for a couple of weeks

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [July 9, 2024, 11:06am UTC](https://community.homey.app/t/web-api-issues/112610/4 "2024-07-09T11:06:53Z")

</div>

What did Athom say about it?

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [July 9, 2024, 12:00pm UTC](https://community.homey.app/t/web-api-issues/112610/5 "2024-07-09T12:00:58Z")

</div>

I have created a new (Bearer) Token with Homey api keys (all options activated).  
This is the result in Postmaster getting all devices (see yellow parts): “417 Expectations Failed”

 ![Postmaster](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/9/09a8bb1f7c643749cf73b766113c02945bc76eb5.jpeg)

According Homey app is the Cloud status still “connected”.  
Any ideas?

---

<div class="post-metadata">

**Author:** ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)\
**Post date:** [July 9, 2024, 12:15pm UTC](https://community.homey.app/t/web-api-issues/112610/6 "2024-07-09T12:15:31Z")

</div>

Maybe that’s a misunderstanding on my part, but I thought the API keys are meant for the local api only?

---

<div class="post-metadata">

**Author:** ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)\
**Post date:** [July 9, 2024, 12:20pm UTC](https://community.homey.app/t/web-api-issues/112610/7 "2024-07-09T12:20:16Z")

</div>

I just took a look what endpoint is used by [https://tools.developer.homey.app](https://tools.developer.homey.app) and I can access the devices with an API key and using the same url used by the dev tools:

`https://<cloudid>.homey.athom-prod-euwest1-001.homeypro.net/api/manager/devices/device`

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [July 9, 2024, 12:37pm UTC](https://community.homey.app/t/web-api-issues/112610/8 "2024-07-09T12:37:36Z")

</div>

Thanks @staeff, this is working for me.  
Do you know what the diffrence is between your command and my `https://<cloudid>.connect.athom.com/api/manager/devices/device` ?

Has there been any changes recently in the web api calls, presuming I was using the latest web api calls.

---

<div class="post-metadata">

**Author:** ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)\
**Post date:** [July 9, 2024, 12:39pm UTC](https://community.homey.app/t/web-api-issues/112610/9 "2024-07-09T12:39:31Z")

</div>

That probably is for Athom to answer, maybe they just switched off to resolve the correct cloud server this way or they changed the URL without documenting it.

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [July 9, 2024, 12:43pm UTC](https://community.homey.app/t/web-api-issues/112610/10 "2024-07-09T12:43:37Z")

</div>

@diapolon Could you test as well the above solution? What is your exprience?  
I have been experiencing this “homey\_offline” behavior since this morning.

---

<div class="post-metadata">

**Author:** ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)\
**Post date:** [July 9, 2024, 12:48pm UTC](https://community.homey.app/t/web-api-issues/112610/11 "2024-07-09T12:48:26Z")

</div>

If you have either a static ip or some dyndns service and have enabled port forwarding for Homey you can also access the api via:

[https://123-123-123-123.homey.homeylocal.com:4859/api/manager](https://123-123-123-123.homey.homeylocal.com:4859/api/manager) (123.123.123.123 being your external ip)

---

<div class="post-metadata">

**Author:** ![diapolon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/diapolon/32/82612_2.png) [@diapolon](https://community.homey.app/u/diapolon)\
**Post date:** [July 9, 2024, 1:15pm UTC](https://community.homey.app/t/web-api-issues/112610/12 "2024-07-09T13:15:55Z")

</div>

i have the same problem, reboot homey don’t resolve, reboot modem also.  
I use [noip.com](http://noip.com) for expose local connection to internet (workaround)

---

<div class="post-metadata">

**Author:** ![diapolon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/diapolon/32/82612_2.png) [@diapolon](https://community.homey.app/u/diapolon)\
**Post date:** [July 9, 2024, 5:18pm UTC](https://community.homey.app/t/web-api-issues/112610/13 "2024-07-09T17:18:57Z")

</div>

> [@staeff](#):
>
> https://.homey.Athom-prod-euwest1-001.homeypro.net/api/manager/devices/device

Tried, it work…but it’s a temporary server? it’s not documented…

---

<div class="post-metadata">

**Author:** ![Torstein](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torstein/32/2043_2.png) [@Torstein](https://community.homey.app/u/Torstein)\
**Post date:** [July 10, 2024, 6:54am UTC](https://community.homey.app/t/web-api-issues/112610/14 "2024-07-10T06:54:24Z")

</div>

Not sure if a connected incident, but I suddenly get “Homey\_offline” when I’m outside local network, but that seems only to be in the app. When I try the web version it does not seem to throw a offline error…very strange behavior. Does this mean app is using other “calls/apps” then web version?

---

<div class="post-metadata">

**Author:** ![Torstein](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torstein/32/2043_2.png) [@Torstein](https://community.homey.app/u/Torstein)\
**Post date:** [July 10, 2024, 3:50pm UTC](https://community.homey.app/t/web-api-issues/112610/15 "2024-07-10T15:50:11Z")

</div>

Now we know…

 ![IMG_6622](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/7/2775b880947d0f94ed067861095dbcd586cde0a7.jpeg)

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [July 11, 2024, 2:41pm UTC](https://community.homey.app/t/web-api-issues/112610/16 "2024-07-11T14:41:15Z")

</div>

The HomeyAPIV3Cloud command `https://<cloudid>.connect.athom.com/api/manager/devices/device ` on Homey 2023 is up and running again.

 ![2024-07-11 16_40_12-Homey Status](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/f/5f1d1a88e3686dfd78b2f4ef04b2e944076c91f7.jpeg)

---

<div class="post-metadata">

**Author:** ![diapolon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/diapolon/32/82612_2.png) [@diapolon](https://community.homey.app/u/diapolon)\
**Post date:** [July 11, 2024, 3:19pm UTC](https://community.homey.app/t/web-api-issues/112610/17 "2024-07-11T15:19:05Z")

</div>

yes, now it work.
