I was trying to setup the remote integration but it would never get pass the pin code. HA would register the pin as valid and immediately after show the following error:
Turns out this is “caused” by the TV booting with a USB remote plugged in. It’s one of these generic ones:
I haven’t confirmed if this also happens with any regular HID input device or if it’s just specific to this remote. It also has a built in mic so that could also be an issue. This was also affecting the Google TV app, it’s not HA specific.
Here are the integration logs:
2025-06-12 19:12:30.210 DEBUG (MainThread) [homeassistant.components.androidtv_remote] async_setup_entry: {'host': 'fd02:6122:bb02:0:a202:2144:2e11:c0d3', 'name': 'Philips Google TV TA7', 'mac': '38:1B:9E:86:B4:DD'}
2025-06-12 19:12:30.322 DEBUG (MainThread) [androidtvremote2] Couldn't connect to fd02:6122:bb02:0:a202:2144:2e11:c0d3:6466. Error: [Errno 104] Connection reset by peer
2025-06-12 19:12:35.781 DEBUG (MainThread) [homeassistant.components.androidtv_remote] async_setup_entry: {'host': 'fd02:6122:bb02:0:a202:2144:2e11:c0d3', 'name': 'Philips Google TV TA7', 'mac': '38:1B:9E:86:B4:DD'}
2025-06-12 19:12:35.791 DEBUG (MainThread) [androidtvremote2] Couldn't connect to fd02:6122:bb02:0:a202:2144:2e11:c0d3:6466. Error: [Errno 111] Connect call failed ('fd02:6122:bb02:0:a202:2144:2e11:c0d3', 6466, 0, 0)
2025-06-12 19:12:37.163 DEBUG (MainThread) [homeassistant.components.androidtv_remote] async_setup_entry: {'host': '192.168.110.143', 'mac': 'B8:59:CE:8C:20:F5', 'name': 'MiTV-AESP0'}
2025-06-12 19:12:40.240 DEBUG (MainThread) [androidtvremote2] Couldn't connect to 192.168.110.143:6466. Error: [Errno 113] Connect call failed ('192.168.110.143', 6466)
2025-06-12 19:12:44.873 DEBUG (MainThread) [homeassistant.components.androidtv_remote] async_setup_entry: {'host': 'fd02:6122:bb02:0:a202:2144:2e11:c0d3', 'name': 'Philips Google TV TA7', 'mac': '38:1B:9E:86:B4:DD'}
2025-06-12 19:12:44.883 DEBUG (MainThread) [androidtvremote2] Couldn't connect to fd02:6122:bb02:0:a202:2144:2e11:c0d3:6466. Error: [Errno 111] Connect call failed ('fd02:6122:bb02:0:a202:2144:2e11:c0d3', 6466, 0, 0)
2025-06-12 19:12:46.221 DEBUG (MainThread) [androidtvremote2] Closing idle connection
The most straight forward solution is to just get rid of the remote, but that might not be possible. In that case it could be useful to not supply power to the USB port until either the service starts or HA connects to the remote service. I’m not entirely sure if the issue comes up when HA connects to the service while the USB thing is connected, or if it just dooms the service from boot, so that part is left as an exercise to the reader 
.
I’m honestly not surprised at android’s inability to work in anything but the average use case. Anyways, this took me a long time to figure out, I hope this helps anyone with a similar issue.