I have opened a request here (i hope it is on the right place)
The additional functions are described there (in addition to existing functions that already allow us to get the local temperature and other technical data)
Thanks to tell me what i should do from there
Best would be an issue on GitHub, including your diagnostics information.
Done
Last time I was searching for some wireless scene switches which could replace my Somfy Smoove IO wall units. I had found this Moes switch:
The problem with this switch is that it is not very fast with sending the zigbee command. Also I read a lot of stories that the batteries are drained very fast (2 months).
Because I have everywhere Hue Lights in my house I thought maybee the Hue Dimmer Switches are an option.
So I have replaced 2 Somfy Smoove IO units for 2 Hue Dimmer Switches V2 for testing the coming days.
To use the KIS (keep it simple) principle 
I still have to place labels on the hue buttons. For now I have created the next functions to the buttons:
I have to say that it works quite nice. There is offcourse some lag. This will be improced with a local api. Also iām going to change my microcontroller to a version with ethernet instead of wifi.
When everything stays working perfect, I will change all my Somfy smoove IO units by those Hue dimmers.
Pros:
Neg:
But when somebody knows another wireless switch, Iām still interested. At this moment I donāt have buy all the other switches that I āhaveā to replace.
@imick Hi, I have a question: With the Overkiz Cloud Integration, I can also see lamps that have been integrated into Tahoma Switch via philps Hue and Somfy Protect. with the local developer API integration, these lamps are no longer retrieved. would it be possible to get the bulbs from the Local Developer API as well?
Thanks for an answer.
Hi, sadly the local api as implemented by Somfy/Overkiz is just a subset or their cloud version.
Itās why all the devices are not returned when you switch to the local version. There is nothing we can do on our side.
But may I ask why you paired your Hue lights with the Tahoma? The Hue integration within HA is way more powerful and give instant feedback.
Hi, actually I also use the Hue integration in Home Assistant. Itās a basic question as I noticed the difference. There is also an MQTT integration for the Somfy Protect devices, but so far I have also gotten along well with the Overkiz Cloud Integration.
@Stylewarz3 which Somfy Protect devices do show up in your Overkiz cloud, but not in your Overkiz local? Can you share the hardware and model names? (you can find that on the device page in Home Assistant).
In the future; we will probably make it possible to use local and cloud API next to each other.
@imick of course:
The first device is not specific:
Modell:
Home Protect System
von Somfy
Firmware: 1
The second device:
Modell: MyFoxAlarmController
Hardware: myfox:SomfyProtectAlarmController
The third device:
Modell: MyFoxSecurityCamera
Hardware: myfox:SomfyProtectSecurityCameraController
With the MyFox Security Camera device, lights connected to the camera are also integrated as entities.
I made significant progress to integrate ValveHeatingTemperatureInterface, which corresponds to this somfy product
The first (and biggest) difficulty was to extract the overkiz integration built in home assistant from the core back in a custom component, (simply use the core source code, and adding a version is not working)
I have to admit i am quite new in Home assistant ecosystem and my python skills were quite limited. I used to be an embedded software engineer in the last century, but more used to develop in assembler, C/C++ and Java than on the kind of new languages where you discover issues when running itā¦
OK after some time i managed to build this development environment in my custom folder, taking this fork as the heart of the custom component GitHub - iMicknl/home-assistant-core at overkiz/local_support
When implementing the somfy device i started from pre integration work done few years ago and managed to at least be able to set a temperature on my valve. and it worked !
"""Support for ValveHeatingTemperatureInterface."""
import logging
from homeassistant.components.climate import ClimateEntity
from homeassistant.components.climate.const import (
HVAC_MODE_HEAT,
SUPPORT_PRESET_MODE,
SUPPORT_TARGET_TEMPERATURE,
)
from homeassistant.const import ATTR_TEMPERATURE, TEMP_CELSIUS
from ..entity import OverkizEntity
_LOGGER = logging.getLogger(__name__)
# Map Overkiz HVAC States to Home Assistant HVAC states
OVERKIZ_TO_HVAC_STATES = {
"open": "heating",
"closed": "idle",
}
HVAC_STATES_TO_OVERKIZ = {v: k for k, v in OVERKIZ_TO_HVAC_STATES.items()}
# Map Home Assistant presets to TaHoma presets
PRESET_MODE_TO_OVERKIZ = {
"away": "awayMode",
"comfort": "comfort",
"eco": "eco",
"frostprotection": "frostprotection",
"geofencing": "geofencingMode",
"manual": "manual",
"suddenDrop": "suddenDropMode",
}
OVERKIZ_TO_PRESET_MODE = {v: k for k, v in PRESET_MODE_TO_OVERKIZ.items()}
class ValveHeatingTemperatureInterface(OverkizEntity, ClimateEntity):
"""Representation of Valve Heating Temperature Interface device."""
_attr_hvac_mode = HVAC_MODE_HEAT
_attr_hvac_modes = [HVAC_MODE_HEAT]
_attr_preset_modes = [*PRESET_MODE_TO_OVERKIZ]
_attr_supported_features = SUPPORT_PRESET_MODE | SUPPORT_TARGET_TEMPERATURE
_attr_temperature_unit = TEMP_CELSIUS
@property
def hvac_action(self) -> None:
"""Return the valvestate and transpose in Climate state."""
return OVERKIZ_TO_HVAC_STATES[self.executor.select_state("core:OpenClosedValveState")]
@property
def target_temperature(self) -> None:
"""Return the temperature."""
return self.executor.select_state("core:TargetTemperatureState")
@property
def current_temperature(self):
"""TO DO Return current temperature from sensor - not working for the momment"""
return self.executor.select_state("core:TemperatureState")
async def async_set_temperature(self, **kwargs) -> None:
"""Set new temperature."""
temperature = kwargs.get(ATTR_TEMPERATURE)
await self.executor.async_execute_command("setDerogation",float(temperature),"further_notice")
async def async_set_hvac_mode(self, hvac_mode: str) -> None:
"""Set new target hvac mode."""
# TODO
return
@property
def preset_mode(self) -> str:
"""Return the current preset mode, e.g., home, away, temp."""
return OVERKIZ_TO_PRESET_MODE[
self.executor.select_state("io:DerogationHeatingModeState")
]
async def async_set_preset_mode(self, preset_mode: str) -> None:
"""Set new preset mode."""
await self.executor.async_execute_command(
"setDerogation", PRESET_MODE_TO_OVERKIZ[preset_mode]
)
So i am the most happy man on earth as i can already pilot my valve using HA environment and not anymore the Somfy one
But now i want to go beyond
they have the same URL but with #1 and #2 at the end of the URL
I wish to merge them or at least to copy the current temperature from #2 in the #1
I will continue to improve the integration (management of the io:OpenWindowDetectedTargetTemperatureState function for instance) and ready to share work in teams if some of you share the same goal
I wish also to better integrate my tahoma switch component (device internal:PodV3Component, device internal:WifiComponent, io:StackComponentā¦) if anyone interested to work togetherā¦
Hello Stylewarz
My Understanding is that Somfy protect is not handled physically by your somfy box (Tahoma or Tahoma switch) locally.
It is integrated in the cloud, together with your box installation by Somfy making it visible with the same API. (thus a HA cloud API integration implement both your box and the somfy protect services)
Reason why you do not see it if you implement local
My recommendation (that i did in my installation) would be to integrate somfy protect locally using Homekit (for the flow part, the lightā¦)
and using MQTT (for the configuration part - using SomfyProtect2MQTT add on ) as it implement most of the configuration available in the somfy protect app itself but is not implementing the real flow of the camera (only snapshot)
I made a card to fully use what I developped
it is using simple-thermostat from HACS
type: custom:simple-thermostat
entity: climate.vanne_e1_salon #THE NAME OF YOUR VALVE DEVICE
layout:
mode:
icons: true
headings: false
hide:
temperature: true
sensors:
- entity: sensor.vanne_e1_salon_vanne_e1_salon_temperature #THE NAME OF YOUR SENSOR
name: Currently
Hey @legantois dont put more work into it as imick commited an integration for the valve in github. In one of the comming updates (when it is all done and approved for) it should be supported by core.
Maybe you want to contact them to join them in integrating stuff as you seem very capable and enthusiastic 
Sadly I am only enthusiastic but not capable as I cant code stuff and fail at simply yaml code 
We are in contact, no worries.
You can still help. What kind of bridge do you have ?
I have the (now older) tahoma box (not the tahoma switch).
And I got plenty of zip-shades from Somfy, Io thermostats, Io smoke detectors etc.
And the zigbee usb stick in the tahoma box to control the Danfoss Thermostats.
I plan to remove the heating control from the tahoma box and to control them over Z-Wave.
Except the Io ones as they only can be controlled by the tahoma integration.
I actually worked on @linuxstony his account to develop the integration :). So both of you did help in a way to get your device supported in HA. It is merged in and will ship next update.
Iāve recently gotten my hands on a Somfy Connection Kit, which is basically the TaHomaās little brother which works with the same Somfy TaHoma app. It works great with the Overkiz integration in general, but I just noticed that there is no entity for a low speed cover position change in HA. The TaHoma app does show the ādiscreetā option for my compatible covers (RS 100 IO) though.
Is this option currently not available? Thereās not much to configure in the Overkiz integration, do I have to add some additional config?
For the low speed mode, you should normally see two covers within your cover device. One is the normal mode and the second one, the silent/slow mode.
Thatās what I expected, but only the standard cover entity shows up. āRolluik SK1ā should have the slow speed mode available. It shows up in the TaHoma app and works like a charm.
This is the whole Overkiz integration:
And these are the only entities it generates:
@bham86 could you create an issue on core GitHub so we can investigate? Please include your diagnostics information for the device where it isnāt working.
