# Port Forwarding in App 8.0

**URL:** <https://community.homey.app/t/port-forwarding-in-app-8-0/104066>\
**Category:** Questions & Help\
**Created:** [February 15, 2024, 4:19pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066 "2024-02-15T16:19:42Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Stef\_Jacops](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stef_jacops/32/101012_2.png) [@Stef\_Jacops](https://community.homey.app/u/Stef_Jacops)\
**Post date:** [February 15, 2024, 10:09pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/21 "2024-02-15T22:09:03Z")

</div>

> [@Le\_Cactus](#):
>
> Even then I still need their cloud to authenticate?

Not sure about that one.

---

<div class="post-metadata">

**Author:** ![KestasM](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kestasm/32/97463_2.png) [@KestasM](https://community.homey.app/u/KestasM)\
**Post date:** [February 15, 2024, 10:13pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/22 "2024-02-15T22:13:10Z")

</div>

Thank you.  
In reality, it’s the same and nothing new, just added the climate button. Sad, could have named it as version 7.8 but not 8.0

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [February 16, 2024, 6:07am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/23 "2024-02-16T06:07:56Z")

</div>

> [@Stef\_Jacops](#):
>
> You can communicate directly with your homey.  
> Otherwise it will communicate via the cloud.

The cloud is still used for authentication, so if Athom’s cloud is down it won’t work (it also depends on Athom’s DNS servers).

Also, this feature depends on having a (semi-)static public IP address, which is becoming less and less of a given.

---

<div class="post-metadata">

**Author:** ![Gustav\_Persson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gustav_persson/32/56442_2.png) [@Gustav\_Persson](https://community.homey.app/u/Gustav_Persson)\
**Post date:** [February 17, 2024, 3:01pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/24 "2024-02-17T15:01:57Z")

</div>

I think that there should be link on the settings page like “Educate yourself of the security implication” which links to a page that gives unbiased information what port forwarding introduces as security risks to your network.

On the same page a step by step for some popular routers could be included.

Providing this feature without also discussing the security topic is irresponsible according to me since not all Homey users are aware of this topic and can make an informed decision.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [February 17, 2024, 6:11pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/25 "2024-02-17T18:11:06Z")

</div>

At least with this feature Athom are offering TLS support, with their Home Assistant app they say “you have to open up a port on your router to forward to your Home Assistant instance”. Completely irresponsible IMO.

---

<div class="post-metadata">

**Author:** ![Gerard\_L](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerard_l/32/30781_2.png) [@Gerard\_L](https://community.homey.app/u/Gerard_L)\
**Post date:** [February 22, 2024, 9:19am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/26 "2024-02-22T09:19:13Z")

</div>

It did not works on a AMPLIFI WiFi router.  
The router is via a utp cable connected to Ziggo modem.  
The WiFi of Ziggo modem is switched off  
Need I works directly to Ziggo WiFi to get port forwarding.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [February 22, 2024, 9:28am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/27 "2024-02-22T09:28:09Z")

</div>

Port forwarding needs to be configured on your main router (the one connected to your internet provider’s cable), unless you’re using double NAT (a router connected to a router), in which case you will have to configure it on both routers (but double NAT is not something you want).

---

<div class="post-metadata">

**Author:** ![Gerard\_L](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerard_l/32/30781_2.png) [@Gerard\_L](https://community.homey.app/u/Gerard_L)\
**Post date:** [February 22, 2024, 9:58am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/28 "2024-02-22T09:58:33Z")

</div>

Need I set the AMPLIFI to bridge mode?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [February 22, 2024, 10:17am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/29 "2024-02-22T10:17:26Z")

</div>

If you have to ask… 😅

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [February 22, 2024, 10:17am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/30 "2024-02-22T10:17:30Z")

</div>

No, the router should be in bridge mode and work as a modem only.  
It depends on your provider if this is possible or not.

I had an older Vodafone cable router that could be set to bridge mode via vodafone account portal.  
The newer one can’t be usednin bridge mode.  
Now have a double NAT and ports must be forwarded in both routers.  
But thanks to a fixed public IP I still can use my domain.

---

<div class="post-metadata">

**Author:** ![Gerard\_L](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerard_l/32/30781_2.png) [@Gerard\_L](https://community.homey.app/u/Gerard_L)\
**Post date:** [February 22, 2024, 10:21am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/31 "2024-02-22T10:21:47Z")

</div>

I will look in the Ziggo modem setting and set the forwarding settings  
I see in Ziggo no specific port forwarding setting but only a range.  
There is only external port setting and no internal port setting  
I have set external to 4859 and internal to 443  
Neeed I do the Same for AMPLIFI router or need I to set both to 443

---

<div class="post-metadata">

**Author:** ![Gerard\_L](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerard_l/32/30781_2.png) [@Gerard\_L](https://community.homey.app/u/Gerard_L)\
**Post date:** [February 22, 2024, 10:54am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/32 "2024-02-22T10:54:29Z")

</div>

It works now  
At AMPLIFI router I have set both to port 443  
At Ziggo modem the external are set 4859 and internal port set to 443  
Thanks for your responses

---

<div class="post-metadata">

**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:** [March 10, 2024, 11:04am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/33 "2024-03-10T11:04:52Z")

</div>

> [@robertklep](#):
>
> this feature depends on having a (semi-)static public IP address

I am confused and would appreciate a more detailed explanation.

1. I do not understand why a (semi) static IP is needed.

- Your mobile phone app is not aware of a static IP, it will authenticate with the Athom cloud who then forwards the request to your home IP known at that time (the known external IP from your Homey, dynamic or not) to the port that you provided in the new Port Forwarding feature.
- Your browser app (from remote) also does not use your static IP. You browse to [https://my.homey.app/](https://my.homey.app/) which will be translated in the Athom cloud to your home IP (same as above)

1. Nor do I understand what we gain in speed here. It is probably something else in the new App, but unrelated to port fowarding

I do understand that it may be easier for some / very particular use cases where port 443 is in use or where Homey is somewhere in the home network (double NAT/VLAN, etc) that could benefit from port forwarding to Homeys local IP.

Athom do not say all this in their comments: they say it it is the long-awaited feature for HP2023 users.  
I really do not understand why most users would care about this. Am I missing something?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 10, 2024, 11:14am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/34 "2024-03-10T11:14:54Z")

</div>

> [@Rrrr](#):
>
> I am confused here and would appreciate a more detailed explanation.
> 
> 1. I do not understand why a (semi) static IP is needed.
> 
> - Your mobile phone app is not aware of a static IP, it will authenticate with the Athom cloud who then forwards the request to your home IP known at that time (the known external IP from your Homey, dynamic or not) to the port that you provided in the new Port Forwarding feature.

It means that it will not function when your internet provider is using CGNAT.

> [@](#):
>
> 1. Nor do I understand what we gain in speed here.

Once the Homey app is connected to your router, communication with your Homey isn’t being proxied through Athom servers anymore. I think that practically speaking the speed increase will be negligible (and also, since the app still requires the Athom cloud servers for initial setup, if those servers are offline you still can’t access your Homey, even with port forwarding enabled).

> [@](#):
>
> I do understand that it may be easier for some / very particular use cases where port 443 is in use or where Homey is somewhere in the home network (double NAT/VLAN, etc) that could benefit from port forwarding to Homeys local IP.

I don’t think it will work when both the app and Homey are on a local network (also because not all routers support hairpin NAT).

> [@](#):
>
> Athom do not say all this in their comments: they say it it is the long-awaited feature for HP2023 users.  
> I really do not understand why most users would care about this. Am I missing something?

Yes, namely that Homey’s marketing mostly consists of BS. I think 99.9% of Homey users don’t care about this feature at all.

---

<div class="post-metadata">

**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:** [March 10, 2024, 11:48am UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/35 "2024-03-10T11:48:36Z")

</div>

@robertklep Many thanks Robert, appreciated!

> [@robertklep](#):
>
> it will not function when your internet provider is using CGNAT

Let me try to rephrase:

- Port forwarding is only useful for some HP2023 users with specific use cases (VLAN/double NAT/etc).
- “it [port forwarding] will not function when your internet provider is using CGNAT[, unless you have a static IP]”.
- Most users with a HP2023 whose ISP uses CGNAT will not have any trouble. Some that do have a network issue, like syncing Homey with Google Home due to CGNAT can opt for a static IP (optionally with port forwarding) and hope that solves the issue.

**Background**  
Most users do not now know their ISP is using CGNAT even though more and more ISPs are. When you have an ISP with CGNAT, it makes it difficult to forward traffic to ports in your Home network as your external IP could be the same as someone else.

This can usually be solved if the user can request (and pay) the ISP for a static external IP which is unique and can be addressed from anywhere so routing to your network is straightforward.

(another complication here is that some ISPs with CGNAT provide external static IPs on the basis of a VPN, but then your last chance is Athom support).

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 10, 2024, 12:24pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/36 "2024-03-10T12:24:42Z")

</div>

> [@Rrrr](#):
>
> - Port forwarding is only useful for some HP2023 users with specific use cases (VLAN/double NAT/etc).

I don’t see how VLAN/double NAT are relevant here, because I can’t think of a way where _Homey’s_ port forwarding feature is useful for that.

> [@](#):
>
> - “it [port forwarding] will not function when your internet provider is using CGNAT[, unless you have a static IP]”.

Using CGNAT rules out static/fixed IP addresses (it’s “either/or”).

> [@](#):
>
> - Most users with a HP2023 whose ISP uses CGNAT will not have any trouble.

Port forwarding is not possible at all if your ISP uses CGNAT, because CGNAT works port-based itself (it’s basically the same as NAT on your home router, just on a larger scale). So Homey’s port forwarding feature will not work, and you have to rely on the existing system where Athom’s cloud servers proxy between the app and your Homey.

> [@](#):
>
> When you have an ISP with CGNAT, it makes it difficult to forward traffic to ports in your Home network as your external IP could be the same as someone else.

It makes it _impossible_ to forward traffic to ports in your home network.

---

<div class="post-metadata">

**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:** [March 10, 2024, 12:44pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/37 "2024-03-10T12:44:37Z")

</div>

I have a provider with CGNAT, but I requested a static IP and can do all the port forwarding I need.  
There may be different CGNAT implementations of course.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 10, 2024, 12:58pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/38 "2024-03-10T12:58:56Z")

</div>

If your provider can offer static IP addresses, they will be able to do that _besides_ using CGNAT.

Most users just use their internet connection for TikTok or Netflix and those are served through the CGNAT pool, but more tech-savvy users that request a static IP address will get one from the “static pool”, usually for an increased subscription price.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [March 10, 2024, 1:02pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/39 "2024-03-10T13:02:23Z")

</div>

> [@Rrrr](#):
>
> There may be different CGNAT implementations of course.

In other words, you requested a fixed or dynamic IP for port forwarding on your router. The provider disabled CGNAT for you.

---

<div class="post-metadata">

**Author:** ![MGB](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mgb/32/79675_2.png) [@MGB](https://community.homey.app/u/MGB)\
**Post date:** [April 18, 2024, 7:36pm UTC](https://community.homey.app/t/port-forwarding-in-app-8-0/104066/40 "2024-04-18T19:36:39Z")

</div>

hey,  
did you get it to work?  
I cant get mine to work although it seems to be everything set up as it should

[Previous page](https://community.homey.app/t/port-forwarding-in-app-8-0/104066.md?page=1)

[Next page](https://community.homey.app/t/port-forwarding-in-app-8-0/104066.md?page=3)
