Setting port forwarding for home assistant on port 8123

[Snigehere]

Hi - Hope someone can assist ...

my sky router is Model SR203 with Firmware Version 7.02.0001.R

I am trying to set up the home assistant application to allow remote connection over ssl  .. I need to port forward the inbound connection to port 8123 however the selection list is constrained by a set of pre defined rules and none include 8123 .. I could use a more generic rule and allow other ports but don't want to open my system in that way.

Is there a way to over ride the predefined list or get the predefined list updated to include home assistant? 

[jamesn123 · Accepted solution]

@Snigehere 

Under Security > Services you can add your own custom services

[Snigehere]

Many thanks for the help

[me0879]

Hi @Snigehere, I'm trying to do exactly the same thing. I have found how to add custom services but struggling how to specify forwarding to port 8123. Can you show what you created to get this to work? Thanks!

[mae-3]

@me0879 

Security Tab, then inbound rules and you'll need to spectify the service and LAN IP address of the home assistant server.

[me0879]

Hi @mae-3 , thanks for replying so quickly. Here's what I have...

192.168.0.61 is the static ip address of my respberry pi running home assistant. I must be missing something because I don't see how to specify port 8123 as the forwarding destination.

[mae-3]

@me0879 

The service isn't set correctly for port 8223 it is set for port 443.

[me0879]

Can you be more expansive on how it should be configured? I have tried changing 443 to 8123 and I have tried the start port as 443 and the end port as 8123 but it doesn't work. Clearly I don't understand what the configuration needs to look like. Can you help please?

[mae-3]

@me0879 

The service can be done by selecting the security tab, then services. One is then offered boxes that you full in with details that need to provided; the name of the service, which you can enter anything that is descriptive, type that can be TCP, UDP or both of these protocol types. The start port, and the finish port; usually the start and finish ports are the same numerical numbers.

[me0879]

I'm not being specific about the problem I'm trying to solve - sorry. Here is the example using some other router from the Home Assistant / DuckDNS config page....

Here is my latest attempt to replicate the above in my Sky Hub...

It's still not working. Anyone got any ideas?

[mae-3]

@me0879 

I'm aware of many configurations for home assistants, bridges, etc..., so will be able to help if you describe the issue accuartely. Just waiting for the screenshots to be appoved and I'll comment further. 😀

[mae-3]

@me0879 

Have you set up the RPi and can you access it internally on the LAN? The forwarding looks good for the router now to ports you have specified.

[me0879]

Yes, the RPi is working fine, I can see it locally using 192.168.0.61:8123/lovelace/default_view, it's just remotely via DuckDNS that doesn't work. As a bit of background, I have had Home Assistant running fine for a couple of years but recently switched from Virgin Media to Sky broadband. Clearly the VM router worked fine but I'm struggling to get Sky to do the same. I haven't restarted the router after the config changes. Is that necessary?

[mae-3]

@me0879 

Once the ports have been opened then it will need that RPi to communicate with the DuckDNS service, so one may need to restart the RPi or service itself, once you have restarted the router. And the service for updating dynamic DNS services usually takes a couple of hours to update on the internet DNS infrastructure globally.

[jamesn123]

@me0879 

Looking at the example screenshots you posted from the demostration router it looks like they are telling you to map public port 443 to private port 8123. This is not possible on the Sky hub as it does not support port translation.