2nd part…
What will actually resolve it:
· Where you need whole-home synchronised groups, the WiiM endpoints really do need a wired connection. Grouping Wi-Fi endpoints with wired zones is the specific combination that fails.
- -> This won’t be possible, as I don’t have a wired network connection everywhere (I have plenty in some rooms, but not in all of them ;-), a planning error :-)), and in any case, it won’t be possible any time soon, as my electrician would first have to lay cables, which would als o inc u r further costs .
· Your laundry repeater is running on a wireless mesh backhaul, so any audio endpoint behind it is effectively two wireless hops from the router, the hardest case for RAAT. I’d avoid placing audio endpoints there, or give that repeater a wired backhau l.
- -> I’m fully aware of that, and I’ve recognised the problem. The electrician and I are looking for a solution that will allow us to run a cable to the repeater as easily as possible. It’ll take a bit while, though, b efore we’re ready
.
· On the FritzBox, set a fixed IP (DHCP reservation) for each Roon endpoint. We can see at least one device has already changed address between captures, and re-addressing forces Roon to re-establish connecti ons.
- -> That’s exactly what I didn’t want! What I want is for a central device to handle the DHCP, so that I don’t have to manage the DHCP addresses. It’s a right pain and time-consuming. Yes, perhaps only when setting it up for the first time, but when troubleshooting problems it’s always a hassle and, to be honest, I dread network problems as my technical knowl edge is limited.
On your restart question, this is a great observation, and the behaviour is intentional.Your zone groupings, settings and library live in the Roon Server database, which is persistent by design; a restart is not meant to reset them, so nothing is stuck or corrupted there. What a restart does clear is the transient, in-memory state, the live audio connections and device discovery. So retained zone groups after a restart are exactly what we’d expect. One thing worth mentioning: the logs for this period show the Roon Server software itself started only once, so whatever restart you’ve been performing may not be cycling the Roon Server process. In practice, if you want to clear a stuck audio path, power-cycling the endpoints (the WiiMs / repeaters) tends to help more than restarting the s erver.
-> I see. I can understand this explanation too, and yes, from this perspective, the behaviour is of course correct and is also what I, as a customer, would expect. One question on this: if I restart the device, won’t it obtain a new DHCP address if it d oesn ’ t have a predefin e d one?
If you run the test above, share the result and we’ll take it fro m there.
I’ll probably have a proper look into it at the weekend and will be happy to get back to you. Thank you very much again for your support. I’m looking forward to working with you to find the cause. I’m currently learning an awful lot
Bes t regards ,
Remo
