Node 2021 LED Light switch on randomly
Answered
Hi All,
I've already returned one unit with this problem and I now have a similar issue on my replacement. (Support concurred that there seemed to be an issue)
The top panel LED randomly switches on despite me not activating the proximity sensor. Has anyone else experienced this issue? Although not as bad as the first unit, I'm perplexed.
Unit works without issue otherwise and Bluesound support has been excellent. I was just wondering in case I was missing something. (Tried all the resets etc for problem shooting).
-
Sadly in the same possition.
0 -
Hi, I have a similar problem with my N130. My blue light led on top and in front are always on (set to dimed or normal positions no difference) but top touch panel with presets buttons and volume control arrows turns on and off randomly, every 5-10 sec panel lights up, for 5 sec and then again, at that time the top and front led illuminate without interruption. If I set blue led light to off, then top panel led, front led and touch panel switching on and off all together.
2 -
Quote :- Tony W. - Product Support Manager
Our QA and Engineering team is investigating an issue with the front LED pulsing on the NODE N130 in conjunction with the proximity sensor periodically being triggered by a false positive randomly turning it on such as light from a window or a plant in proximity then turning off at a regular interval - we hope to resolve this in software in a very near-future release.
This was 2 months ago, any news ?
1 -
@Andrea Crema
in the end you already quoted it :
"we hope to".
Nuff said - probably working already on a successor of this device.
0 -
... they keep selling the faulty device.
1 -
Marcel
in the end you already quoted it :
"we hope to"
Nuff said - probably working already on a successor of this device.
———————————————————
Its either yes or No. If “No” then I will require a refund.
0 -
Andrea Crema I already tried this in Germany/Austria. Bluesound Europe says that they are not aware that this is a hardware issue. Also after I provided screenshots from here. I guess they are afraid if they refund one then they have to refund all the others as well.
0 -
Hi to all, I have spent a lot of time, asking them to refund my node and they refused. The logic was since a lot of them were/are defective, even if they would replace it, most probably I would get a faulty one. Of course, they denied it.
Lesson learned. Unfortunately, the only solution is to buy all electronics (the ones you can find) from amazon. Return it back no questions asked. Leave a negative rating.
My experience with bluesound is one of the worst I have ever had. I cannot do anything about that, my bad that I spend my money on them.
2 -
George Chatzidakis
I second all of your lines.
0 -
They either fix via firmware or there has to be a product recall.
0 -
had the same problem when i plugin to powerquest Niagara 1200 or powerquest ac power conditioner.
When connect diract to wall power outlet the NODE works fine0 -
Sorry audioquest
0 -
@Jimmi Hansen
Thank you for your input. I double-checked and it makes no difference for me.0 -
Hi guys,
I did a big investigation of this "blinking". In order to understand this in my system, I tried everything, changed the location of NODE (as you advised), changed the cables, connection types, etc. So now I will try to describe what is going on.My system:
NODE - DAC (Cambridge Dacmagic Plus) - AMP (Cambridge Audio Azur 851A) - Speakers (B&W 603 S2)
Connections:NODE - power cable, ethernet cable (tested WiFi and and cable only - no difference) , coax cable to dac
DAC - original power source, coax cable from NODE, rca cables to AMP
AMP - Power cord, rca from dac, speakers (all the rest was disconnected for tests)
So first I noticed that blinking stops when i disconnecting coax cable from DAC to Node and no matter which side - DAC or NODE. Then I decided to skip dac and connect the node directly to amp via RCA cables (coax cable was removed so no connection with dac at all) - and blinking STAYS UNCHANGED!!!!! And after many tries I have found that this phenomenon is caused by my integrated AMP (amp is in perfect condition - no bzz, fzz, or other issues noticed). Most interesting thing is that blinking stops ONLY when I remove a power cord from the AMP!!!! No other conditions affect this - COAX or RCA, DAC on or off, AMP on or off (even when the main power switch on the back of AMP is off) - no power cable to amp - no blinking, connect power cable back at the same moment blinking starts. Who can explain to me, how that mystical signal which affect proximity sensor on NODE can travel from AMP via RCA cables to DAC and from DAC via COAX cable to NODE even when AMP and DAC both are switched off??????? (Cambridge DAC has only a physical power button so when it is off its mean OFF!)0 -
I have noticed that the blinking is almost constant when NODE has connection to earth ground (to earth referenced equipment) via either RCA, COAX or USB. On my system using TOSLINK optical connection between NODE and DAC makes things better. Then blinking is not completely gone but there are only some occasional false activations of the proximity sensor.
Vytis physical power button does not disconnect the ground, only unplugging the power cord does.
0 -
Hello
I had the same problem. When a put the rca cable, the light of the node 130 switch randomly.but not to bad. It’s happen some time but not continually. When a put the toslink connection, all is fine.
I don’t want to return my Node and have a new one with the same issue.
My Node 130 work perfectly with great sound and great app.
I hope a solution nearly.0 -
Hello again,
Yesterday I submitted a post with similar problem. The light of my node 130 switch randomly.
Today a tried a experiment with the node. I simply disconnected the electrical outlet of my Triangle active speakers. The node is connected with rca cables on it. And……..
the problem disappears. No light switching on it. Only the littles bleues lights.
This is the solution for now. Always waiting for a other solution. Hope nearly coming soon.0 -
Hi,
I picked up a current (gen 3) Node this week. It is exhibiting the same random false positive from the proximity sensor and the top panel lights are turning on/off at random intervals. I have tried all of the solutions mentioned above, no rca connection, no coax sp/dif connection, wired/WiFi, no external connections at all just power, different locations, different material supports / stands and NOTHING makes a difference.
This unit also makes a 'pop' noise when switching between streaming sources when using the analog RCA outputs. I very much like the design and concept of the Node, but it appears that there are some significant hardware issues with this generation.
It looks as though this unit will be getting returned, unless Bluesound want to chime in with a 'fix'?
0 -
No news now for long, i consider all pretentions of "we are working on a fix" as a bad marketing-related lie to calm down people.
They put their ressources already in next generation of devices, you can be pretty sure of that.
I will spread these experiences as necessary, its has to be noticed what a buggy piece of hardware they delivered.
0 -
Just received BluOS update 3.14.31 to my NODE N130. No improvements regarding this issue.
To stop the blinking you can switch off 'Proximity' in the player settings. Then the panel lights are always on. In settings there is 'Indicator brightness' with values Normal, Dim and Off. The Off setting does not do anything (seems to be identical to Dim). Probably another bug. 5th that I have found .
0 -
Hi jkan, I raised the same point with bluesound support and this was there response:
After speaking with our engineering team regarding the specific issue they have been able to replicate it here in our labs. Our engineering team will be looking into this further and be providing a fix for this issue in a future firmware update.
In the meantime, if you wish to turn off the LED on top of the NODE (N130), then I would advise pressing and holding down the blue circle button (i.e. the play/pause button) until the LED turns off (as mentioned in your previous email).
Hopefully this helps, and thank you for your extended patience with us in advance.
Take good care and stay safe,
Eric W.
BluOS Support Crew Analyst.0 -
@Paul Reeve
What does it actually do? It's not documented in the manual.
0 -
It puts it into standby. To switch it back on just tap the same button, just for a second, and its backup. I have noticed that the majority of times it immediately continues playing songs in your playlist. You might not think this is much of a problem, but if it's early in the morning and you want to listen to the news, having Royal Blood (for example) blaring out is a shocker. I've found it better to switch it off this way, especially when watching films, having not to watch out the corner of my eye the node light show.
0 -
Hi everyone! Finally, the issue seems to be solved with todays update to BluOS 3.16.1. Thank you!
0 -
It has been 5 months since the OP posted about this problem. I have returned my unit for a refund. It's a pity that Bluesound weren't a bit quicker to resolve this issue as it is now unlikely that I'll ever buy another Bluesound product. C'est la vie.
0 -
I've applied 3.16.1 update this evening and can confirm it has fixed the problem as Martin previously suggested. No annoying flashing lights - at least for a week until the wife puts up the Christmas tree.
1 -
This is a very long time with no comment, no update and no firmware.
Apart from this annoying bug(s) with LED flicking on randomly and not being able to disable the proximity sensor, where is the fabled USB update for audio.
I have to say for all my years in HiFi I've never seen such lack lustre support. A fan of Bluesound I ain't at the moment
0 -
Thank you for your patience Andrea (et al)
We are thrilled that our engineering team was able to find the root cause of the issue and provide a solution via firmware. Unfortunately not all software bugs are in fact easy fixes - this is an example of one that took some time to find.
0 -
Many thanks Tony,
Can it be the case that this week´s firmware update 3.16.1 already solves the issue. For me it seems to work fine after the update.
1 -
That was our goal - we are pleased to see it did, not only in testing but in the wild as well.
0
Please sign in to leave a comment.
Comments
91 comments