Weird Behavior (Backup myServer)

I've been playing around with my backup server and am seeing this behavior.  The Tivo driver on the secondary server finds and connects to the Tivo, however the commands are not recognized when sent (they send fine) and once sent I see device-connected and then disconnected in the logs.

31/01/2025 10:14:31.14 · DEBUG · Tivo.NetConnect - Device Tivo 192.168.2.180 has connected. 
31/01/2025 10:14:31.14 · DEBUG · Tivo.NetDisconnect - Device Tivo 192.168.2.180 has disconnected. 
31/01/2025 10:14:41.14 · DEBUG · Tivo.NetConnect - Device Tivo 192.168.2.180 has connected. 
31/01/2025 10:14:41.14 · DEBUG · Tivo.NetDisconnect - Device Tivo 192.168.2.180 has disconnected. 
31/01/2025 10:14:51.14 · DEBUG · Tivo.NetConnect - Device Tivo 192.168.2.180 has connected. 
31/01/2025 10:14:51.14 · DEBUG · Tivo.NetDisconnect - Device Tivo 192.168.2.180 has disconnected. 

The Main server continues to work fine...

FYI - this is not on my test Virtual Image, it is on a second licensed Master Image installed on a PI4

 

Is it maybe one of those drivers where you can only have one 'controller' connected at once? Like the Android TV driver - if you try to connect to the same device from more than one myServer you get connected, disconnected, connected, disconnected etc. on the second one. Until you disable it on the first myServer then the second one connects properly.

You are probably right..but I don't want to risk breaking my original server.  I'm going to assume it will work and when everything else is tested and I cut over I will try it.

 

Solution - I deactivated the Tivos on the Old myServer and the new one still didn't work (same error as above). I rebooted the Tivos and they worked fine from the New myServer.

You should try to reauthenticate from the new myServer. Delete the authentication, and do it again with the device. Many of these authentications hand shakes are machine to machine.

That was one of the first things I tried. I deleted the entries in the Tivo driver and forced a new discovery. The same thing happened with the newly discovered devices. I then went a step further and removed the Tivo driver, rebooted the server, installed the driver, and did another discovery. No change.

This isn't a big deal because you haven't fully implemented the Primary/Backup server setup (the menus are there but the code isn't). It will become an issue when you do try to implement it.

This should work because the Tivo allows communications via their Networked Mobile App while the myServer is connected.