Hi Peter, thanks for the app.
I have an issue with the flows and sometimes the blinds wont open. I saw in the configuration section there is an input for the papertrail.com platform to send the logs, but it is complicated to open an account there.
What do you suggest I could use to get hold of the logs and see what is really happening ?
Cheers,
Oh, thank you very much, i am going to input that right away.
If everything is fine, you should see calls for curtain opening in the morning (around 6:20) and calls for closing at dusk.
They actually close but not open . I have to trigger the opening manually because the flow doesn’t open them.
Hervé, I bought a Tohoma Switch and tried to make the IO transfer as you described in your French manual. Am I right you choose “Transfer IO key” and not recieve an IO key. And after this choice, you have to select a compatible device. Is that “Other, compatible with IO home control”.
I did not got this working and have manualy installed the velux windows in Tohoma
Yes that’s right. You don’t receive any IO key by yourself. The TaHoma will transfer this key and that’s the Velux Active Box that will receive it.
After having selecting “Other, compatible with IO home control” on the TaHoma app, have you done the final manip using the Velux Active box ? See below
Oké, clear. But using the Tahoma Switch directly in Homey and address the windows in Tahoma Switch the Velux Active is not necessary anymore, right? So why did you made this workaround
I’ve been using the Velux community app of Peter Jansen (much appreciated Peter!) in combination with 6 Velux windows, blinds, sun screens and some room sensors.
I’ve been experiencing that my automations on a regular basis don’t seem to work because the app seems to loose some sort of connection/session with the active control hub. On a restart of the app in homey everything works fine again.
As a workaround I now imported a restart of the app at the start of the planned flows and that seems to solve my problem but I can’t figure out what is causing the real problem.
I’m using the Homey Velux app together with a VELUX ACTIVE with NETATMO gateway (model code 3LG E01 EU).
This system connects VELUX products (windows, blinds, shutters) via io-homecontrol and communicates with the VELUX / Netatmo cloud through the gateway.
My setup worked perfectly for many months, but for a few weeks now (I believe since late 2025) my four shutters stopped responding in Homey.
What I observe
The devices appear online in Homey
When I try to control a shutter, the command times out
No “device unreachable” warning is shown
If I restart the Velux app in Homey, the shutters briefly show as offline, then come back online
After that they still timeout on every command
Interestingly, my indoor climate sensor still works and reports data regularly, so the gateway itself seems reachable.
What I already tried
Restarting the Velux app
Removing the Velux app from Homey completely
Installing the app again and trying to reconfigure everything from scratch
Unfortunately, the setup process also fails with a timeout when trying to add the shutter devices again.
Possible authentication change?
When I log out of the official VELUX ACTIVE app and log in again, I now have to authenticate via the gateway by pressing the button on the underside of the hub to retrieve an authentication key.
This step seems to be required for new devices or users and might be related to security changes in the Velux / Netatmo ecosystem.
My suspicion is that:
the gateway requires a new authentication
but the Homey Velux app does not trigger this authentication flow
Without completing this authentication step, the gateway might no longer allow control commands, which could explain the timeouts.
Questions
Has anyone else with VELUX ACTIVE with NETATMO experienced similar issues recently?
Could this be related to changes in Velux / Netatmo authentication or API behaviour?
Is there any workaround or updated version of the app that supports the newer authentication flow?
As a workaround I decided to try a different approach. I reset all shutter motors and paired them with my Somfy TaHoma bridge instead, since they use io-homecontrol.
The reset process was not exactly straightforward (each shutter motor had to be reset individually before it could be discovered again), but in the end it worked successfully.
After pairing them with TaHoma, I was able to integrate the shutters into Homey via the TaHoma integration, and control works normally again.
So the shutters themselves and the io-homecontrol communication appear to be working perfectly fine. The issue therefore seems to be specific to the VELUX / Netatmo gateway integration in Homey.
For now I have retired my VELUX bridge and put it aside, since the TaHoma setup is currently the only reliable way for me to control the shutters via Homey.
Does this only work with VELUX Active with Netatmo, or is the standard VELUX App Control gateway enough? I don’t really need the extra sensors that come with Netatmo.