Anyone with the same problem?
I use the rhythm scene ‘Burlesque Rhythm’ while listening to music. However, that scene consistently freezes after some time. So far, it is the only scene affected; I have not seen this behavior with any of the other community scenes I downloaded through the iOS app. Other than that, I have no issues at all — the only problem is these freezes. Anyone??
In the meantime, I even built a live investigator to observe in real time what is actually happening. I can also work around the issue — and effectively fix it — with that live script running; it basically performs a soft restart of the scene at a defined interval, all fully automatically once the script is started.
(Support case already open)
-
Offizieller Kommentar
Thank you for the feedback and for sharing the detailed troubleshooting you've already done. We've escalated this issue to our team and have worked to address it. Since you're seeing the behavior specifically with the "Burlesque Rhythm" scene while other community rhythm scenes continue to function normally, we'd recommend making sure your Nanoleaf device firmware and Nanoleaf app are updated to the latest available versions, as updates may include fixes related to scene performance and stability.
Since you already have a support case open, please provide your support ticket number if you haven't done so recently. This will allow us to review the case, gather any additional information needed, and help get this fully resolved as quickly as possible.
You can also update your existing case or contact support here: https://support.nanoleaf.me/hc/en-us/requests/new
-
Thanks for the comment.
My case number is #221680 — I originally submitted the ticket around the end of May / beginning of June and have already been in touch with support several times by email. so yes, this issue and I know each other pretty well by now.
All of my devices and apps are fully up to date, always and everywhere.
No worries though - I’m a patient person and I know there’s no solution yet and the team is still investigating, which is perfectly fine for me.
Right now I can work around the problem by running a live script on my MacBook whenever I listen to music, so I’m not under any real pressure. It’s a bit of a nerdy workaround, but it does the job.
I’ve invested quite a bit of time into optimizing and analyzing the behavior with a custom live investigator setup, so I can provide more technical data if that’s useful:
At this point I can make the freezes visible in a live log, and during analysis I can consistently break the freeze either via specific actions in the macOS Nanoleaf Desktop app / iOS app or through the ‘autorecover’ routine in my script. When autorecover simply re‑selects the current scene without me manually overcoming the freeze via the Nanoleaf apps beforehand, the controller purrs like a kitten again — everything behaves normally.
By using the Nanoleaf apps to interact with the frozen scene, I can however trigger and observe these freezes very clearly, which lets me capture the behavior quite precisely. When that happens, either the scene continues or the controller crashes and does a kind of near‑restart. After that, overall stability tends to degrade over time. The longer it runs, the more unstable everything becomes — 4D Screen Mirror, controller responsiveness, API reachability, and even the apps themselves start lagging or temporarily fail to recognize all other Nanoleaf devices also.From that point on, the only thing that really helps is cutting power and doing a full restart of the controller.
Long story short: if my autorecover kicks in within roughly two minutes, everything is fine and the system stays stable; if I ‘revive’ the scene via the Nanoleaf macOS/iOS apps instead, the controller goes into a very odd, unstable and critical mode where things slowly fall apart — including 4D Screen Mirror, controller responsiveness, API reachability, and app behavior.
So it looks like I can reliably trigger a broader instability state, not just a one‑off scene freeze, and I can reproduce it consistently.
Over the next days, when I find some time again, I plan to record a few clean multi‑hour sessions with my investigator and run them through my NDJSON log analysis. If that helps your investigation, I’m happy to share additional logs and possibly another video — and I’m also happy to dive deeper into the technical side of this
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare