Overkiz integration - Local API [Development / Testers topic]

283

I see, will do so if required. An exciting day, this santa clause day :santa::wink:

284

Itā€™s great to see this finally in core, Iā€™ve set the local integration up on my test instance but unfortunately as far as delay goes, itā€™s actually worse than the cloud setup (which I still have on my prod system, controlling the same tahoma switch),.

More specifically, when I use the local integration to turn on my pergola lights, the lights do come on within ~1 second however then it takes about half a minute for the state of the HA entity to actually reflect the status, i.e. for the switch to turn on (the same thing happens when I turn them off). With the cloud integration thereā€™s also a delay but much shorter, typically <5s. (again for the state to be reflected in HA, NOT for the actual lights to come on)

Interestingly enough, when I turn the lights on using the local integration, the cloud entity in HA reacts quicker and changes state well before the local one does although it seems slower than when you actually initiate the state change using the cloud integrationā€¦

Iā€™ve only tested the lights so far, I will test screens tomorrow to see if those work as expected.

285

Please turn on debug logging and create an issue on GitHub. A possible issue here is that the events are not in order, hence the API is not polling every second, which is hard to fix. We normally poll every second after an execution, until the execution is registered, than we move back to 30 seconds.

To clarify, in your case execution is instant, but state updates are slower.

286
  • @iMicknl added local API support for the Somfy TaHoma to the Overkiz integration! Also, thanks Somfy! Itā€™s nice to see a manufacturer adding local API support!

Now in the official release :slight_smile:
Congrats Imick

287

Issue created, the delay is exactly 30s between the command and the state change

288

How do you get your Somfy devices into HomeKit @fair_dinkum ?

289

See Overkiz - Home Assistant (home-assistant.io).

290

@Sddawson (off topic and FYI): that Homekit integration is awesome and super reliable, however the tilt attribute is not reporting the current state properly. There is an issue created on github already but not fixed yet

291

Hey,

Thank you very much for this evolution, this looks awesome !

Is there a way to use local API for covers but still have the climate devices through cloud ?

Somfy is the only way to access my heatpump so i canā€™t lose it from this integration.

292

@imick awesome, what a good job thanks.

293

Not at the moment. This would require more efforts (because they share the same ids), and thus I havenā€™t focused on this due to my time constraints. My hope is still that Somfy will include climate devices into the local API.

294

What piece of kit supports a Homekit integration?

295

Yeah understandable.
Letā€™s hope so but with Somfy this could take a very long timeā€¦

Thanks for the answer !

296

There is a link to a PDF on the Overkiz integrations page, section Homekit (its mainly shutter motors)

1 Like
297

Hello Mick

Cannot use the local Version

image
image856Ɨ344 25.4 KB

i did reboot HA, the switchā€¦ nothing works

very strange as i was able to connect on the PR version

Leg

298

When you use the ip address I thought you have to uncheck the checkbox of the certificate.

299

I managed to make it work by unchecking the SSL box using the PIN code version

should be better documented :grin: to avoid post install support

ā†’ whatsoever the Local API is still not able to manage asynchronous / batteries device such as Thermostatic valves (it still needs clould treatment) so i come back to the cloud version. Full behavior described here Overkiz integration - Local API [Development / Testers topic] - #201 by legantois

cheers

Leg

300

Thanks for the feedback. What would be your suggestion to make it more clear? We tried linking the issue/solution with an error that says ā€œCertificate verify failedā€ and having a button with ā€œVerify certificateā€. Open for suggestions how to document this better.

The IP option is mainly for people that have a very complex networking setup and/or people where the MDNS (gateway-xxxx-xxxx-xxxx.local) cannot be resolved. Unfortunately for direct IP connections, we cannot verify the SSL certificate.

Indeed, that is a pity and a limitation on the local API. In the future we hope to support local and cloud at the same time, but that is quite some work, so for the initial release we didnā€™t focus on this.
I donā€™t see this happening any time soon to be honest. We can have a look via Discord to a quick hack on how to enable this, but this wonā€™t be supported by us, and is likely to cause some other minor problems.

301

Hello Mick

I use the gateway-xxxx-xxxx-xxxx.local option to declare my somfy switch not the IP mode, but I had to uncheck the SSL box option. otherwise the configuration stoppped and ā€˜cannot connect to host, certificate verify failedā€™ error was showing up.

so i am a little confused as i understand from you that normally this error should be displayed when using IPĀØdeclaration of the box.

Do i understand well ?

302

Which hub do you have and is it up to date? Previously Somfy did use the wrong certificate on their hubs, hence we couldnā€™t verify the certificate.

Donā€™t having certificate verification is no big deal though, since it is a device in your local network you should trust :wink: . It is just best practice to verify the certificate, thus we do this.