I occasionally have to updated a Sonos device DNI when the router decides to change its IP.
In the new UI I can edit the DNI field under Device Info, but the changes to that field are lost when I click Save.
If it's relevant, the Sonos device has been created by the built-in Sonos Integration app.
Does your router not have the capability to set a DHCP Reservation for the Sonos?
That's the easiest way to consistently keep it (or any other LAN device) on the same IP.
2 Likes
I'm not able to replicate this problem, including with a Sonos device. You might want to try a virtual device to see if something is specific to this device, though I'm not seeing that, either.
You might want to make sure you are on the latest platform version (build 146 as of my writing) and see if a different browser changes things.
Of course it does; I just don't want to do that across the multiple Sonos devices I have.
That's beyond the topic in question though.
I am indeed running the most recent version of the platform.
- Open the Sonos device page
- Select the Device Info tab
- Click on "Edit" for DNI
- Modify the DNI
- Click the Save or Save&Close button at the bottom of the tab
- The DNI goes back to its original value
Not sure what could be different in my environment; I am using Chrome.
It's best to name the specific platform version, but I'll assume it's the same.
Can you replicate the problem with a virtual device?
I can't with Sonos, and I don't see anything in the code that should immediately revert the DNI (it will if it gets an SSDP broadcast matching the MAC address of the device per the device data; even that should be the same as the new IP if that's what it is), but I asked because that would rule out something with this particular device/integration.
This specific device is running on a C8 Pro with 2.4.0.146.
No problem with a test virtual device.
That Sonos device is enabled and used in hub mesh; let me see if I can remove it from the mesh.
BTW, the same exact operation worked smoothly with older platform versions/UI versions...
Ah, got it; the new DNI actually conflicts with another Sonos device (which has changed as well). My mistake.
BTW, it would be useful if the UI showed a message making it obvious to understand that the DNI change has been rejected because it matches a different one...
Thanks for your help.
4 Likes
If your hosts do not change much, make the lease time long like a year.
make the lease time long like a year
It is, indeed; and it often survives the year interval as well. But in some cases some major shake ups in the networking end up causing the occasional change.
Now, in almost 10 years of this, this is the first time that a bunch of them suddenly changed at the same time; I guess the router got bored and decided to do something.
