Big problems with iOS Controller Connectivity
Answered
Hi from Germany,
I have big problems with the connection of my iOS controller app with my new Node 2i.
If the Node is playing something and I start the controller app, the app sometimes does not show what is just playing and I cannot control the Node. If I then swipe to my music sources, only "Settings", "Help" and "Add Player" is choosable. The player is visible. After restarting the app once ore several times everything is ok again. This strange effect occurs with 3 different iOS devices but not with an Android device. My dealer gave me another Node, the same problem. The Node is connected with a LAN cable.
What I have already tried:
- Updating router and Node
- Resetting router and Node
- Varying several router settings
- Varying several iOS WiFi settings
I urgendly need your support. Below you can find screen shots.
Kind regards, Thomas
-
Official comment
Hi All
Thank you for your continued patience. Please look for an update to the BluOS App for iOS (version 3.12.5) to be released later this week to resolve this issue.
We do apologise for the inconvenience. -
Hi Thomas,
could you let us know your network setup in more detail. So which network components do you use ?
Does switching off and again on WiFi on the Apple device help?
Btw. the iPad OS version seems more sensitiv to me too, but I am still not shure if it is related to one of the last iPad OS updates or really the BluOS app on my iPad. But it’s not often and little different issue.
0 -
Hi Stefan,
that you for your reply.
My WiFi setup is quite simple:
- 1 Node 2i connected via LAN
- AVM Fritz Box 7590
- 1 repeater AVM 1750e (disconnected it already for testing reasons)
- 1 iPhone XS
- 1 iPhone X
- 1 iPadSwittching off and on does not help. Tried it a lot.
Regards, Thomas
0 -
Hi Thomas
Please select Help, Send Support Request once the player returns to the App - it may take a minute or two. We will need to take a closer look
0 -
Hi, I sent the Support Request again via the Conroller app. What will happen now?
0 -
I have the same issue. Periodically cannot connect to my Pulse2 from my iPhone 12, iOS 14.3, but I am able to connect to the player's web interface in Safari by IP address, so I know that the connectivity is ok. I am also able to connect to the Pulse2 via the BluOS controller on my Macbook whenever this happens.
I have tried power cycling the player, and turning wifi on/off and airplane mode on/off on the phone, no luck getting the iOS controller to connect. Can someone help?
0 -
Hi All
Our QA Team has replicated this and is looking to resolve it quickly - thanks for your patience.
0 -
I also have this problem, I just got this Bluesound Node 2i and its always not connecting to Tidal Connect, this is very disappointing for such an expensive device, can you provide update when this will be fixed please
0 -
Hi All
Thank you for your continued patience. Please look for an update to the BluOS App for iOS (version 3.12.5) to be released later this week to resolve this issue.
We do apologise for the inconvenience.-1 -
I look forward to testing this at my home as so far my experince on IOS has not been good , with an Android Tablet it appears better.
0 -
I've downloaded iOS BluOS app version 3.12.5, but still experience the same issue; NAD M10 not visible in BluOS app. A few minutes later it is visible, and then not. M10 is UTP wire connected, so no WiFi issue. Als I experience this issue both with my iPhone 13 Pro as well as iPad Pro
0 -
In my case all clients can access the Node 2i web server and iPhone widget is working but the BluOS application can't see any players in the network. It does not matter if Node 2i is having wired or wireless connection. The setup is currently totally unusable.
Clients: iPhone 11 Pro (MWC62FS/A), iPad Pro (MTXN2KN/A)
iOS/iPadOS: v14.4
BluOS: v3.12.5
0 -
Esa Kiiski,
your issue sounds like an Multicast issue. If players are connected to the network and you can reach the webinterface, but the discovery of the BluOS app can't find the players this sounds like not all communication can happen in your network.
Do you use AirPlay in your network, for example to an Apple-TV? if so, does that work?
Littlebit strange is that the iPhone widget seems to work, but maybe the communication was limited and got broken after some time. I saw network setups where the multicast traffic was limited so it worked for a short time but suddenly it stopped.
If you try to make a AirPlay connection, do you see the Player there?
Did you try to restart the Node 2i, did that help?
Did you try to disable WiFi on your iPhone and/or iPad, wait a short time and enable it again?
Did you try to restart your whole network (switches and accesspoints)?
1 -
My Node 2i seems to now be working better after that last IOS release, one thing I found was the Wifi strength needs to be fairly good, I moved one of my extenders and that seems to have made things so much better. Also seems to that Tidal Connect works now.
0 -
Thank you for pointing out the Multicasting. It seems that Ubiquiti APs won't allow mDNS/Multicast/Broadcast across radios (2.4G/5G) by default. They also seem to block mDNS/Multicast/Broadcast across 5G radio and LAN (eth). As long as client devices running BluOS Controller application are connected to 2.4G radio, everything seems to be fine. Of course, this can't be the final solution. Have to run some deeper inspections by running Wireshark etc.
EDIT: If somebody with Ubiquiti APs is struggling with this issue, please check that you don't have "Auto-Optimize Network" setting enabled. It will kill Multicast and Broadcast traffic. That option might be switched on automatically after the firmware update of APs. After disabling the "Auto-Optimize Network" the BluOS Controller application seems to work with all my mobile devices no matter in which WLAN radio (2.4G or 5G) they are connected to.
0 -
I had also been struggling with this issue for some time.
I also use Ubiquiti AP’s. 3 in total all hardwired to switch.
Turns out for me switching off “Uplink Connectivity Monitor” in UniFi has solved this intermittent connectivity issue which I was experiencing on some of my devices.
Note I did not have “Auto-optimize Network” on when I had the issues and I still have that switched off.
Hopefully this helps some people out that are experiencing this issue.
1 -
Thanks for the possible fix for the Unifi problem. I have had the same issue and just disabled the “Uplink Connectivity Monitor”. Seems good so far, but time will tell.
0 -
Dean Nurscher I have the same issues but don't see the "Auto-optimize Network” setting as an option in my Unifi Controller. Where is this setting?
What kind of controller are you using? Mine is just locally on my PC perhaps this feature is only tied to USGs and dream machines?
After I disabled "Uplink Connectivity Monitor" Airplay and things went back to normal but a minute or so later back to the same issues, no airplay and no connection to the player from the app :(
0 -
Hi Matt,
I noticed that I couldn't find the "Auto-optimize network" feature in Unifi recently. Its either been removed or moved elsewhere but I can't find it.
To be clear, I never had that feature turned on when I was experiencing connectivity issues with Node player.
Turning off the "Uplink connectivity monitor" is what fixed my issues. I was experiencing random inability to see the player in the app (while at the same time I could still connect to the player by its IP address from a browser).
To date I have not had an issue connecting to player from app at all since turning off uplink connectivity monitor.
Dean
1 -
One thing I just noticed is Multicast DNS was not enabled on my UNifi Controller, I enabled it and it seems I can at least play music again!
I hope this combined with the Uplink connectivity monitor fixes my issues.
0 -
On the iOS Unifi app, the Uplink Connectivity Monitor setting is under Settings-> System Settings -> Controller Configuration. Disabling this fixed the issue for my BluOS devices. I hadn’t even realized, but my Ring Chimes were also not working because this setting was enabled.
2
Please sign in to leave a comment.
Comments
21 comments