# \[APP\]\[Pro\] Homesh Controller & Homesh Satellite - Connect Homey Pro 2023 to Homey Pro for Led, Speaker, Zwave(satellite) and network resource **URL:** \ **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:** 20\ **Page:** 16
**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:** [December 2, 2025, 9:05pm 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/309 "2025-12-02T21:05:07Z")
> [@Domenico\_Etere](#): > > router restart Did you reserve IP addresses for both Homeys? ---
**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:** [December 3, 2025, 7:59am 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/310 "2025-12-03T07:59:48Z")
Yes, sure. For both Homeys I reserved static IP address in DHCP configuration of my router ---
**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:** [December 3, 2025, 5:48pm 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/311 "2025-12-03T17:48:30Z")
Thanks, so we can rule out changed IP addresses. A workaround: @ Pro 2019: Install the [Net Scan app](https://community.homey.app/t/app-pro-netscan-version-2-0-6-test-version-2-0-8/47454) Add a “TCP Port” device Enter your router’s IP address Enter the port, either 80 or 443 (just test which one connects) ![Screenshot_20251203_185210_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aa6beba62deffe34462768c9abe93190340c1a38.jpeg) Now you can restart the Homesh app(s) automatically when Homey has (re)established the connection with your router (FlowComments is just an example app name): ![Screenshot_20251203_184129_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/1/b1b437d3b4f70aef9a3a5c46df839eb084440a0b.jpeg) ---
**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:** [December 3, 2025, 6:24pm 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/312 "2025-12-03T18:24:06Z")
Hi Peter, Do you suggest to automatically restart the Homesh Controller APP when the router has been restarted and back online? Right? But I already do it manually after my router restart and the Homesh Controller doesn’t recover, I have to put manually the pin code to recover successfully. For that reasons I asked Arie to let to put the pin code by a Flowcard. It would be possible to do that because the Homesh Controller APP has connection back active to the Satellite part after LAN connection recovered ---
**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:** [December 3, 2025, 6:32pm 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/313 "2025-12-03T18:32:59Z")
Yes indeed, but I misunderstood the real issue. > [@Domenico\_Etere](#): > > have to put manually the pin code I missed that part, sorry 🫣 ---
**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:** [December 4, 2025, 7:59am 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/314 "2025-12-04T07:59:08Z")
no problem Peter, your suggestions are appreciated! 😃 👍 ---
**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:** [December 11, 2025, 10: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/315 "2025-12-11T10:57:06Z")
Hello Arie, It is happened again after my router restart. From my HPE2019 I see Homesh Controller which loses connection to Satellite part on my HPE2023 side: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9bd55c0139ba268eac8e5bf16426a9037190db09.png) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/8/583c4c2023a474f2c88b1fbab97e088c7bf91c43.png) I have to put Satellite PIN to recover even if I have restarted Homesh Controller and Satellite APPs on both Homeys. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/1/f110b7d28131840827d64b3eca1fdb1ff8140464.png) Below the diagnostic report on HPE2019 side (Controller part): efaa7e65-3c5b-4886-b04c-a242254ee2ef and the diagnostic on HPE2023 side (Satellite part): b9e24225-f1cd-4eff-8d08-f09786b490a0 Please let me know ---
**Author:** ![Wilfred\_Greven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wilfred_greven/32/13070_2.png) [@Wilfred\_Greven](https://community.homey.app/u/Wilfred_Greven)\ **Post date:** [January 3, 2026, 2:01pm 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/316 "2026-01-03T14:01:58Z")
Could we use Homesh also for SHS and HP23? ---
**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:** [January 4, 2026, 3:12am 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/317 "2026-01-04T03:12:52Z")
Why wouldn’t it, Wilfred? It’s created to connect a Pro 2016-2019 to a Pro 2023 and v.v. And you can install the apps to see if it works. You can’t install a ‘wrong’ app on a Homey App store says: ![538](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/33fe60c8e3a45f317a420540650ea6639e796a90.jpeg) ---
**Author:** ![Wilfred\_Greven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wilfred_greven/32/13070_2.png) [@Wilfred\_Greven](https://community.homey.app/u/Wilfred_Greven)\ **Post date:** [January 4, 2026, 9:39am 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/318 "2026-01-04T09:39:14Z")
I have used it with a HP2016 and a HP2023 and it worked nearly 100%. Now i see users only use SHS with homeylink but for a lot of people it didn’t work. I am looking at the pro and con for SHS (memory at HP2023 is a bottleneck) And i think i am gonna use homesh (experience in the past). How do you look at it? ---
**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\ **Post date:** [January 4, 2026, 10:40am 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/319 "2026-01-04T10:40:51Z")
For 130-150 euros you have a CM4 **1** 08032 to place in the Homey Pro 2023 and than have 8GB memory. Done the [modding](https://community.homey.app/t/modding-various-homey-pro-early-2023-modification-suggestions/79487) myself and runs already for 2 years very good. ---
**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\ **Post date:** [January 15, 2026, 12:00pm 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/320 "2026-01-15T12:00:34Z")
Found another trick > [@Homey SHS - Trigger WebHooks locally?](https://community.homey.app/t/homey-shs-trigger-webhooks-locally/147816/5): > > Just note that the GET webhook cannot pass #, end of lines and icons like fire in the text. MQTT would do it, but I do not have the memory to install it slight_smile Solved with a Gemini HomeyScript encodeURL as per below (there is no need to decode on the receiving side). // EncodeURL // Script Version: 2.0 // Purpose: URL Encode text and return as a LOCAL tag // 1. Get the argument (safely handle empty input) let inputString = args[0]; if (inputString == null) { inputString = ""; }… ---
**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\ **Post date:** [January 15, 2026, 12:16pm 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/321 "2026-01-15T12:16:39Z")
@Wilfred_Greven I am going through exactly the same: no memory on HP2023 and moving parts to SHS. Logging: I am now using the built-in webhook to send logging texts to SHS where I have moved Telegram and Whatsapp to save memory on HP2023. With a [little text encoding](https://community.homey.app/t/homey-shs-trigger-webhooks-locally/147816/5), it works like a charm. HomeyLink: I installed HomeyLink and it seems to work fine. What are the issues you are seeing? Homesh Triggers: This would require installing Homesh on both sides. I used it in the past and looks much like Advanced Triggers (same star developer @Arie_J_Godschalk 🥰 ). But it means more complexity/maintenance of starting flows on the other side and it would not save much memory. Before spending too much time building flows on SHS, I prefer to wait and see if and when Athom comes with a migration that will almost sure wipe out the work. Why are you considering Homesh? ---
**Author:** ![Wilfred\_Greven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wilfred_greven/32/13070_2.png) [@Wilfred\_Greven](https://community.homey.app/u/Wilfred_Greven)\ **Post date:** [January 15, 2026, 1:02pm 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/322 "2026-01-15T13:02:35Z")
> [@Wilfred\_Greven](#): > > I have used it with a HP2016 and a HP2023 and it worked nearly 100%. > > Now i see users only use SHS with homeylink but for a lot of people it didn’t work. > I am looking at the pro and con for SHS (memory at HP2023 is a bottleneck) > And i think i am gonna use homesh (experience in the past). That is why. ---
**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 13, 2026, 7:04pm 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/324 "2026-04-13T19:04:34Z")
I have a similar issue. From my HPE 2019 I can’t reach SHS by using Homesh controller APP on my HPE2019. Viceversa it is working fine: from my SHS i can reach HPE2019 by using Homesh controller APP on my SHS. Did you have any suggestion? The error that rises on my HPE2019 side is “connect ECONNREFUSED -IPaddrSHS-:80”, it happens when I try to connect to the Homesh Satellite APP on SHS. Please could anyone help me? ---
**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 15, 2026, 10:12am 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/325 "2026-04-15T10:12:55Z")
No suggestion from anyone? ---
**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 15, 2026, 8:33pm 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/326 "2026-04-15T20:33:08Z")
I’m sorry but the other day I responded to your exact same question in a post of yours elsewhere 🤷‍♀️ ---
**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 17, 2026, 7:35am 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/327 "2026-04-17T07:35:47Z")
Hi Peter, In which post you’ve already responded? ---
**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 17, 2026, 3:45pm 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/328 "2026-04-17T15:45:03Z")
This one, Domenico 😉 > [@Homey Self-Hosted Server with Docker on Linux | Megathread](https://community.homey.app/t/homey-self-hosted-server-with-docker-on-linux-megathread/146441/49): > > I have a similar issue. From my HPE 2019 I can’t reach SHS by using Homesh controller APP on my HPE2019. Viceversa it is working fine: from my SHS i can reach HPE2019 by using Homesh controller APP on my SHS. Did you have any suggestion? The error that rises on my HPE2019 side is “connect ECONNREFUSED :80”, it happens when I try to connect to the Homesh Satellite APP on SHS. Please could anyone help me? ![Screenshot20260417174411Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/b/cb3fec757c3906e6012118a15d036b5228ce8f07.jpeg) ---
**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, 10:58am 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/329 "2026-04-18T10:58:09Z")
Hi Peter, I’ve put the same post in two different places but I see that anyone have not yet answered.. 😔 [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=15) [Next 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=17)