# \[APP\]\[PRO\] LedFx – Control your LedFx virtuals, effects and scenes (test) **URL:** \ **Category:** Apps\ **Tags:** app, homey-pro\ **Created:** [September 27, 2026, 1:43pm UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070 "2026-09-27T13:43:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Dennis\_Klatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_klatt/32/35258_2.png) [@Dennis\_Klatt](https://community.homey.app/u/Dennis_Klatt)\ **Post date:** [September 27, 2026, 1:43pm UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070/1 "2026-09-27T13:43:16Z")
A beta of the LedFx app for Homey Pro is now available as a test version: > **[LedFx | Homey](https://homey.app/en-us/app/community.ledfx/LedFx/)** > > Let your lights dance to the music What it does: - “LedFx server” device: all virtuals on/off, global brightness, and a flow card to activate LedFx scenes - A device per LedFx virtual: on/off, brightness and the active effect - Flow cards to set an effect, apply a preset or clear the effect How to get started: 1. Give the PC/Pi running LedFx a fixed IP address (LedFx 2.x, default port 8888) 2. Add the “LedFx server” device first, then add your virtuals 3. Try on/off, brightness and a scene from a flow Good to know: - I don’t have a LedFx setup myself, so this is built on the LedFx API documentation. You’re the first real tester, so some things may not work yet. - Brightness per virtual only works when an effect is active (that’s how LedFx works). - Homey Pro only; it communicates locally over your network. If something doesn’t work: Homey app → Settings → Apps → LedFx → Send diagnostics report, and post here what you did and what happened. The logs show me exactly where it goes wrong. Looking forward to your feedback! ---
**Author:** ![Dennis\_Klatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_klatt/32/35258_2.png) [@Dennis\_Klatt](https://community.homey.app/u/Dennis_Klatt)\ **Post date:** [September 28, 2026, 5:29am UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070/2 "2026-09-28T05:29:21Z")
@Pieter_Pessers thanks for testing and for sending the diagnostics report, that really helps! The log shows that Homey can’t reach LedFx at all during pairing. So it’s a network issue, not a problem with your lights or the virtuals. Usually that’s quick to fix. Could you check these: 1. Quick test: on your phone (on the same Wi-Fi as Homey), open http://:8888/api/info If that page doesn’t load, Homey can’t reach LedFx either. 2. Firewall (most common cause if LedFx runs on Windows): open PowerShell as administrator on the LedFx PC and run: New-NetFirewallRule -DisplayName “LedFx” -Direction Inbound -Protocol TCP -LocalPort 8888 -Action Allow -Profile Private Also check that your network is set to “Private” (not “Public”) in the Windows network settings. 3. In the Homey pairing screen, enter only the IP address (e.g. 192.168.1.50), without http:// or the port. 4. Make sure the LedFx PC and Homey are on the same network (not a guest Wi-Fi). I’ve also released version 1.2.0 in test. It gives much clearer error messages, so if it still fails, the message tells us exactly why (for example “connection refused” or “no response, check firewall”). Please update the test app, try pairing again, and let me know what the error says, or send a new diagnostics report. Also useful to know: which LedFx version do you use, and does it run on Windows, a Raspberry Pi or Docker? ---
**Author:** ![Pieter\_Pessers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pieter_pessers/32/8848_2.png) [@Pieter\_Pessers](https://community.homey.app/u/Pieter_Pessers)\ **Post date:** [September 28, 2026, 11:02am UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070/3 "2026-09-28T11:02:10Z")
Hello @Dennis_Klatt. I got it working. This is great. I think used the wrong IP-address. It is when i went back to the WLED controller i noticed there was a override on 192.168.1.209. Not what the webbrowser showed on 127.0.0.1. I need do learn how to use the app. On this moment i only see the scene: “Blade scene”. I sended you a log. Maybe it helps you pollishing the app. 😉 5b11fa5c-80b7-4f5c-ac32-42506d6c0130 ---
**Author:** ![Dennis\_Klatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_klatt/32/35258_2.png) [@Dennis\_Klatt](https://community.homey.app/u/Dennis_Klatt)\ **Post date:** [September 28, 2026, 4:22pm UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070/4 "2026-09-28T16:22:05Z")
@Pieter_Pessers thanks for the log and the kind words! It already helped: pairing works fine with LedFx 2.1.9, and global brightness on the “LedFx server” device is confirmed working. I’ve just released version 1.3.0 in test: - The app now warns when 127.0.0.1 or localhost is entered during pairing (so others don’t run into the same thing you did) - Better diagnostics logging - New app and device images Could you help me test the rest of the app? That would be great: 1. Create a flow with the action “Activate scene” and pick “Blade scene” 2. Switch one of your virtuals on and off, and change the brightness (this works when an effect is active on that virtual) 3. Optional: try “Set effect” or “Apply preset” in a flow Afterwards, please send another diagnostics report. Then I can see whether everything works as it should. Two tips: - Give your LedFx PC a fixed IP (192.168.1.209) in your router, so the connection keeps working after a restart. - LedFx shows your strips and their segments as separate virtuals (for example lepro-tb1 and lepro-tb1-seg-0/1/2). You don’t have to add them all to Homey; only add the ones you actually want to control. Controlling a strip and its segments at the same time can give unexpected results in LedFx. Thanks again for testing! > **[LedFx | Homey](https://homey.app/nl-nl/app/community.ledfx/LedFx/test/)** > > Bedien je lokale LedFx-engine: virtuals, effecten, presets en scènes. ---
**Author:** ![Pieter\_Pessers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pieter_pessers/32/8848_2.png) [@Pieter\_Pessers](https://community.homey.app/u/Pieter_Pessers)\ **Post date:** [September 28, 2026, 5:29pm UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070/5 "2026-09-28T17:29:52Z")
Hello Dennis. Beautifull app images. I can tell you that also in the flow activating a scene works. And also adjusting the brightness. Switching the LedFX gives the control back to the wled controller. Perfect. But when switching it back on again looks that only 2 of the 3 segments will be controlled by LedFX. the 3th segment turns off. When starting your app my led-controller freezes. Don’t you worry. It is not by your app. I had it before. Reason unknown. So when you see many problems in the app this can be generated by the controller. Not by your app. I think you can trust the logging from around 19:00. Thank you for your app. Sended you a small donation 1099bc0f-a13c-419c-b8a9-8df3964f7e55 ---
**Author:** ![Dennis\_Klatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_klatt/32/35258_2.png) [@Dennis\_Klatt](https://community.homey.app/u/Dennis_Klatt)\ **Post date:** [September 28, 2026, 6:27pm UTC](https://community.homey.app/t/app-pro-ledfx-control-your-ledfx-virtuals-effects-and-scenes-test/160070/6 "2026-09-28T18:27:37Z")
@Pieter_Pessers thank you so much, both for the thorough testing and for the donation! Really appreciated. Great to hear that scenes and brightness work. The issue with the third segment is caused by my app, not by you. When the “LedFx server” device was switched on, the app activated all virtuals, including ones that were off before or had no effect (like the full strip together with its segments). An active virtual without an effect sends black, which is why one segment turned off. I’ve just released version 1.4.0 in test: - Switching the server off now remembers which virtuals were active - Switching it on restores exactly those virtuals, one by one, instead of switching on everything Could you update and try it again: switch the server off, then back on, and check if all 3 segments come back? A new diagnostics report afterwards would be very helpful, because the log now shows exactly which virtuals are remembered and restored. About the controller freezing: I agree it’s probably not the app. The app only talks to LedFx, never directly to your WLED controller, and at startup it only reads status. So it could be LedFx or the controller itself. Thanks for mentioning it, I’ll only look at the logs from 19:00. Thanks again!