Hi,
At the moment, support is quite limited in somfy’s official API. But you can have a look at this one for larger support: Tahoma Integration Refactored
Cheers
V.
Thanks, I will have a look at this Tahoma component.
Cheers,
Christophe
Hi,
Many thanks, I have finally succeeded in installing the Tahoma custom component (not so straightforward for a new user of HA 
).
I have almost all my Somfy devices, but the climates, a remote and the tahoma button are missing, did I miss something ? Should they be manually declared ?:
Best would be to discuss this in the Somfy TaHoma integration topic, to keep the discussion here about the Somfy integration via the official API. The readme offers guidance on how to approach devices that are currently not working yet.
Hey, this integration no longer works for me after updating to the latest version 1.10.1 (connexoon rts Australia). I get an Auth error 
1 Like
I guess you are using the Somfy TaHoma integration and not the Somfy integration from core?
If true, please continue the discussion in the right topic Tahoma Integration Refactored - Share your Projects! / Custom Components - Home Assistant Community (home-assistant.io). I did create an issue on GitHub, feel free to add your context there as well.
Sorry, it’s working, I had a senior moment and wasn’t picking the right hub when logging on. Thanks for your great work 
Don’t forget to change your interval to a high interval (like a month) via the options. This is something we should do by default in a new version.
Hi,
I tried on my tahoma box with the homeKit pin code from tahoma custom components (as I don’t have this code on the box).
I never paired this tahoma with anything before this attempt, but I have the same error (M5: not an error or a proof).
I tried to reset it with the RST hole on the box, but I get the same result. I don’t have an iphone (nor an apple account), so I can’t try the instruction given at the end of this thread.
Did you succeed to pair your box ?
hi, though I did a search, I didn’t find the exact issue I am facing: the official Somfy integration sees all my IO roller shutters, but doesn’t see my IO garage door.
Is this a bug, or a ‘feature’ 
The CC https://github.com/iMicknl/ha-tahoma sees the garage door fine, as I have installed it on my experimental system. Production system uses core only for now, so please let me know if I can find a way to see the garage door there too?
thanks
This, unfortunately, is a feature. The official Somfy API only supports a few devices, thus there are no options to add these devices.
The Somfy Tahoma integration uses their internal API, which means that all devices are supported. We are in the progress of adding this integration to core, but in the meantime you would need to use the custom component.
1 Like
ok thanks Mick, good to now. CC is working just nicely!
Any idea when this will be merged into core?
Second big diffenrence I notice, is the updating of the CC is much more responsive than the current core integration? Taking a long time for the position to be updated using core, while the CC is quite swift. Though only for 0% and 100%, it doesn’t update while opening/closing?
now that I have you here: what does the alarm_control_panel.alarm do in the CC config? I dont have a Somfy alarm, and yet this device and entity was created.
Unfortunately, I wasn’t able to pair the TaHoma Box with homeassistant via homekit controller. Even after the latest Somfy Update, it still doesn’t work.
This still could take months, since there is a huge backlog of contributions on core. For now I would just use the custom component and watch the changelogs 
.
This is correct, their official API is very limited, thus the experience with their internal API could be significant better.
This is disabled by default, since many users don’t use a Somfy alarm panel. However, there is no way for us to understand if Somfy Protect is enabled or disabled unfortunately. This is the reason why it is included, but not activated.
I am afraid that this won’t work soon. We are not sure if this is a limitation in the homekit_controller implementation in Home Assistant or if this problem is on the Somfy implementation.
Cool, thanks! Any chance of the CC being able to update ‘live’ while opening/closing? Ive made an automation and template sensor for my Ikea cover doing so, and would have hoped the Somfy integration to have that built-in…
cover_stookhok_position:
friendly_name: Stookhok position
value_template: >
{% set position = state_attr('cover.raamverduistering_stookhok','current_position') %}
{% set state = states('input_select.raamverduistering_stookhok') %}
{% if state == 'Stationary' %} {{state}} at {{position|int}} %
{% else %} {{state}}
{% endif %}
automation:
alias: Cover stookhok
trigger:
platform: state
entity_id: cover.raamverduistering_stookhok
condition:
>
{{trigger.to_state.attributes.current_position !=
trigger.from_state.attributes.current_position}}
mode: restart
max: 35
action:
service: script.raamverduistering_stookhok
data:
old: '{{trigger.from_state.attributes.current_position}}'
new: '{{trigger.to_state.attributes.current_position}}'
I have a question to @imick and @tetienne: What about combining the official Somfy API and the Somfy WebAPI into one component and providing the superset of features to the user. Whenever possible, you use the official API; if it fails or if the feature is not avialable, you fall back to the WebAPI. On one hand, that would make it more stable; on the other hand you would only have one set of Somfy components in HA instead of two sets of covers/shutters etc.
What do you think?
Feel free to create a feature request on GitHub (GitHub - iMicknl/ha-tahoma: Custom component for Home Assistant to interact with smart devices via Somfy TaHoma or other OverKiz based API's.). I am not sure how feasible this is though, we probably only receive the new position when the execution has been successfully executed.
Current behavior is that we show a different icon in the front-end, when a cover is in moving state.
I like the idea, but it isn’t feasible unfortunately. And even if it technically would be possible, it would make it a very complex integration and also hard to pinpoint where the issues are. For now, the official Somfy API is less stable and has less devices supported.
Their internal API based on the Overkiz platform is also used by other platforms (CozyTouch, Rexel, Hi-Kumo), thus a more logical next step would be to rebrand tahoma integration to the overkiz integration.
You could easily use both integrations next to each other, where you can disable duplicate entities.
Ok I will, but I’ll check first if the position is being updated while opening closing. The current core integration doesn’t do that as I have just been able to establish with the above automation and template sensor.
@imick sorry if this is the wrong thread, but after dl’ing the CC in the correct folder and restarting HA, I still cant see the integration and set it up…
Did a fine install on another system, so am confused now.
Do we need to reboot the host, or restart Home assistant (or restart core…)
the link is somewhat multi-interpretable:GitHub - iMicknl/ha-tahoma: Custom component for Home Assistant to interact with smart devices via Somfy TaHoma or other OverKiz based API's.
reboot Home Assistant
hmmm, even a host reboot doesnt reveal the Somfy TaHoma integration. Now what./…
update
a 3d restart made it happen… Tahoma integration loaded.
This is mainly due to front-end caching probably, only one restart of Home Assistant should be enough.