Node 2021 LED Light switch on randomly

Answered

Comments

91 comments

  • Rudi B.

    Hi Tony,

    I can confirm. Many thanks to all who were supporting the bug fix!

     

    1
  • Nate

    I've just taken delivery of a NODE and I'm having this same issue, despite it running the latest firmware. I'm a little bit concerned that it seems to have been fixed for most people 4 months ago!

    I have the indicator brightness set to off. A previous post seemed to hint that stray light might cause the issue, however, with a darkened room and no direct light or any light change whatsoever, it will sometimes light up 5-6 times in 10 minutes, or sometimes go 20 minutes between being activated. Either way, it's very annoying!

    The firmware version is 3.16.7. 

    0
  • Tony W.
    Product Support Manager

    Hi Nate - I have escalated your issue to our Support Crew for more 1:1 details about your proximity sensor

    1
  • Nate

    Thanks, Tony. 

    0
  • Stefan Müller

    The same issue here. Also version 3.16.7 Build 2650.

    0
  • Gerrit Deppe

    Same issue here, Node is freh out of the box.

    Firmware 3.16.7.

    0
  • Tony W.
    Product Support Manager

    Please select Help, Send Support Request in the BluOS App so our Support Crew may take a closer look.

    0
  • Виталий

    Hi all. There was the same problem, the device is only 7 months old. LED panel flashing for no reason

    1
  • Seppi Evans
    Hi-Res

    ^^^

    If the LED is blinking blue then it’s been out into mute mode, perhaps you have a TV connected that’s doing this?

    0
  • Виталий

    Involuntarily, not only the blue indicator turns on/off, but also the entire touch panel. And the TV is not connected to node130

    0
  • Виталий

    Experiments have shown that if you disconnect the RCA cable from my active Triangle, then the disco on the touch panel ends. When you connect the speakers again, everything starts again. I have already read in this thread that other users had the same thing. Haven't they fixed it in a year?

    0
  • Seppi Evans
    Hi-Res

    ^^^
    Your issue is quite different as using active speakers, your symptoms / fix suggest there might be an earthing / noise issue locally. You could try using an optical cable as this would then isolate the speakers from the Node.

    0
  • Виталий

    This is strange, because previously there was no such problem for 7 months of using node 130 in conjunction with these speakers. False activation of the touch panel appeared only a week ago. Moreover, I like the sound of an RCA cable more than an optical one.

    0
  • Seppi Evans
    Hi-Res

    Perhaps try another coaxial cable, you can use any interconnect for the test and not a cable sold as digital.

    Beyond that best to log a support ticket with Bluesound, from the Bluesound App select help, Send Support Request.

    0
  • Виталий

    I have already written to the support service. They reply that they are aware of the problem and will try to solve it in the next system update. It's like a year ago. Thank you for your advice!

    0
  • Dzmitry Mikhnevich

    Same blinking with my new node (mains voltage is 220V in my region, the node is plugged directly into the wall socket with the supplied 2 pins cable) on the latest firmware. Blinking goes away if I disconnect RCA cables going to the amp from the node. Doesn't matter if the amp is on, in standby or off. I don't want to switch to a node digital out as the node seems to have a better DAC than my amp, at least for my taste. Had to switch the sensor off as for now. Would like to get an option just to switch the lights off even when the sensor is not in use. Looking forward to bluesound deal with this issue. 

    ps. submitted a support request from the app and linked this post there.

    0
  • Dzmitry Mikhnevich

    upd. I replaced the stock power cable with an Audioquest one (x2-c7). It helped a lot, the issue with lights turning on is not completely gone, but became far less often with the new cable.

    0
  • Seppi Evans
    Hi-Res

    Interesting, try pulling out the Audioquest power cable and turn it 180 degrees and insert it back in and see if that changes the behaviour.

    0
  • DK

    I have the same problem with waking the panel. Having to buy a power cable for 65 euros does not seem to me a serious solution to this problem.

    0
  • Dzmitry Mikhnevich

    The issue came back even with another power cable, even without RCA plugged in (I switched to using digital output with a coax). Switching the phase (by turning the plug 180 degrees) doesn't help. 

    0
  • Gerrit Deppe

    Solved the issue by having node connected via LAN as  t h e  o n l y  device plugged into the switch.

    As soon as I added another device to the switch the issue came back. It is fine for me now since 6+ months. I informed BS support about the solution.

    Nothing else helped. No experience with WLAN connection on my side. 

    0
  • DK

    Using a good power cord doesn't change anything. Only after unplugging the RCA cable (and also of a higher class) - the panel does not wake up. So I only work through COAX. Apparently, after disconnecting the RCA cable, the Node sounds better with COAX. Do you confirm it?

    0
  • Meziane

    Hello,
    Like the message from Vytis 1 year ago, I encounter the same problem after some time following my purchase and with the latest firmware installed (3.20.25), it's crazy as a problem because without RCA the
    proximity detection works but I need these outputs to connect my Cambridge amp!
    Help, quickly a serious solution the Bluesound team!

    0
  • Manuel

    Good morning, I have the same problem, if I connect my Rotel amplifier to the RCA outputs, the lights turn on and off continuously. I have tried with rotel amplifier, pioneer and active speakers with the same result, if I disconnect rca cables everything works perfectly. I have tried with 2 bluesound node 130 units with the same result.
    I have the latest firmware 3.20.25 to see if there is someone who can help.
    Cheers

    buenos dias, tengo el mismo problema, si conecto a las salidad rca mi amplificador rotel las luces se encienden y se apagan continuamente. He probado con amplificador rotel, pioneer y altavoces activos con el mismo resultado, si desconecto cables rca todo funciona perfectamente. He probado con 2 unidades bluesound node 130 con el mismo resultado.
    tengo el ultimo firmware 3.20.25 a ver si hay alguien que pueda ayudar.
    Saludos

    0
  • DK

    Hello. Today I noticed that the panel is cyclically waking up again. And it's only connected via COAX. Maybe the last update broke something. It's starting to look like a circus...

    0
  • Manuel

    Buenas noches, parece que solo conectandolo por fibra se soluciona lo de las luces. Cualquier otra conexion activa las luces aleatoriamente, voy a ver si puedo obtener un reembolso por que parece que estas unidades estan defectuosas y no van a poder solucionar el problema.

    Good evening, it seems that only connecting it by fiber will solve the problem with the lights. Any other connection triggers the lights randomly, I'm going to see if I can get a refund as it seems these units are faulty and they won't be able to fix the problem.

    0
  • Gergely Voros

    I am using fiber and it does not solve the issue for me.
    But after I remove the Node from power it seems to be better for a bit.

    I could live with this issue and disable the proximity sensor with the leds always on.

    The only thing I do not really wan’t is that my Node is coming up from standby all the time (even with the sensor turned off).

    Is there any standby indicator I could check?
    Can the “vacation” mode damage my device if I use it as shut down?
    My recommendation would be to at least create a hibernate setting so I could set the Node to go to “vacation” mode or do not check on the network in certain periods (during worktime and night).
    I also hope that in the next update we can configure the top panel to stay off when the proximity sensor is off.

    I do not look at this issue as a huge consumer problem but it is not environment friendly!

    After 2 years of development I think the community should at least see the planned date for this fix or the planned release of a workaround.

    0
  • Tony W.
    Product Support Manager

    HI Gergely

    We have been able to resolve most of these issues with the proximity sensor. If you are still having issues, please select Help, Send Support Request so our Support Crew can review your log file and find out why you are still experiencing issues.

    0
  • Gergely Voros

    Hi Tony,

    I've got the same copy and paste answer about a possible fix in an update. I think I was the only one who checked on the uploaded logs.

    I also contacted the distributor and they also said that as it is only a bug, they can't replace the product or give my money back.

    0
  • DK

    Hi. It's sad, but the manufacturer can't control his equipment...

    0

Please sign in to leave a comment.