# \[APP\]\[Pro\] Velux **URL:** \ **Category:** Apps\ **Tags:** app, homey-pro\ **Created:** [September 5, 2024, 7:12pm UTC](https://community.homey.app/t/app-pro-velux/115573 "2024-09-05T19:12:09Z")\ **Posts on this page:** 20\ **Page:** 4
**Author:** ![jss](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jss/32/121174_2.png) [@jss](https://community.homey.app/u/jss)\ **Post date:** [August 5, 2025, 7:27am UTC](https://community.homey.app/t/app-pro-velux/115573/62 "2025-08-05T07:27:21Z")
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](http://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, JS ---
**Author:** ![Peter\_Jensen1](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peter\_Jensen1](https://community.homey.app/u/Peter_Jensen1)\ **Post date:** [August 15, 2025, 7:28pm UTC](https://community.homey.app/t/app-pro-velux/115573/63 "2025-08-15T19:28:52Z")
Hi JS, It sounds like a connection issue, but i will have a look if you put the following into you papertrail settings (in the app configurations): **Papertrail Host:** x **Papertrail Port:** x (removed) Best, Peter ---
**Author:** ![jss](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jss/32/121174_2.png) [@jss](https://community.homey.app/u/jss)\ **Post date:** [August 15, 2025, 7:45pm UTC](https://community.homey.app/t/app-pro-velux/115573/64 "2025-08-15T19:45:49Z")
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. ---
**Author:** ![Peter\_Jensen1](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peter\_Jensen1](https://community.homey.app/u/Peter_Jensen1)\ **Post date:** [August 18, 2025, 7:07pm UTC](https://community.homey.app/t/app-pro-velux/115573/65 "2025-08-18T19:07:10Z")
Hi JS I canā€™t see any logs from you, but it might be on my end. Will you please click on one of your devices in homey and send me the full url Will look something like this **[https://my.homey.app/homeys/640eca400xxxxx958954b8/devices/604b3a63-xxxx-xxxx-xxxx-b5acfbdda79d](https://my.homey.app/homeys/640eca400xxxxx958954b8/devices/604b3a63-xxxx-xxxx-xxxx-b5acfbdda79d)** Best Peter ---
**Author:** ![Richard\_Biz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/richard_biz/32/16757_2.png) [@Richard\_Biz](https://community.homey.app/u/Richard_Biz)\ **Post date:** [August 19, 2025, 9:05pm UTC](https://community.homey.app/t/app-pro-velux/115573/66 "2025-08-19T21:05:20Z")
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 ---
**Author:** ![Herve69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/herve69/32/37183_2.png) [@Herve69](https://community.homey.app/u/Herve69)\ **Post date:** [August 22, 2025, 9:43am UTC](https://community.homey.app/t/app-pro-velux/115573/67 "2025-08-22T09:43:06Z")
Hi Richard, 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 ![Capture dā€™Ć©cran 2025-08-22 114157](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/9/0906e0b060753e7f60be199d9120c0a684298d26.jpeg) ---
**Author:** ![Richard\_Biz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/richard_biz/32/16757_2.png) [@Richard\_Biz](https://community.homey.app/u/Richard_Biz)\ **Post date:** [August 22, 2025, 9:30pm UTC](https://community.homey.app/t/app-pro-velux/115573/68 "2025-08-22T21:30:28Z")
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 ---
**Author:** ![Herve69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/herve69/32/37183_2.png) [@Herve69](https://community.homey.app/u/Herve69)\ **Post date:** [August 25, 2025, 8:12am UTC](https://community.homey.app/t/app-pro-velux/115573/69 "2025-08-25T08:12:32Z")
Okey, great šŸ™‚ I also used the Velux Active because I already had it, and Velux told me to do so ^^ ---
**Author:** ![petero-dk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petero-dk/32/81190_2.png) [@petero-dk](https://community.homey.app/u/petero-dk)\ **Post date:** [August 29, 2025, 9:45pm UTC](https://community.homey.app/t/app-pro-velux/115573/70 "2025-08-29T21:45:04Z")
Fyi, I had a Velux KLF-200 from an earlier project and I have just created a proof of concept APP that works with Windows for now. > [@\[APP\]\[Pro\] Velux via KLF 200](https://community.homey.app/t/app-pro-velux-via-klf-200/142411): > > I have just made a proof of concept for a Velux App that runs completely locally via the KLF-200. Currently it just supports Window Openings. The source code can be found here [GitHub - petero-dk/org.obel.velux: App for Homey to control Velux Skylights, using a KLF-200](https://github.com/petero-dk/org.obel.velux) It will detect (probably) rain and update the sensor value, but it will for now not update the sensor value if the window is not moving. Because of the weird way the KLF closes connections, there are two extra flow cards that wiā€¦ ---
**Author:** ![H\_van\_Barneveld](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/h_van_barneveld/32/18371_2.png) [@H\_van\_Barneveld](https://community.homey.app/u/H_van_Barneveld)\ **Post date:** [September 6, 2025, 5:07pm UTC](https://community.homey.app/t/app-pro-velux/115573/71 "2025-09-06T17:07:23Z")
Does this also mean that for control of blinds I can use tahoma? in our new house there are two Manual velux Windows. I want to open/close both separately and mount at both shutters. Windows are at different floors. I have Some doubt about what i need from velux to control it all with Homey (and remote in the room ) ---
**Author:** ![Sprenged](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sprenged/32/120739_2.png) [@Sprenged](https://community.homey.app/u/Sprenged)\ **Post date:** [October 31, 2025, 8:07am UTC](https://community.homey.app/t/app-pro-velux/115573/72 "2025-10-31T08:07:20Z")
Hi guys! 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. Do any of you recognise this behaviour? ---
**Author:** ![Matthias\_Sieber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthias_sieber/32/120715_2.png) [@Matthias\_Sieber](https://community.homey.app/u/Matthias_Sieber)\ **Post date:** [March 8, 2026, 12:01pm UTC](https://community.homey.app/t/app-pro-velux/115573/73 "2026-03-08T12:01:51Z")
Hi everyone, 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? Any ideas would be greatly appreciated. Thanks! ---
**Author:** ![Matthias\_Sieber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthias_sieber/32/120715_2.png) [@Matthias\_Sieber](https://community.homey.app/u/Matthias_Sieber)\ **Post date:** [March 8, 2026, 6:15pm UTC](https://community.homey.app/t/app-pro-velux/115573/74 "2026-03-08T18:15:35Z")
Just a quick update on my issue. 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. ---
**Author:** ![Rasket787](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rasket787/32/138382_2.png) [@Rasket787](https://community.homey.app/u/Rasket787)\ **Post date:** [March 17, 2026, 9:49am UTC](https://community.homey.app/t/app-pro-velux/115573/75 "2026-03-17T09:49:34Z")
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. ---
**Author:** ![Didier\_Boschmans](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/didier_boschmans/32/120935_2.png) [@Didier\_Boschmans](https://community.homey.app/u/Didier_Boschmans)\ **Post date:** [April 7, 2026, 2:32pm UTC](https://community.homey.app/t/app-pro-velux/115573/76 "2026-04-07T14:32:20Z")
Hi Peter, My exterior awning blind (store pare-soleil) used to work with the Homey Velux app but is no longer found since a recent update. The roller shutter on the same gateway (3LG E01) still works fine. Could this be a regression? Thanks ---
**Author:** ![Rene\_Kaeseler](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rene_kaeseler/32/121015_2.png) [@Rene\_Kaeseler](https://community.homey.app/u/Rene_Kaeseler)\ **Post date:** [May 22, 2026, 3:43pm UTC](https://community.homey.app/t/app-pro-velux/115573/77 "2026-05-22T15:43:19Z")
Hi - I read the first post about the limitation of not being able to close the Velux windows after opening them via this app. Does this limitation still apply, or has it been resolved in the meanwhile? ---
**Author:** ![Joffray](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joffray/32/120728_2.png) [@Joffray](https://community.homey.app/u/Joffray)\ **Post date:** [July 13, 2026, 4:30pm UTC](https://community.homey.app/t/app-pro-velux/115573/78 "2026-07-13T16:30:48Z")
Hi, did we find a solution to bypass the code to open the Velux or to give the code to Velux through a script like it is done with Google Home? Thanks ---
**Author:** ![Guillaume\_Chopot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/guillaume_chopot/32/168951_2.png) [@Guillaume\_Chopot](https://community.homey.app/u/Guillaume_Chopot)\ **Post date:** [July 15, 2026, 8:09pm UTC](https://community.homey.app/t/app-pro-velux/115573/79 "2026-07-15T20:09:48Z")
Hi, Iā€™m experiencing the same problem with the Velux Kig 300 and the Velux App that always asks for the code to open the shutters, thus blocking the Homey App. It doesnā€™t seems to be a problem for the blinds though. Is there the same problem with Tahoma? Best regards, Guillaume ---
**Author:** ![Nicki\_Madsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nicki_madsen/32/170989_2.png) [@Nicki\_Madsen](https://community.homey.app/u/Nicki_Madsen)\ **Post date:** [August 5, 2026, 9:03pm UTC](https://community.homey.app/t/app-pro-velux/115573/80 "2026-08-05T21:03:51Z")
Hi, First of all, thank you for your work on the VELUX app. I have just installed a new **VELUX KIX 300** gateway and connected it successfully to the official VELUX app. Everything works perfectly in the VELUX app, and I can both open and close my roof windows. I then installed the Homey VELUX app (version **1.3.1** ). The app successfully imports all my devices (2 roof windows and 2 blinds), and it correctly displays their current positions. However, I have an issue with the roof windows: - I can **close** the windows from Homey. - I **cannot open** them or move them to a partially open position. - When I try, Homey displays the following message: ā€œDue to Velux security measures, you can only view the status and close the window covering. Opening it is not permitted.ā€ This message appears even though Iā€™m controlling a **roof window** , not a window covering. The same windows can be opened without any issues from the official VELUX app. My setup: - Homey Pro (2023) - VELUX app v1.3.1 - VELUX KIX 300 gateway - Official VELUX app working correctly - 2.4 GHz Wi-Fi (UniFi network) Is this a known issue with the current API or the Homey app? If you need logs or if there is a beta version available, Iā€™d be happy to help test. ---
**Author:** ![Nic2](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nic2/32/170647_2.png) [@Nic2](https://community.homey.app/u/Nic2)\ **Post date:** [August 24, 2026, 1:30pm UTC](https://community.homey.app/t/app-pro-velux/115573/81 "2026-08-24T13:30:51Z")
Exactly the behavior I am experiencing right now. Did you manage to get it working? [Previous page](https://community.homey.app/t/app-pro-velux/115573.md?page=3) [Next page](https://community.homey.app/t/app-pro-velux/115573.md?page=5)