Cannot install app via Homey CLI "Homey seems to be offline"

Hello,

My Homey Pro (early 2023) is fully functional and connect to Wifi and Ethernet. I can ping both IPs from my laptop on which the CLI is installed.

However, when running

homey app run or homey app run --remote I get the following error message:

Error: XXXX (----) seems to be offline. Are you sure you're in the same LAN network?
    at /usr/local/lib/node_modules/homey/lib/AthomApi.js:235:17
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async AthomApi.getActiveHomey (/usr/local/lib/node_modules/homey/lib/AthomApi.js:223:24)
    at async App.run (/usr/local/lib/node_modules/homey/lib/App.js:153:19)
    at async exports.handler (/usr/local/lib/node_modules/homey/bin/cmds/app/run.js:43:5)

This seems to be a frequent issue but I could not solve it so far. Especially as I can successfully connect to it over SSH and even ping it.

Any suggestion?

Are your laptop and Homey in the same network segment/VLAN?

You’re right though that this rather stupid issue occurs frequently, not just with the CLI but also with the mobile apps. Athom apparently isn’t able to solve it.

Yes, same VLAN. I have a very basic network setup.

I’ll give it a try with another computer to see if maybe it is on Mac OS side.

Frustrating…

1 Like

hi @Cedric_Hernalsteens
same pb here ! I keep investigating…
I will post if I find a solution / workaround :wink:
have a found something ?
regards

Can you check the Homey connection in Homey settings? I my case, the Homey was only cloud connected. A restart got it bavk into local connection.

Unfortunately, I haven’t found a solution yet.

Homey Pro is correctly connected via Wifi and Ethernet at the moment and everything works as expected except this.

What do you mean by “cloud connected” ?

Mobile app, settings/general.

If this state is not local connected while you are in the same LAN like your Homey, then the chance is high that your PC also can’t connect locally.

Thanks, I"ll check that.

I could verify that I was indeed connected locally (iOS app was connected locally to my Homey Pro).

I finally found the culprit: on my Mac, the settings where such that my terminal app did not have access to the local network… for some reason I was not prompted to enable it (this can be manually enabled in the settings).

Problem solved.

1 Like