Improved api performance with port forwarding

A while ago I made my own Homey dashboard (I know about the existing Homey dashboard). Because the api performance with Homey cloud gives varying performance, and my Dashboard app can’t handle local addresses, I think the solution could be via Port forwarding.

However, I can’t make a connection with Homey via Port forwarding. What have I already done/tried:

  • fixed IP address for Homey

  • port forwarding enabled in modem


  • firewall authorized for the default Homey port 4859

  • Configured port forwarding in Homey, with a message that it is active when saving this; the operation of port forwarding is checked when activating.

  • requested my IP address with Whatismyip.com.

  • created an Api key in Homey

  • with Postman I request the following with GET: https://[ip-address-from-Whatismyip.com]:4859/api/manager/devices/device. I also set the Bearer Token with value: Bearer [api key]

Postman response: Could not get response.

Does anyone have any suggestions to make this work? (I’m not a network hero)

2 Likes

In your firewall local port shall be 443 and external port shall be 4895

1 Like

https://support.homey.app/hc/en-us/articles/16397583238556-Enabling-Port-Forwarding

1 Like

Even after a compete firewall deactivation I get the error in Postman: Could not get response:
Error: write EPROTO 1071616:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:........\src\third_party\boringssl\src\ssl\tls_record.cc:592:SSL alert number 40

Using KPN Box 10 modem (fiber). Any suggestions I could try?

You cannot access Homey using your (external) IP address because TLS/SSL certificates are bound to domain names.

You can try accessing it via this URL:

https://AA-BB-CC-DD.homey.homeylocal.com:4859/api/manager/devices/device

Where AA/BB/CC/DD are the octets of your external IP address (in other words, if your external IP address is 12.34.56.78, the URL becomes https://12-34-56-78.homey.homeylocal.com...)

1 Like