Overkiz stopped working after power failure

Third party integrations
1

I have be using the Overkiz integration together with the somfy Tahoma box for some time now and up till now it worked perfectly.
A few day’s ago we had a power failure and after resoring the power the overkiz integration stopped working.
When I restart HA and go to the overkiz in the integrations I can see: failed to connect.
When I use the Tahoma app on my phone I can control all (4) of the shutters.

image
image998×321 23.9 KB

What could be wrong and how do I correct it?

2

Hello Frank Weijnen,

Did you reserve an IP address in your router for the device when you set it up?
I’m thinking the power reset changed some IP addresses…

3

Hi Sir_Goodenough,

Yes, I have a IP reservation for the box in my Router.
When I ping the Tahoma box at address I assgined in the router, I get a response so that seems to work.

When I use the TaHoma app on my phone, I can connect to the box and control all screens. I entered the password I use to setup the box so the password is ok.

I also checked the pin number of the box. That also matches.

4

Can you access 192.168.2.51:8443 in your browser? Most likely the port is closed after your power failure. Port 8443 closed after reboot · Issue #139 · Somfy-Developer/Somfy-TaHoma-Developer-Mode.

The TaHoma app on your phone uses the cloud API, thus you can’t compare this.

5

Hi Mick,

I can’t access 192.168.2.15:8443 in my browser.
(Do I have to add http:// in front of the IP address?)

I reset my box and had to setup wifi again but after that still no connection to the box.

What else can I do?

Frank.

6

I got it working again. :slightly_smiling_face:

here is what I did:

  • I shutdown HA completely.
  • Closed HA on all tablets.
  • Unpluged the TaHoma box from the mains.
  • Waited about half an hour.
  • Pluged-in the TaHoma box and waited until the light turned white.
  • Started HA

After HA was started I tested the box in HA and all my screens are working again.

Thanks for the help.

2 Likes
7

Hi, I had similar problem - REBOOTING HA seemed to sort out the issue (not a normal restart), must be the FULL reboot.

8

@rohangopal what error did you have in your logs? It should auto recover actually, no need to reboot HA.
Or did this happen after the time change? This is actually not an issue in Home Assistant, but an issue of your hub…