Two Node N130's not working subsequent to latest update
As of now both have been blinking red and green for 3-4 hours. We have a gigabit fiber internet connection which is working correctly and both nodes are connected via ethernet. Please advise. Thanks!
-
Offizieller Kommentar
You can power them off, just try one again connected directly to the Router if you have other devices in the chain or even WiFi if the signal is good enough where the NODE lives.
If this does not help then use the BluOS App to send a support request.
-
T hanks. both are connected by gigabit ethernet to the router. tried shutting off ac and restarting, has not worked. I have been a node user since v1, and while this has not happened many times, neither is it the first. I think Blueound needs to look very hard at how to make their update process more fault tolerant, improve backup of configurations for each device, and also think very hard about not forcing updates at all.
0 -
Hi Rober
I have escalated you to our Support Crew for a closer look.
0 -
I want to update this and provide some useful diagnostic info. Subsequent to my last post I brought a 3rd node, which we use as a spare, to our home overseas and connected it to the network with the same result as the first two - detected upgrade, upgrade tried to run, unit got stuck on flashing green/blue and would not come up. Three dead nodes. However. In diagnosing some other issues I also noticed that the DNS proxy service we had been using for some years had stopped working recently despite the fact that we had made no configuration changes and the account was current. (yes I had also bounced everything - fiber unit, routers, access points.) After not receiving any replies from the DNS company's tech support for several days, I ripped it out. After that I re-connected the dead Nodes one at a time and each one then finished the update and recovered itself. So the good news is: What happened was caused by some sort of issue related to that DNS proxy service; what it was I have no idea. But. I also want the Bluesound people here to know that in the process of getting all this figured out I had also thrown into my suitcase a Wiim streamer, which, when connected, detected an available update, installed it, and had no problems. This suggests that Bluesound has more work to do in ensuring the robustness of their upgrade process, and I would also suggest that, assuming upgrades have to be applied at some point, that the user be given an opportunity to delay it for MUCH more than 24 hours. If we had that ability I could have told my poor wife to simply delay the updates until I arrived and could be there to get things unraveled. At the very least one month, but preferably more. 24 hours is setting things up for trouble and customer dissatisfaction. had my wife been able to delay the updates by a few weeks i would have been there when they ran, figured out the problem pretty quickly, and recovered the Nodes without having to parry requests to move us to a different platform. So, please prioritize this change!
1
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare