button on Naim remote > Network Settings > DHCP
Then toggle DHCP off / on. Streamer will (hopefully) reconnect without needing to power down.
1 Like
Must be frustrating…
So I might be able to suggest some things to look up,
1 can you say why you think the 272 is dropping in and out of the network… what is telling you this, and how long does it take, does it have a new local IP address when it reconnects. Is music play out interrupted?
2. What do you connect your 272 to on your home network, and how does your wifi connect to your home LAN Ethernet, and what is it.
3. What do you use to control the 272 app… iOS/ android etc
You see your 272 could be fine, but a mobile device on your wifi is having difficulties with the data protocols being used.
BTW don’t fiddle around with dhcp… leave it on… only go there if you have a faulty dhcp server on your router… kind of very unlikely… what is your router. Usually best to use an isp supplied router(certainly if with quality isp) unless you have a specific reason not to.
Ah thanks that would be a piece of cake but my NDS screen is dead so not sure I can do that.
Last night my 272 stayed connected all evening, apart from the usual reboot of 272 and BT hub, the only other change I made was when I logged into the BT hub, I noticed an icon labelled smart connect. I’ve never noticed this on the hub before so I engaged the icon. Not sure if this made a difference or not, but the 272 did stay on with no dropouts last night. I’ll see how it fares today.
Doable in theory if you carefully counted the number / direction of clicks on the remote — the Naim equivalent of Morse code 
Removing / reinserting the streamer’s network cable achieves the same results. Preferable to constantly turning hardware off & on?
1 Like
Hi all,
I’ve just checked with the necessary teams and we’re not seeing anything unusual going on with the last release. There are a couple of more niche cases on Tidal that need fixing on next build but overall holding together pretty well.
In the case of @Kompressor1 it indicates he’s on older code and hence that is at least 3 years old and very well proven. It indicates that is a localised fault that is going on.
To ensure issues are on the radar make sure support tickets are raised with Naim. Ultimately if there are issues that are down to a bug or compatibility issue we’ll fix them. As proven from this last code release, we are still supporting the older products, some of which go back 11yrs now.
On a side note, I have looked at a couple of cases in the last few months and they ended up being hardware faults. Some of these products are getting very old and some electronic components are starting to fail (inherent in any electronics if you make enough of them). Again, our helpdesk is there to help break down the problem.
With regards
Steve Harris
Software Director
Naim Audio Ltd.
2 Likes
Can I ask about this, I’ve not been successful with the current software update. My problem seems to be obtaining the necessary driver to install the upgrade. When I have tried to get the driver, I have an error code telling me the file is no longer available or has changed the file name.
I will add since ticking the smart connect icon when logging into my BT hub the problem seems to have resolved itself, but it is early days, only a couple of days has passed since the change.
Is it PC or Mac drivers you are wanting? If it’s Mac, what OS are you running?
Windows
Ok so you are using these instructions?
There is a link in there for the download site for the drivers and I checked just now and it’s working for me.
The download site is
http://www.silabs.com/Support%20Documents/Software/CP210x_VCP_Windows.zip
I suggest try again. Maybe the site was down when you tried before.
- The 272 (latest firmware) is dropping b/c it disappears from the app and does not come back unless I cycle the power on the 272.
- The 272 is connected by wire to the last cisco catalyst PD (POE) switch in the network. My Muso v1 is connected by wire to the first cisco catalyst PD switch in the network. And the first cisco catalyst switch is connected by wire to the Amplifi HD router (latest firmware) and the router is connected to the ISP modem. All network connections are via BJC Cat6A.
- Apple iPad Pro via wifi latest firmware.
I didn’t have this issue prior to the latest 272 firmware update and my current network settings/set up are unchanged from the previous firmware where I had no issues.
Known use case that causes the room to drop occurs while in multiroom and I choose a Hi Res file (by mistake) from my NAS or from Qobuz. In the past the file would just not play and after exiting multiroom I could get the track to play. Now, the app just drops the room entirely. Obviously I can avoid this by not choosing hires files while in multiroom but sometimes I forget.
I also will get a room drop from less obvious scenarios where I’m in the app and I choose a track then quickly choose a different track. Or I choose a track from the NAS (asset upnp) and then quickly choose a radio station from a playlist (Minimserver upnp).
These room drops are mostly rare and avoidable but still a pita nonetheless and a new problem since the last fw update.
1 Like
I think it has been reported before that some BT hubs have 5GHz wifi and 2.4GHz wifi networks which communicate with the outside world but not with each other. I have experienced that myself. Check if your phone or tablet is connecting to wifi on the 5GHz network some times, usually when you are within line of sight of the hub. In that case, it may not see your 272 which is on the 2.4Ghz net or ethernet. You can turn off the 5Ghz network, putting your phone and 272 on interconnected networks, and you might find this is the solution.
I have had similar issues with my NDX, running latest firmware. I did try switching off router overnight, which apparently generates a new IP address from the ISP (got this from another thread on here). That totally sorted it for a week, then it’s started coming back. One thing that did seem to work for me and others on that thread was cycling inputs to iradio, which prompted the NDX to re-initialise and then come back online. I’m using a Google home mesh network, with NDX plugged into one of the Google hubs, though I had the same issue previously when plugged directly into the router itself.
This issue was fixed months ago by a firmware update to the BT hub.
I have an earlier BT Home Hub 5 and it has not had a firmware update from BT for a couple of years. It would still show this problem, but I use whole home wifi disks to avoid it.
BT Home Hub 5 (Type B) | Software version v0.07.08.25060-BT | Last updated 23/6/2020
A number of people here have had problems using Google mesh devices because they run a DHCP server which cannot be disabled, so if you also have one running on your router they will inevitably cause conflicts. Maybe something you could investigate as the issues you are experiencing could be symptoms of this issue.
I hadn’t thought about cycling the input to iRadio. I’ll give that a shot next time. Thanks for the suggestion.
Ok, thank you. So this only happened with the latest firmware update.
Ok well that does suggest firmware… essentially the 272 has to advertise to the network (and your app) that it is a UPnP player device. A specific protocol is used for this typically related to a multicast discovery (SDP). If these messages are interrupted by a deficiency in the home network equipment or app operating system (used to be quite common a few years ago and Android used to be more problematic ) or the host (the 272) is not sending the responses back or keeping membership of the discovery group (IGMP) then the host (the 272) will disappear from the app, even though it’s still on the network.
The fact this behaviour changed after the firmware upgrade suggests the firmware / device… as such you should progress with Naim support. Also the fact it works after a powercycle, possibly suggests group member ship methods or algorithm is not working as well as it should.
Underneath the covers to provide flexibility for different home networks, there are negotiated options, so your issue might not apply to everybody as they have different home networks.
Simon
1 Like
It’s worth reading Steve’s post on this very point Simon…
indeed thanks - I saw that - hence the recommendation to liaise with Naim support - and what goes on underneath the covers