I didn’t know exactly where to post this.
I just built up a new ‘server’ (Windows 10 Pro 64bit) and noticed that SageTV could not communicated with the tuner shortly after any recording ended. After days of diagnosing I discovered (using Wireshark) MCEBuddy was pounding the crap out of the Ceton with Upnp ‘requests’, thousands and thousands of coms being produced. After several minutes the tuner would start throwing error because it could handle all the requests.
It only seems to start after the first recording has ended after a reboot (or MCEBuddy.service restart), and then would not stop until MCEBuddy.service was shut down or the computer was rebooted.
After shutting off Upnp inside MCEBuddy everything worked as it should, and MCEBuddy.service stopped berating the Ceton.
The Ceton is on 192.168.200.1 delivering to 192.168.200.2. MCEBuddy is sitting on 192.168.1.26 (server ip) so I’m not sure why MCEBuddy is going nuts trying to communicate with 192.168.200.x.
Maybe we need the ability to bind MCEBuddy to a specific adapter or address?