Somfy Tahoma Switch no longer accessible via Homekit integration

Configuration
1

Hi all,

I’ve had my somfy tahoma Switch box integrated with overkiz (cloud) and HomeKit (local) for like a year.

Now the local access does not work anymore and I cannot see why this would be the case.

It seems to have stopped working Monday, as can be seen from this entity’s availability:

1000048067
10000480671080×933 67.4 KB

I tried reloading the integration, restarted HA, installed current version of HA.

Overkiz works fine.

Checked somfy website - Dev access still enabled (not sure if required for homekit).

I did a port scan of the port reported by the integration error message:

1000048068
10000480681080×420 39.1 KB

Nmap says it’s closed, so maybe/probably not an error on HA side.

Any idea how that might come? I found nothing on Google regarding port and somfy, so out of ideas what to do. Can someone else do a port scan of this is normal?

2

Can you connect to 192.168.1.107:8443 in your browser?

1 Like
3

Hi,

I double checked the ip address in opnsense and it is correct:

1000048276
10000482761080×719 34.2 KB

Access to port 8443 is blocked:

1000048277
10000482771080×1169 69.1 KB

What could I have done wrong to disable that port? :cry::cry:

I googled a bit and found this, eg Port 8443 closed after reboot · Issue #139 · Somfy-Developer/Somfy-TaHoma-Developer-Mode · GitHub

Seems a common issue. I will dig into this when the kids sleep tonight.

1 Like
4

Another restart has helped … the fifth one … This Somfy environment is just the worst you can imagine 2025. I will set Uptime Kuma to monitor port 8443 and restart the box if it is down.

1 Like
5

Same problem here. It is almost exactly 1h after the last request made (automatically opening one shade in the morning). I’ll probably add a smart socket to reset it…

1 Like