Hi @DrCWO,
Moving my earlier post here as requested.
In an attempt to rule out some possible causes for my extensions disconnect issues I did the following:
Turn off Ropiee client to remove it’s remote control extension from Roon
Turn off the rooNuimo Pi to remove it’s extensions from Roon
This leaves just the rooDial (and corresponding rooExtend) extension in Roon
All music end points are Ethernet connected and none are streaming music
I powered down the rooDial Pi
I rebooted the Roon core server
I started a Wireshark packet capture to capture the IP traffic between Roon and the rooDial Pi
I powered up the rooDial Pi - which is Ethernet connected to the same switch as the Roon core server
At this point, there are no wi-fi connected devices, no music playing and the rooDial and rooExtend extensions are discovered by Roon (and no other extensions).
Now I simply waited for 2-3 minutes, playing no music nor changing anything in Roon
The rooDial extension disappeared from the list of Roon discovered extensions.
With only this extension active, it reinitialised much quicker than before and the rooExtend extension didn’t seem to disappear at all. A later test with music playing to the Roon bridge on the rooDial Pi didn’t kill the music playing, unlike before with multiple extensions active - presumably sufficient data is buffered to cover the much shorter outage?
In the rooExtend log, it just reports Error: socket hang up .
The message before that is minutes before when the rooDial got paired with CORE
In the Roon server log, it just reports Info: [roonapi] [apiclient 192.168.1.89:52920] disconnected
The messages before that are multiple instances of CONTINUE Changed {“message”:“Enter USB-Stick to save License Keys.\nTo restore the License Keys enter the USB-Stick with the saved License Keys before boot.”,“is_error”:false}
In the packet capture, I see Roon and the rooDial Pi chatting quite happily on 3 separate connections until Roon sends FIN,ACK & RST,ACK from port 9300. The rooDial Pi responds by sending FIN,ACK to port 9330 on the Roon server and the IP traffic ends until the rooDial Pi sends SYN,ACK to port 9330 to restart things once more.
So I don’t think this is a problem with rooExtend, the Roon server clearly ends the connection on port 9300, which terminates things. But why? And why does it appear to only affect my setup?