[APP][Pro] Homesh Controller & Homesh Satellite - Connect Homey Pro 2023 to Homey Pro for Led, Speaker, Zwave(satellite) and network resource

Apps
, ,
330

Well I need to see why it is connecting on port 80.

Homes uses a homey-build in function to find and connect and the port (on normal Homeys) is never port 80.

Currently I haven’t setup a HsH tho.

331

Ok Arie,

Pls let me know if you need a diagnostic report, if it can help…

332

Odd, my answer is right below your post in the “self-hosted server” topic.
Maybe it’s hidden from you for some reason. Here’s a screenshot, Domenico:

Screenshot20260421013530Ecosia
Screenshot20260421013530Ecosia1079×2496 276 KB

But I’ll leave Arie to it, as he developed the Homesh app set.

333

Hi Peter,

Ok, but the question is: How I can change the TCP port on Homesh App…

Hope Arie can give a suggestion on that

334

You can’t, Domenico; you only can change the port of HSHS, to see if that helps, by editing the docker compose file. But, maybe Arie is investigating already, as Homesh should work on HSHS in theory.

Screenshot20260423010355Ecosia
Screenshot20260423010355Ecosia1079×2043 180 KB

https://support.homey.app/hc/en-us/articles/24010537261980-How-to-install-Homey-Self-Hosted-Server-with-Docker-on-Linux

Example:

services:
  homey-shs:
    image: ghcr.io/athombv/homey-shs:latest
    container_name: homey-shs
    restart: unless-stopped
    network_mode: host
    privileged: true
    volumes:
      - ~/.homey-shs:/homey/user
    PORT_SERVER_HTTP: 80
335

Hi Peter,

Ah, good suggestion. In the meantime Arie find a correction I can give a try.

So I have to stop homey-shs container and to restart it with the settings you’ve proposed.

Can I proceed also by using the docker start command instead of using docker compose file?

336

Hi, just tried with docker compose file but the response is the following:

docker compose -f homey-shs.yml up --detach
validating /home/deadmin68/homey-shs.yml: services.homey-shs additional properties 'PORT_SERVER_HTTP' not allowed

Any other idea?

337

Retried just now…

I have just restarted successfully the homey-shs container by giving the directive related to env variable PORT_SERVER_HTTP:80. I have made the correction in yml file by specifing the keyword “environment” before the directive:

services:
homey-shs:
image: Package homey-shs · GitHub
container_name: homey-shs
restart: unless-stopped
network_mode: host
privileged: true
volumes:

  • ~/.homey-shs:/homey/user
    environment:
  • PORT_SERVER_HTTP:80

Now homey shs started with the env variable in place but the result is the same. When I try to reach Satellite part on SHS from Controller part on my HPE2019 the same error rises:

connect ECONNREFUSED 192.168.1.63:80

Hope Arie can give a solution…