Thanks - I'll try clearing the WiFi and see if that helps, but I don't think I ever used this TV with WiFi.
* Astute or psychic? 🙂 Technically, I do have 2 DHCP servers, but it's unrelated to this. There is a guest VLAN directly connected to a firewall port and the firewall hands out DHCP to that subnet - zero access to my network, and that's where the Amazon device lives. 😉
I do not run IPv6 anywhere. DHCP (on Windows Server 2022) only has V4 enabled. Cisco core switch has V6 disabled. I have no static IP devices in the workstations VLAN except for the media server (.252) and a Plex server (.253). Servers are on a separate VLAN and are all static. DHCP scope in the Workstations VLAN is 172.16.12.16-63, with addresses 16-31 excluded for DHCP Reservations. There are 8 reservations - my PC, an HD-HomeRun receiver, a printer, and 5 Roku devices, including the TV. Cisco switch handles IP Helper (DHCP relay) natively.
I've also confirmed that the port that the TV - like all other Roku devices - is configured only for the Workstations VLAN. The PCs are configured with dual Workstation/Voice VLANs and are connected through Cisco 7900 series phones. The TV does get its assigned reservation. Cable was swapped with a brand-new cable, and both cables pass a cable test.
Just seems odd that this one device seems to have issues. I'm used to turning on one of the other TVs, which turns on the USB-powered Roku and I can connect as soon as the Roku menu comes up. Even more strange that there doesn't seem to be a distinction between cold power cycle and warm power on. Roku Menu appears, wait 90 seconds, then "connected".
I'm having the same issue with 10 of the Roku TVs. Glad to hear it is not just me. Hoping for a solution but not encouraged.
I think I may have found a solution to this. If I turn on Fast TV Start in the power settings, it appears to keep the connection active.
