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

**URL:** <https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369>\
**Category:** Apps\
**Tags:** app, z-wave, homey-pro\
**Created:** [October 13, 2022, 11:06am UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369 "2022-10-13T11:06:38Z")\
**Posts on this page:** 8\
**Page:** 17

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [April 18, 2026, 11:47am UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/330 "2026-04-18T11:47:03Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\
**Post date:** [April 18, 2026, 1:31pm UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/331 "2026-04-18T13:31:03Z")

</div>

Ok Arie,

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

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 20, 2026, 11:38pm UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/332 "2026-04-20T23:38:37Z")

</div>

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:

 ![Screenshot_20260421_013530_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/c/2ce5086d64ad6ce70d52d1f10009aba5e816dc7e.jpeg)

> [@Homey Self-Hosted Server with Docker on Linux | Megathread](https://community.homey.app/t/homey-self-hosted-server-with-docker-on-linux-megathread/146441/50):
>
> I’d first try the HomeyLink app instead. Otherwise, you probably have to change the default port temporary from 4859 to 80 to see if it connects; Make sure there’s no other local web server running on port 80.

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

---

<div class="post-metadata">

**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\
**Post date:** [April 21, 2026, 6:44am UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/333 "2026-04-21T06:44:39Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 22, 2026, 11:11pm UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/334 "2026-04-22T23:11:40Z")

</div>

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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/b/0b79e14a87ffc83ff0fee2af7d1c857fd41952fd.jpeg)

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

Example:

```auto
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

```

---

<div class="post-metadata">

**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\
**Post date:** [April 23, 2026, 6:57am UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/335 "2026-04-23T06:57:41Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\
**Post date:** [April 23, 2026, 11:15am UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/336 "2026-04-23T11:15:14Z")

</div>

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

```auto
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?

---

<div class="post-metadata">

**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\
**Post date:** [April 23, 2026, 12:12pm UTC](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369/337 "2026-04-23T12:12:51Z")

</div>

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](http://ghcr.io/athombv/homey-shs:latest)  
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…

[Previous page](https://community.homey.app/t/app-pro-homesh-controller-homesh-satellite-connect-homey-pro-2023-to-homey-pro-for-led-speaker-zwave-satellite-and-network-resource/70369.md?page=16)
