Aha ! After the firm has come to reset all, all is working again through HA
Now i’m keeping all, and never resetting the velux klf200 again 
See picture up how it looks in my HA dashboard.
Still looking for a more appropriate cover card
Also: anyone exposing to google assistant?
I can, but i was thinking if i shouldnt make scripts, so my screen and lamellen open at …% and close fully…
Any ideas about that?
I exposed my Velux roof Windows to google, allthough I just open/close them 
yeah i exposed it to google too, but not devices, i made scripts so it opens till % open
and closes
Yeah, but I want to speak native to google, and not use Keywords like activate for scripts, I prefer open/close/stop cover
Hello
I have 8 SOMFY motors for rolling shutters, paired with a KLF200 and everything is working perfectly. I also had a SOMFY motor for a garage door and it also worked well with the KLF200 and HA.
But I also have a SOMY on/off plug. It is OK on the KLF200 side (the plug is paired with the KLF200) but I can’t find the plug in HA…
Does anybody have an idea what could be the problem?
Plugs are not supported by the Velux integration as per the docs, see here:
Thank you for your answer.
I read this page but it was not so clear to me. I was a bit confused by the mention of « light ». If I am right, the here is no io light product, but there are io receveirs than can drive lights. So I though that my plug will be recognised as a light.
Anyway, I think this page of the doc should be more clear about what kind of devices are supporter or not.
Since my previous message, I read the github page of PyVLX.
I had some hope when I read this
« Changing of on-off switches:
await pyvlx.nodes[‘CoffeeMaker’].set_on()
await pyvlx.nodes[‘CoffeeMaker’].set_off() »
(My plug is recognised by the KLF200 as an on-off switch)
but then I saw someone posted an issue to ask for the support of on/off plugs.
Someday maybe…!
Hi,
I tried to add my KLF200 to HA running in Docker on Synology NAS yesterday. But I wasn’t able to add the integration. I tried to add custom integration in HACS which looked it worked, but still can’t choose the integration.
Anything else I need to install, Python or something?
Thx, pretty new to HA
The Velux integration is part of HA, no need to add. Unless you mean the MyVelux integration, that is a little different. Have you added the config with the IP address in the configuration.yaml as described in the above link?
Yes I did, but doesn’t change anything or how can I now control anything via KLF200 ?
The below is what I added. and a custom integration as well, but still can’t choose integration vellum anywhere in home assistant
velux:
host: “192.168.X.XXX”
password: “KLF200WIFIPASSWORD”
I also tried this My Velux via HACS but it doesn’t show up nor download the folder to custom components 
Make sure you have the indentations in the config, else it will fail. And of course no “quotes”
velux:
host: IP_ADDRESS
password: VELUX_WIFI_PASSWORD
Then, do a HA-config check and a HA-reboot, as far as I remember, it should do an auto-discover of the device (but I’m not sure). If that is not the case, head to Integrations, click add and search for Velux in order to configure it.
Also, and this is very important, what Firmware are you having on the KLF at this stage?
Unfortunately I’ve done all this, no difference between quotes or not. I cannot find Velux at all in the integrations part, not showing up to choose it
These are the errors showing up in the log when I just started the HA
Can not process <Telegram direction=“Incoming” source_address=“1.0.16” destination_address=“10/3/14” payload="<GroupValueResponse value="" />" /> for Licht Zimmer 1 - State: <CouldNotParseTelegram description=“Payload invalid” payload=""/>
21:53:58 – (WARNING) /usr/local/lib/python3.9/site-packages/xknx/remote_value/remote_value.py - message first occurred at 21:51:37 and shows up 5 times
Could not sync group address ‘12/0/1’ (Stromverbrauch Total - Value)
21:53:41 – (WARNING) /usr/local/lib/python3.9/site-packages/xknx/remote_value/remote_value.py - message first occurred at 21:51:37 and shows up 4 times
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 12/0/1
21:53:41 – (WARNING) /usr/local/lib/python3.9/site-packages/xknx/core/value_reader.py - message first occurred at 21:51:37 and shows up 4 times
custom-components/wienerlinien - Repository is archived.
21:51:54 – (ERROR) HACS (custom integration) - message first occurred at 21:51:54 and shows up 2 times
Setup failed for velux: Integration failed to initialize.
21:51:51 – (ERROR) setup.py
Can’t connect to velux interface:
21:51:51 – (ERROR) velux
Setup of velux is taking over 10 seconds.
21:51:43 – (WARNING) /usr/local/lib/python3.9/asyncio/events.py
Error doing job: application protocol failed to receive SSL data
21:51:41 – (ERROR) /usr/src/homeassistant/homeassistant/runner.py
Entity sensor.hacs (<class ‘custom_components.hacs.sensor.HACSSensor’>) implements device_state_attributes. Please report it to the custom component author.
21:51:37 – (WARNING) helpers/entity.py
Detected code that uses str for device registry entry_type. This is deprecated and will stop working in Home Assistant 2022.3, it should be updated to use DeviceEntryType instead. Please report this issue.
21:51:37 – (WARNING) helpers/frame.py
192.168.0.78 is not logged in to a HEOS account and will be unable to retrieve HEOS favorites: Use the ‘heos.sign_in’ service to sign-in to a HEOS account
21:51:35 – (WARNING) Denon HEOS
The ‘tunneling’ option near /config/configuration.yaml:31 is deprecated, please remove it from your configuration
21:51:34 – (WARNING) KNX
What is the Velux Gateway Firmware Version?
Latest Firmware 2.0.0.71
that’s showing in the logs
2022-06-07 20:49:16 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-07 20:49:16 ERROR (SyncWorker_2) [homeassistant.loader] Error parsing manifest.json file at /config/custom_components/velux/manifest.json: Expecting value: line 8 column 1 (char 7)
2022-06-07 20:49:18 DEBUG (MainThread) [homeassistant.components.velux] Velux interface started
2022-06-07 20:49:18 DEBUG (MainThread) [pyvlx] Connecting to KLF 200.
Does that mean the connection to KLF200 works, but within HA anything doesn’t?
I guess you should remove the velux custom component and try again.
And maybe take care of all the other warnings in your logs too 
I just added it to get it working, neither works with nor without
And btw I don’t get the KNX issues as it’s working and the addresses are working fine.
Make sure you include the reboot automation, klf are stuck quite often, it’s necessary to reboot it when you restart HA, so make sure you include the reboot automation
but shouldn’t it work at least once.
I know the automation code, but don’t know where I can put it just the code, is it also in the config yaml? oder under automation where I cannot just use a code to copy?
Yes, it’s not an integration, you need to put it in manually into the config, see here
but what I mean where do I put in this code below, just into the YAML? or where on the automation part can I put in just code?
automation:
alias: KLF reboot on hass stop event
description: Reboots the KLF200 in order to avoid SSL Handshake issue
trigger:
- platform: homeassistant
event: shutdown
action:
- service: velux.reboot_gateway
I put that into YAML now but also after restarting I only got the automation in, but no Velux things.
Question on the KLF200 itself, how does it look on your side. I just added the shutters and LED lights, is there anything else to do? So I pressed PROG on the Somfy IO remote and the devices were showing up in KLF200, nothing else done. Did I miss anything there maybe?