My Node 2i is stuck on failed update (firmware 3.8.19)
Answered
Anybody else here using Node 2i having an issue upgrading to latest firmware? I think the firmware is 3.8.19. My node 2i failed to update last night. I tried doing the USB stick update and that failed as well. I emailed support asking if I can instead install the previous firmware (3.8.17) but got no response yet. This product sounds great but the reliability is a big issue. I sure hope I don't have a $500 brick.
-
Official comment
Hello Jose,
Please continue to work with the support crew to resolve the issue. We thank you for your continued patience.
Regards,
Sam R. -
Can anybody from support help me with this? My node 2i is dead because of this! I have opened support call # 191991 yesterday. They suggested doing a usb install. I tried that and that failed as well. I got no response from support today. Very frustrating. I've only had this for a few months and now it is useless.
0 -
Sam, I will try to be patient even though I have not heard from support the past two days. It is really infuriating when you have a device that was working perfectly then it gets bricked by an update.
0 -
I am having a similar problem in that my node 2i refuses to upgrade to 3.8.19. I also have a Soundbar 2i and it upgraded fine. For my node 2i it just sits there with the red light solid. Ive tried updating multiple times. If I go to the iOS app I see my Soundbar device working fine, but the node 2i device says “Upgrade Failed”. If I unplug the node 2i and plug it back in it recovers (but back to the previous firmware version). So fortunately for me this is not “bricking” the device, but it is annoying that it wont upgrade and I expect that if one device continues to upgrade and the other does not, eventually that will cause synchronization issues between them. So Bluesound please fix this.
BTW, it looks like a failure to download the update. Here is a snippet from the log:
Aug 15 02:57:01 (none) user.info stage1: Detected model: NODE 2i Aug 15 02:57:02 (none) user.info stage1: [error] curl: (35) error:1408E0F4:SSL routines:ssl3_get_message:unexpected message Aug 15 02:57:02 (none) user.info stage1: [warning] Download failed (status=35): n125/stage2 (retry 0) Aug 15 02:57:04 (none) user.info stage1: [error] curl: (35) error:1408E0F4:SSL routines:ssl3_get_message:unexpected message Aug 15 02:57:04 (none) user.info stage1: [warning] Download failed (status=35): n125/stage2 (retry 1) Aug 15 02:57:11 (none) user.info stage1: [error] curl: (35) error:1408E0F4:SSL routines:ssl3_get_message:unexpected message Aug 15 02:57:11 (none) user.info stage1: [warning] Download failed (status=35): n125/stage2.md5sum (retry 0) Aug 15 02:57:14 (none) user.info stage1: [error] curl: (35) error:1408E0F4:SSL routines:ssl3_get_message:unexpected message Aug 15 02:57:14 (none) user.info stage1: [warning] Download failed (status=35): n125/stage2.md5sum (retry 1) Aug 15 02:57:21 (none) user.info stage1: [error] curl: (35) error:1408E0F4:SSL routines:ssl3_get_message:unexpected message Aug 15 02:57:21 (none) user.info stage1: [warning] Download failed (status=35): n125/stage2.md5sum (retry 2) Aug 15 02:57:33 (none) user.info stage1: [error] curl: (35) error:1408E0F4:SSL routines:ssl3_get_message:unexpected message Aug 15 02:57:33 (none) user.info stage1: [warning] Download failed (status=35): n125/stage2.md5sum (retry 3)
0 -
Dave, how do you access the log? Have you tried updating via USB stick? So yours simply reverts back to previous firmware when you restart it? Mine automatically tried to run the upgrade again every time I restarted it then it just suddenly stopped doing it after several attempts. When I restart it now, the led just stays red and never changes. It's not doing anything at all.
This makes me nervous about this happening again in the future if I do get a replacement device. I certainly will not be looking at getting more Bluesound products anymore after this.
0 -
Sam,
I worked with support today to try and fix my node 2i. They could not connect to it so they ruled it as hardware issue. This does not sit well with me because my node was working fine until an update was pushed to it causing it to get stuck on endless update cycle. Shouldn't Bluesound be responsible for repairing my device since it was an update from the manufacturer that caused my device to fail?
0 -
Sorry to hear that. If it truly was a result of the upgrade then I agree. As a long time software developer though I would say never underestimate the power of coincidence...
Obviously 3.8.19 was buggy and just a few days later Bluesound posted 3.10.0. For me this new one upgraded fine. Only one problem. Blue sound apparently removed the ability to see the logs! This is a major disappointment to me because the logs help a lot, not only for seeing where the upgrade is having problems like I showed in the other post, but more importantly, it lets you see where it has problems cataloging local music due to filename anomalies, etc. I have over 30,000 songs locally and the logs are the only way Ive found to find and fix these kind of problems. Bluesound: bring back the log access!!
0 -
Node 2i i GARBAGE! DON'T BUY THEM! I HAVE HAD TWO OF THESE SINCE 12/24/20 AND THEY BOTH SUCK. Software is garbage, the first one i spent weeks trouble shooting why it can't play 24/192 hi res files without dropping audio. the second one i just picked up today and it can now play 192 files off my samsung evo ssd 4tb drive but couldn't finish the setup, can't add any network files etc etc etc... I have been in IT for 30 years.... GARBAGE!
0
Please sign in to leave a comment.
Comments
8 comments