You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Lumux assigns all lights to the entertainment zone #8
When syncing the entertainment zone, which only has a single light, to Lumux, it reads it with 7 channels and tries to control all my lights. Syncing does not work and setting read mode gets applied to all lights in my home.
I am using the Flatpak on Fedora. I have a Hue Bridge V2 and the Hue Play Gradient Light Strip for PC.
In the Hue App, my entertainment zone only contains the Light strip. I also tried recreating the entertainment zone.
I have the same behaviour when I add a Hue Iris to the entertainment zone instead.
I’m experiencing the same issue. I installed v0.6.0 via Flatpak on Arch Linux using GNOME 50.1.
My setup includes a Bridge v3 and a sync zone consisting of a Hue Play Gradient Lightstrip and an E27 color bulb (reporting as 10 channels).
When I start syncing, the zone correctly changes colors at first, but then it freezes and drops the connection (seemingly on the Hue side, as the lights fade out like when you stop it via the app). While Lumux continues to attempt the sync, the visuals no longer update and the output drops to 0.5 FPS, despite a target of 30 FPS.
Using the reading mode changes all lights connected to that bridge. Not sure if video mode does the same.
I was able to resolve the issue by completly uninstalling all setup files included and starting from scratch. After reconnecting to the bridge lumux didn't work but after stopping and restarting lumux now everything works perfectly again. Hope this helps!
I've uninstalled the app and then deleted the folder ~/.var/app/io.github.enginkirmaci.lumux, but it did not fix my problems.
Was these the steps you did?
I installed Lumux via Discover. I uninstalled the usual way and then klicked on "remove all files". After reinstalling an reconnecting to the bridge everything works again. Today I did a cold start and it worked automatically (after choosing the window).
Reading Mode tries to find the zone's lights by matching channel members with rtype == 'light'. But in the Hue v2 API those members are always entertainment services, never light. So nothing matches and it nosedives into the fallback:
# Fallback: use all known lightsreturnself.bridge.get_light_ids() # yep, the whole house
With reading_mode.auto_activate on (the default), this also fires on app quit and PC shutdown, so stopping or shutting down can light up every room. There's a second gremlin too: turn_off() stops sync, the callback re-activates reading mode, then turn_off bails without turning anything off. So shutdown turns lights ON. Backwards af.
Fix: resolve the zone's lights properly (grab the entertainment rids from the config, map each to its light rid via /resource/device), and kill the all-lights fallback so no zone means no-op. Plus mute that auto-activate callback during turn_off. After this, reading mode only touches the zone (9 devices for me instead of 34), and shutdown stays quiet.
No-patch workaround: set reading_mode.auto_activate to false, or fill in reading_mode.light_ids in settings.json. An explicit list skips the broken discovery entirely.
Activity
timscn123 commentedon Apr 28, 2026
I’m experiencing the same issue. I installed v0.6.0 via Flatpak on Arch Linux using GNOME 50.1.
My setup includes a Bridge v3 and a sync zone consisting of a Hue Play Gradient Lightstrip and an E27 color bulb (reporting as 10 channels).
When I start syncing, the zone correctly changes colors at first, but then it freezes and drops the connection (seemingly on the Hue side, as the lights fade out like when you stop it via the app). While Lumux continues to attempt the sync, the visuals no longer update and the output drops to 0.5 FPS, despite a target of 30 FPS.
Using the reading mode changes all lights connected to that bridge. Not sure if video mode does the same.
Tylli commentedon Apr 28, 2026
I was able to resolve the issue by completly uninstalling all setup files included and starting from scratch. After reconnecting to the bridge lumux didn't work but after stopping and restarting lumux now everything works perfectly again. Hope this helps!
timscn123 commentedon Apr 28, 2026
I've uninstalled the app and then deleted the folder ~/.var/app/io.github.enginkirmaci.lumux, but it did not fix my problems.
Was these the steps you did?
Tylli commentedon Apr 29, 2026
I installed Lumux via Discover. I uninstalled the usual way and then klicked on "remove all files". After reinstalling an reconnecting to the bridge everything works again. Today I did a cold start and it worked automatically (after choosing the window).
thepedroferrari commentedonMay 25, 2026
Heads up, there are two separate things tangled in this thread. I fixed the "reading mode hits every light in the house" part
This is the one @dalton5000 and @timscn123 both mention, and it's a real bug.
Reading Mode tries to find the zone's lights by matching channel members with
rtype == 'light'. But in the Hue v2 API those members are alwaysentertainmentservices, neverlight. So nothing matches and it nosedives into the fallback:With
reading_mode.auto_activateon (the default), this also fires on app quit and PC shutdown, so stopping or shutting down can light up every room. There's a second gremlin too:turn_off()stops sync, the callback re-activates reading mode, thenturn_offbails without turning anything off. So shutdown turns lights ON. Backwards af.Fix: resolve the zone's lights properly (grab the
entertainmentrids from the config, map each to itslightrid via/resource/device), and kill the all-lights fallback so no zone means no-op. Plus mute that auto-activate callback duringturn_off. After this, reading mode only touches the zone (9 devices for me instead of 34), and shutdown stays quiet.No-patch workaround: set
reading_mode.auto_activatetofalse, or fill inreading_mode.light_idsinsettings.json. An explicit list skips the broken discovery entirely.