Do you know if you control your motor with a control unit (for example a smoove) if the positions are directly updated in Home Assistant?
The control unit talks directly with the motor with the IO protocol.So when your Home Assistant is directly updated with the correct positions then the Tahoma box is updating itself every second.
I have smoove io remotes in most rooms - updates are coming through thick and fast into HA - for example, when you press āupā on the smoove remote, HA (HomeKit-Controller) will report the cover state āopeningā quite fast. Its not instant but absolutely okey for me.
Okay and where are we talking about? Are it minutes of just some seconds?
With Homekit Controller itās a matter of 1 or 2 seconds.
Okay that is really fast 
.
How reliable is it? 100%?
I have moved to HomeKit-Controller and I donāt regret it at all. I have to admit I currently use the Velux integration with a KLF-200 too, to control tilt.
The Overkiz integration is a great integration, unfortunately the Somfy API is very unreliable from time to time, which is no good for the WAF! 
And it was frustrating for me too.
What Iāve seen so far, the HomeKit-Controller is very reliable, I did not have a single outage since I moved, which is a couple of weeks now.
When you change the state of one cover, its 1-2 seconds as already mentioned. I found though when you update one cover many times in a short period of time (I did this only for test-purposes, it takes a little longer (still seconds) to report the correct state of the cover. This is not a real-life scenario though, at least at my end.
The good news is: you can use Overkiz and HomeKit controller in parallel, so you can test it and still have Overkiz in place. Then, when satisfied, you can move entirely.
BTW, the tilt issue from the HomeKit-Controller integration is already being looked at on github. As soon this is solved, I can get rid of the Velux KLF-200 too 
Sounds good, The problem I have is that I have Somfy RS100 IO motors which has 2 speed modes to operate (normal and discrete mode).
Unfortunately HomeKit doesnāt support the discrete mode.
My hope was that one day the Velux KLF200 was the replacement for my Tahoma. But iām happy to hear now instead of after I buy one, that it is not reliable. So I skip this from my buy list.
Using both integrations: HomeKit Controller and Overkiz is for me no problem. But I donāt think that will work for the discrete mode.
@tetienne : Setting the discrete mode with the Overkiz and then moving the cover up and down with the HomeKit controller doesnāt work I guess?
@tetienne: The stop cover functionality was a few months ago not supported by Somfy with the HomeKit Controller. Does Somfy updated in the meantime there HomeKit support in the Tahoma V2 and Switch?
right, so I updated to todays dev and not sure if this was there before that (didnt check) but None of my devices are showing in the devices list of the Custom integration. All entities are thereā¦
so far so good:
clicking the 11devicesā¦ huh ?
@Mariusthvdb, please create an issue on GitHub, this is not the place for support like this.
And we probably donāt have time to support this issue as well, since we are working on rewriting the integration for the core PRās. If you use the latest dev build (not even beta!), some things can be broken and it doesnāt need to be related to our integration.
understood, and its not Tahoma aloneā¦ No devices displayed in device panel coming from config/integrations Ā· Issue #63160 Ā· home-assistant/core Ā· GitHub
so this is really playing up again, 3d time todayā¦:
and I know you are aware of it, even contacted Somfy on it and waiting for reply.
What I dont get, is how it can be even considered moving in to core with this huge issue. I would think core integrations need to be fully robust, and weāve seen integrations being taken out for things like this.
I couldnāt post this in the HA Core GitHub, since its more of a concern than a bug (though running HA dev, I havent installed the dev Overkiz integration and still are running the Custom integration)
same issue.
when will it be fixed ?
thx
@Mariusthvdb, I donāt even own any Somfy device myself. I just started this project (with @tetienne and @vlebourl) because my parents have a Somfy hub. We spend a lot of time working on this and indeed, lately Somfy had quite some issues.
However, you would be the main reason to just drop working on this. You are constantly bugging me (and others, looking at your replies) without any constructive feedback. If you want it removed from core, fine. I remove it, but donāt expect it ever to come back.
Just my 2 cents.
Oh and by the way, we do this fully voluntarily and unpaid (zero donations). So think about that as well before you create many issues, where many are even related to running unsupported dev builds. Our time is not free.
right. wow. this is so out of proportion. Calling me a
??
first off: me running dev build has nothing to do with it. On the contrary, I would think you are also, and since dev build is only a month away (ahead of) from release, it isnāt a build you can ignore. Even so, this issue is also happening in release, so the point is moot altogether.
itās not me bugging you (or anyone else for that matter). I am simply reporting and returning feedback from the state the integration is in.
I am always glad someone reports issues on my work, and see it as a chance to improve. A gift really.
Having said all of that, I sincerely hope you donāt drop the work on the integration at all, what on earth would have given you that idea. the integration is an essential part of my config!
Its just that this most annoying of issues from Somfy is rather basic for the proper workings of it.
Iām sorry you didnāt like @imick 's answer to you. But to be fair, since you started reporting issues, we felt kinda spammed by the volume of messages recieved (we get notified of every single comment posted, issue opened, answer on either the forum or the github). No offense intended, just an honest opinion.
Regarding this reconfigure issue, we are perfectly aware of itā¦ obviouslyā¦ A thread is opened on the github, as long as itās not closed by us with an answer, you can consider we are still working on it, and donāt need to repost every now and then to āupdateā us that itās still an issueā¦ We are sorry it takes so long, but we canāt be held responsible for Somfy not answering our questions.
As for running dev builds, Iām sorry but I have to agree with @imick. On github, the main branch is only for development purposes. Releases are made when the main branch is considered stable enough in regard to the released version of Home Assistant at the time, not the dev version. Issues are then most welcomed concerning those releases. Using dev version of Home Assistant or any other version of our integration than a release (unless explicitly asked by us for testing purposes) is at your own risk and is not and wonāt ever be supported by us. Donāt feel offended by this either, once again, none are intended. But thatās the only way we can try to tackle issues as they inevitably arise.
Finally, we are more the happy to review PRs from anyone who would like to give us a hand! If you feel we are not going fast enough, feel free to take a closer look and provide us with your solution!
Letās keep this thread a happy place, cheers and happy new year!
(and mean was a typo, itās been edited!)
cool, never mind the āmeanāā¦
and this is not about me running dev and the CC not being supported on that. I know, and appreciate, you are aware and are working on that. I stated as much I my post above. My post was not a āreminderā either. I know how GitHub works.
We all know this has nothing to do with dev or release, but has to do with Somfy being flakey about the external authorization.
What you donāt seem to address is my concern about transitioning a CC to core, while there is such a fundamental issue with the service provider.
As said, this is an essential integration in my HA setup, so I definitely hope it will be integrated into core. I fear though the the issue with Somfy might frustrate that. And, because I had not seen any discussion on that particular matter, I posted above.
Just look at your replies in Issue #665 and Pull Request #667. We appreciate feedback, but this was one of the occasions where I found it too pushy. Your other question around devices missing (which was a core bug) cost us time to investigate and are not related, thatās what I meant.
I didnāt address this because I already took precautions in core, to not have this āreauthā problem. We keep retrying until there is a definitive fix, just as I fixed for the custom component 17 days ago.
Also, I donāt see why (and where) I need to announce that I fixed a bug in core. You could always have asked me in a nice way, instead of how you have phrased it above.
Letās just rest it for now, and get back on-topic. No hard feelings, however I just wanted to share our feelings, since it was bothering us for a while.
For everyone looking for a (temporary) solution for the reauth issues, please have a look at At least one of your integrations requires reconfiguration to continue functioning. Ā· Issue #599 Ā· iMicknl/ha-tahoma Ā· GitHub.
really sorry, but again you point fingers at me, and then you tell me to stopā¦
Tbh, if I read the links you show as an example, thereās no clue as to why you would have lost any time, or even be bothered at all. I am polite as ever. Yet you say I am āpushyā, or āshould have asked nicelyāā¦?
Regarding the missing devices issue: it was merely a first discovery of an issue lying elsewhere. You might have missed it, but I took some time myself to do No devices listed in device panel Ā· Issue #11068 Ā· home-assistant/frontend Ā· GitHub and find the solution tooā¦
now stop feeling so hurt all the time.
And yes, I did see and try the (temporary) solution you mention. Call me a hardliner, but I donāt think that is a solution. Though I appreciate the effort you made and bent over backwards to help the community here, I donāt like to wait a day or so for my devices to get back online. Especially when a mere restart fixes the current situation.
I wont post bug reports on the release version (or the dev version) anymore.
thanks for your time you spend for the community.
You are right, it is fair to give you a chance to respond. Letās close it now and get back on topic regarding the Overkiz integration.
