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 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
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”
I just took a look what endpoint is used by 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:
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.
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.
@diapolon Could you test as well the above solution? What is your exprience?
I have been experiencing this “homey_offline” behavior since this morning.
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?
