Ok,
thanks @wmaker for the tip. I’ve got myself back to that today and took your hint in as well as I’ve read in other cases, the homekit component may cause problems with the homekit controller.
1.a) I removed the homekit component from my configuration.yaml, reset and restarted the velux system completely. tried to find it in HomeAssistant just after connecting the gateway to the WiFi (same subnet as the Synology where I run Home Assistant on docker) when it allows to create a new home. it didn’t show up.
1.b) I’ve readded HomeKit component to the config file with the input_boolean.test and couldn’t discover it neither.
during that time, the process kind of got lost and I had to restart with connecting the gateway to the network.
I kept going further creating the home on the Velux Active App and tried step a and b again when it was asking me for the HomeKit Setup Code.
2.a) without homekit component
2.b) with homekit component and the input_boolean.test
neither with success.
again, the process stopped and I had to restart with connecting the gateway to the network, create the home, cancelled the process of adding to homekit and added the products on the Velux Active App
3.a) without homekit component
3.b) with homekit component and input_boolean.test
still no success.
furthermore I discovered the following in my log file:
2018-08-24 14:05:44 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 244, in discovery_dispatch
config_num = int(discovery_info['properties']['c#'])
KeyError: 'c#'
@wmaker, if you have any other idea how to solve that, let us know. I’m in to try.