Hello @Stefano_Lanfranchi,
Thank you for the clarification. Based on the diagnostic patterns we see from Innuos systems, your symptoms strongly match system-level issues inside the Innuos OS, not a Roon or Tidal problem.
Here are the three specific issues visible in your logs:
1. Network stack failures inside Innuos
Your system repeatedly fails to bring the network fully online, even though your home connection is excellent:
Dec 2 06:26:32 systemd-networkd-wait-online[17936]: Event loop failed: Connection timed out
This causes slow starts, interruptions, and premature track skipping.
2. Innuos internal service restarting every 6 hours
A critical Innuos component (myinnuos.service) keeps crashing and restarting:
Dec 2 11:52:14 systemd[1]: myinnuos.service: Scheduled restart job, restart counter is at 11.
Each restart disrupts Roon’s audio pipeline, resulting in playback stops and next-track switching.
3. DNS / network refresh events triggered by Innuos
Your unit is firing internal DNS change notifications unexpectedly:
Dec 2 00:53:51 start.sh[30268]: DnsChangeNotifier::DnsChanged
These events can momentarily break streaming sessions.
What to do next
Please reproduce the issue again and let us know:
- the exact local time of the dropout
- which zone was playing
- which track/album you were streaming
This will allow us to match your timestamp with the diagnostic logs.
Also, since the motherboard was recently replaced, please perform a full power cycle of the Innuos unit (shut down → unplug 2 minutes → power on).
If the issue continues, we may need to involve Innuos Support, because the log entries above show problems inside the Innuos OS rather than Roon.
We’re here to help — just send us the next timestamp and we’ll continue the investigation.