It works. U upgraded my HA first to 0.89.1 and downloaded and edited the ftahoma component files from the 0.89.1 release.
After a reboot I can see the thermis sensor in HA.
Thanks.
Hey, I’ve been playing around with the tahoma component as the somfy one is not working for me. I’ve added some functionalities like temperature and humidity sensors from the smart thermostat and temperature from the io sensor, rts switch, and lock control. Be advised that the lock is submitted to the same limitation as in the tahoma app, that is, the state does not reflect the actual state of the lock but the last action done through the app. The implementation is not clean enough to be submitted to HA as an update, but you can find it under the custom_components in my repo: https://github.com/vlebourl/home-assistant-config
If any one finds a solution to get the actual state of the lock, I’d be more than happy. I’d be happy to include any development from the community if ever other people are willing to work on this component.
Cheers
Hi,
could anyone give a short explanation where __init__.py and sensor.py are located respectively where these files have to be placed.
I am on raspberry pi with a manual installation of HA into a virtual environment.
Thanks,
Jan
got it
pi@raspberrypi:/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tahoma $ ls
binary_sensor.py __init__.py __pycache__ sensor.py
cover.py manifest.json scene.py switch.py
Hi,
I added a custom integration to HACS to add functionalities to the tahoma integration.
Have a look here: https://github.com/vlebourl/tahoma_extended.
More could be added but I don’t own them, which make the integration difficult. Please PM me if you want another device integrated.
V.
Hi!
I miss the io smoke detector as written here.
https://community.home-assistant.io/t/somfy-missing-io-smoke-detector/172671
Maybe someone can help me?
Many thanks in advance
URBANsUNITED
I can try to add it to the custom comp. Can you check your logs and past the line looking like this?
2020-02-18 11:05:32 WARNING (SyncWorker_12) [homeassistant.components.tahoma] Unsupported type io:AtlanticElectricalHeaterIOComponent for Tahoma device xxx
Thanks for taking care…
Log:
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type io:SomfySmokeIOSystemSensor for Tahoma device Carlotta Rauchmelder
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type io:SomfySmokeIOSystemSensor for Tahoma device Madita Rauchmelder
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type io:SomfySmokeIOSystemSensor for Tahoma device Stube Rauchmelder
2020-02-18 06:32:54 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type enocean:TransceiverEnoceanComponent for Tahoma device ENOCEAN (84327663)
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type internal:TSKAlarmComponent for Tahoma device Alarm
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type internal:PodV2Component for Tahoma device Sensitive Taste
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:NodeComponent for Tahoma device ZWAVE (1#1)
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:TransceiverZWaveComponent for Tahoma device ZWAVE (1#2)
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:OnOffLightZWaveComponent for Tahoma device Beleuchtung vorne
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:OnOffLightZWaveComponent for Tahoma device Beleuchtung Dachschä
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:OnOffLightZWaveComponent for Tahoma device Steckdosen Terasse
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:OnOffLightZWaveComponent for Tahoma device Beleuchtung Terrasse
2020-02-18 06:32:58 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type zwave:OnOffLightZWaveComponent for Tahoma device Steckdosen vorne
2020-02-18 06:33:09 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform tahoma is taking over 10 seconds.
The Zwave part has been solved by swapping the Zwave stick from Tahoma box to my Raspberry.
All Zwave items nicely recognized !
Thanks
URBANsUNITEDPreformatted text
Bonjour Vincent,
celui la est le moteur somfy pour le portail:
2020-02-21 23:59:55 WARNING (SyncWorker_19) [homeassistant.components.tahoma] Unsupported type rts:SlidingGateOpenerRTSComponent for Tahoma device Portail
celui la est un radiateur Atlantic IO:
2020-02-21 23:59:55 WARNING (SyncWorker_19) [homeassistant.components.tahoma] Unsupported type io:AtlanticElectricalHeaterWithAdjustableTemperatureSetpointIOComponent for Tahoma device Milo
tous les autres sont en lien avec ce radiateur:
détecteur de présence
température
energie consommée
comment puis je t’aider?
merci
We got a new terrace covering with Somfy io lamps and a Somfy io awning. Since the following two types are not (yet) available through the Somfy API, I would like to have these types in the Tahoma integration.
We have the following Somfy products:
- Lighting receiver Variation io
- Slim io receiver awning+plug
- Situo 5 io (control)
The Lighting receiver registers as io:DimmableLightIOComponent (dimmable light receiver, on/off and brightness)
The Slim io receiver awning+plug registers as io:AwningReceiverUnoIOComponent (horizontal cover)
Is it possible, to integrate them into the Tahoma integration?
Best regards
I will be working on adding the following devices in the coming weeks. Will let you know when you could test them. I think the DimmableLight requires some additional work since it can not be mapped to one of the supported types (switch?). I believe it has to be mapped to a light type.
io:DimmableLightIOComponent
io:SimpleBioclimaticPergolaIOComponent
The following components in my setup are not supported, however I am not sure if this is something that should be supported at all, since it is internal.
Unsupported type internal:TSKAlarmComponent for Tahoma device Alarm
Unsupported type internal:PodV2Component for Tahoma device Aanraakgevoelige knop
1 Like
That sounds great.
I have integrated the io:AwningReceiverUnoIOComponent with a custom_component to test and fix some problems for myself. If this is stable I can try to make a pull request after your work is finish.
I exclude amongst other things the following internal types:
exclude: [
'internal:TSKAlarmComponent',
'internal:PodV2Component',
'myfox:SomfyProtectSecurityCameraController',
'myfox:LightController',
'myfox:SomfyProtectAlarmController',
]
Hi! Could you please add support for this one?:
‘’’ WARNING (SyncWorker_5) [homeassistant.components.tahoma] Unsupported type io:MicroModuleRollerShutterSomfyIOComponent for Tahoma device Guest Blackout’’’
Many thanks in advance!!
Hey there,
missing support for DimmableLightComponent was bugging me even using “official” API so I completed the tahoma_extended component from @vlebourl to support them (PR is https://github.com/vlebourl/tahoma_extended/pull/3), or the tree where you can use this is https://github.com/CedricGatay/tahoma_extended/tree/feat/dimmableLights
I hope it will help others !
Cheers
2 Likes
Just to clarify, the “MicroModuleRollerShutterSomfyIOComponent” is a small controller by Somfy that can be added on any motor (i.e. non smart motors) and make it IO compatible. Moreo or less it looks like this (not sure it is the same model, but it is the same functionality).
See below:
Maybe we could add it as if it were a “normal” smart motor and I can do the testing to see if it works (probably it will). Many thanks!! 
having these as unsupported
Unsupported type rts:SwingingShutterRTSComponent for Tahoma device Kannerzemmer
Unsupported type rts:HorizontalAwningRTSComponent for Tahoma device Markise
Unsupported type rts:SwingingShutterRTSComponent for Tahoma device Küche Vorne
Unsupported type rts:SwingingShutterRTSComponent for Tahoma device Küche Seite
Unsupported type rts:SwingingShutterRTSComponent for Tahoma device Schlofzemmer
any workaround to get them added as device?
Hey, sorry I haven’t been active for a while. I’m trying to catch up. At the moment, I’m making PRs to include extended features into the core component. When they are published, I’ll remove them from the extended version. In the meanwhile, I’ll not actively add new features to the extended version, but gracefully accept any contribution! Just make a PR and I’ll merge it for you to try it. Once cleaned up and verified, I’ll try to submit it to the core component.
I am now digging through the Tahoma component to add some more devices, but it looks like some parts could be rewritten to support all devices out of the box. Currently the component is using a hardcoded :io and :rts` device list, where you have to hardcode the sensor type.
For example, the following snippet can be retrieved through the Tahoma API. Based on the Widget and uiClass, the sensor type can be defined based on a list. This will allow the component to support all devices making use of those classes.
"controllableName": "io:SimpleBioclimaticPergolaIOComponent",
"widget": "BioclimaticPergola",
"uiClass": "Pergola"
For the BioclimaticPergola device that I am adding support for, the position should not be used. Instead the position_tilt should be used. From the API, you can receive the commands and states, which also allow you to understand which features the device supports, making the implementation more dynamic.
Any thoughts? Would be great to understand the choices of the current component, so I won’t be working on some improvements for nothing. 
@vlebourl @CedricGatay @philklei
Hey, as far as I’m concerned, every contributions are welcome, including your suggestions. Feel free to use the “extended” repo to test it. I’d be very happy if you were willing to have a look at the climate component. It’s working, but it’s not well written…
1 Like
Hi guys, as requested from another forum. I have a number of Somfy devices including a gate with an Axovia IO motor and a Control box 3S IO. Issue is that although these appear in HA through the Tahoma integration, they appear as scenes (replicating the scenarios of the Tahoma box). So I can trigger an “open gate” action but I cannot get the status change to trigger another action (like lights on) in HA. Even in the Tahoma app it seems you cannot use the gate status as a trigger. Same issue with Somfy IO movement and door status sensors. I looked at the API/Somfi integration but neither gates, nor movement/door status sensors seem to be exposed.