Wow that’s great news. But unfortunately I don’t see the connexoon in the list, so that one is not supported?
1 Like
Unfortunately not. Perhaps you could contact Somfy support to ask if they plan to add this in the future.
wow, this is pretty amazing Mick, let us know if we can test drive 
btw, would this also mean we get real time updates on the position of our covers? the 30 sec delay we now e sure must be one of the most obvious ‘issues’ of the current cloud solution.
#fingerscrossed…
Just chiming in, but maybe we could support this hack?
1 Like
Just did it: Connexoon support · Issue #9 · Somfy-Developer/Somfy-TaHoma-Developer-Mode · GitHub
Now fingers crossed…
It is a pity that Connexoon is not supported, perhaps the solution from @dmaasland can be extended to use the new Developer Mode. This would also help to make it easier to get this supported in HA core eventually, since the root is slightly different than the new local ‘developer mode’.
1 Like
Cool! I will definitely check it out when I have a minute.
I tried to understand the API documentation on the somfy developer github, but it didn’t say, which somfy devices are supported. Can you tell, if even sensors are supported (such as illumination, temperature, opening) or only actuators (cover, power sockets etc.)?
Ok so I updated my box to the latest firmware version and re-rooted it (which involved some new steps as public key authentication is now required).
Turns out the new developer mode works on the Connexoon as well as long as you enable the local API. There are some manual adjustments you need to make though to get everything running smoothly, mainly because the connexoon does not have the SSL certificates needed to start the “devmodesocket” out of the box.
I’ll share some more details once I understand more about how it works :).
6 Likes
Long story short, almost everything works out of the box if you update your Connexoon to the new firmware and repeat the rooting process. The only thing that’s missing are the SSL certificates for the local webserver.
Furthermore, the new firmware has some changes regarding partition size and SSH password login. I’ve documented the changes on my blog: No clouds, just sunshine. Disconnecting Somfy Connexoon from the cloud. - Unauthorized Access Blog.
1 Like
Awesome work, @dmaasland! I hoped to have local support in the upcoming HA version (in May), but I am afraid that this will be in June due to a bug on Somfy’s side. ( Cannot register (local) event listener · Issue #4 · Somfy-Developer/Somfy-TaHoma-Developer-Mode (github.com)).
I have a proof of concept working with Overkiz in core, now we just need to polish the code over the next months and I will have a look if we can support jailbroken Connexoon as well! 
2 Likes
I know it’s been a while, but today I was forced to change from somf to overkiz and it comes to me much faster. Does this integration work outside the cloud, directly over the LAN?
Glad you made the switch. The official api was a shame.
The Overkiz integration still does cloud polling as explained in the documentation.
But Somfy finally exposed a local API (see previous messages) and well will update the component to use it.
1 Like
I have an issue where it seems to time out after 24hrs etc. It works fine and accepts my password and I can see and control the entities, but after approx 24hrs the Integration says attention and no longer works, I re-enter my somfy password and it goes back to a working state. Obviously having to manually do this every 24hrs makes this unusable. I am connecting to the Oceania region, any ideas?
Check your logs and see how often its polling. I’m having issues with a bug that makes it poll once per minute, and I’m getting banned constantly. The ban at this stage has only been as much as half hour, but its enough to trigger the reauth once a day (like what you are having). I am also Oceania.
This is what is mentioned in the log:
Logger: homeassistant.components.overkiz
Source: helpers/update_coordinator.py:231
Integration: Overkiz (by Somfy) (documentation, issues)
First occurred: May 5, 2022, 2:00:28 PM (1 occurrences)
Last logged: May 5, 2022, 2:00:28 PM
Authentication failed while fetching device events data: Invalid authentication.
Thats just the failed auth error itself, I get these every ~60 seconds,
2022-05-05 13:19:33 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.0s (pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated)
There was an update for the TaHoma box 2dayz ago. Will that do the trick to have a local support by Overkiz?
Yes, local support was already there but still had a critical bug. This bug has been fixed and we can now start to integrate this.
However, our time is currently quite limited, thus it can take a while. There is a very early alpha version available on GitHub (GitHub - iMicknl/home-assistant-core at overkiz/local_support), however this will require knowledge how to run a core development instance.
You can follow our development in that branch.
1 Like
Thanks for the reply, I will have a look at the alpha, however, I probably rather wait until you implemented it. I am not that good in HA.
So take your time, as long as I know it’s in the pipeline, I am happy. I‘ll be patient, I am happy that there are people out there doing all this coding