Node 2i w/ 3.2.10 requires power cycle daily
Answered
Hello, I have a new Node 2i running BluOS 3.2.10. I am using Roon 1.6 on a Mac Mini and connect to the Node 2i via an 802.11ac network.
I am noticing about once a day that Roon will not connect to the Node 2i. When I try with the BluOS Controller.app, it also cannot "see" the Node 2i.
So, I unplug/re-plug the power, it boots up, and all is well... until the next day.
Here is the Diagnostics output, if that is helpful:
-
Official comment
Here is the Diagnostics output, if that is helpful:
Hi Ken
It is helpful, but not this way... that's why we send it auto-magically when you select Help, Send Support Request in the App.
What is happening is not that the Player is not broadcasting (pull up the Player IP in a browser without issue). What you are seeing is actually the App is not receiving. You do not have to reset your Player, Kill the App. That being said we are always looking for items in Network Discovery to improve the process. Double check your router and ensure mDNS (Multicast) is enabled. I would also look at disabling any QoS or WMM settings you might have on.
We can help with that via a remote session when you do log a support request through the App.
-
I think I know what's causing this: Qobuz.
I logged out of Qobuz on my Node 2i (Controller App) and the off-line problem is no longer occurring.
FYI...
0 -
OK, it's not from Qobuz... it's your wireless stack.
I spent the weekend playing around with this (adding Qobuz back in, connecting wired ethernet) and I am not observing the device crashing when it's connection is wired Ethernet vs. wireless.
I had also posted something earlier about the Node 2i's difficult making an 802.11ac connection, without rebooting the device before playback.
Anyway, something is seriously wrong with your wireless software stack... Good Luck!
0 -
"What you are seeing is actually the App is not receiving. You do not have to reset your Player, Kill the App."
The same behavior occurs with Roon - the device appears to be off-line, so this is not a problem with the BluOS app - it's the device.
"Double check your router and ensure mDNS (Multicast) is enabled. I would also look at disabling any QoS or WMM settings you might have on."
My router is an Apple Airport Extreme, which does NOT have any settings for mDNS, QoS or WMM.
I have plugged-in a wireless bridge (Apple Airport Express) and the problem is gone (for me, anyway).
1 -
This is still a problem. I have to power cycle my Node 2i in order for my controller s/w to recognize the player. For a company that charges a premium pri e for their products, the interfaces are very buggy and support is poor.
0 -
Hi PSmalley
I have escalated you to our Support Crew - they will be in touch in a day or two via e-mail to help walk you through some tips and tricks such as DHCP reservations to ensure the high-quality audio you are paying for is getting through to your players.
0
Please sign in to leave a comment.
Comments
6 comments