Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Bell Home Hub 3000
Core connected via Ethernet
Remote running on Pixel 3 phone (Android version 11, Build RP1A.201105.002) connected via wi-fi
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Not applicable
Description of Issue
There are times the remote app connects to the Nucleus Core from my Android Pixel phone and other times it cannot find the Nucleus Core; it just continues searching for it on my network.
There are times I can connect to the Core OS page from the remote app, yet can’t find the Core; it just continues searching for it on my network.
Nothing in my network or endpoints changed during these issues.
And during both instances, I was able to connect from a remote running on an IPhone.
I tried assigning a static IP to the Core but that didn’t resolve it. Cutrently,
For hard to diagnose reasons, Android Roon is very picky about how a local network implements multicast. Sometimes, turning off IGMP snooping, or turning on IGMP proxying on the router fixes the issue. Many of us worked with Roon over the years to try to track this down, but it is really hard to nail down. I had this problem for a while, but turning off IGMP snooping on a managed switch (Netgear) made it disappear, and I’ve not seen it again even though I’ve now two different networks with different routers and switches.
If you click on the “Help” button that appears on the searching for Core screen and type in the IP address of the Nucleus or the multicast IP of 255.255.255.255 are you able to manually connect to the Core this way?