I have an R3, and I’m having an issue I never had with the R2. I have a couple of activities set up that share, e.g., a Denon receiver and an Android TV (Sony if it matters).
Let’s say I pick up the remote and start the “Watch TV” activity and it works. Everything is fine. Then I shut down the activity. If I wait a few days to “Watch TV” again, 100% of the time the activity will fail with “Service Unavailable” on the TV. I am then unable to use any activity until I delete the Android TV and reconfigure it from scratch.
This is obviously unsustainable.
I don’t think this would have anything to do with power saving settings on the remote, because this only occurs when the remote has been on the dock for an extended period. Is this an issue with the Android integration and the R3?
I have an Philips Android TV and it needs up to 6 minutes to be available if it was in deep sleep or when I switched on the power plug. Try powering on with the original remote and when you see that Android TV is starting with an animation then it was in deep sleep and therefore not available. I disabled timeout on my Philips and never had an problem after that.
When you take the remote out of the dock check if you see a crossed out WiFi symbol or a dot moving back and forth in the top right corner. This means that the remote has disconnected from Wifi or one or more integrations are reconnecting.
If you have set the wake-up sensitivity to the lowest value and wait a few seconds after you pick up the remote from the Dock without pressing any button or touching the screen it enters sleep mode again. That’s a known issue.
That doesn’t appear to be it. The behavior happens even if I wait.
The strangest thing is that, once it fails, nothing seems to fix it. I’m sitting here looking at the TV (turned on) and a remote3 that’s definitely on the network, and I’m still getting the error that the service is unavailable.
I have no idea where to go with this. I reset everything, gave everything a static IP, re-added my Android TV integration, and when I pick the remote up off the dock after an overnight charging and verify that it has rejoined the network, it still gives me an Android TV error, after which the integration must be deleted and re-added. I have disabled all power savings except on the remote. Nothing like this happened on the R2.
2025-11-16 17:30:01.822138 +00:00 intg-androidtv
INFO DEBUG:androidtvremote2:Couldn't connect to
192.168.1.xxx:6466. Error: [Errno 113] Connect
call failed ('192.168.1.xxx', 6466)
Dozens of these entries. The TV is off (as expected) but it doesn’t have any sort of deep sleep setting, has not changed any settings since it was working with R2, and works fine when first added. Something on the R3 appears to be unable to reconnect to an Android TV from sleep.
I also have intermittent stability/reliabilty issues using the Android TV integration with an Nvidia Shield Pro, even with making sure to confirm that WiFi connectivity is reestablished. Some issues when waking the remote, but also issues with apparent loss of connectivity/response during a series of button presses. It is so persistent for me that I have to assume many others with Nvidia Shields (and possibly other Android TV devices) are experiencing similar issues. Can anyone confirm that this iṡ an acknowledged issue that is being investigated?
I have a 2019 Nvidia Shield Pro as well. I use mostly the Bluetooth integration but was using the Android TV integration for the dpad OK button, mapping short press to “Cursor Enter” and long press to “Context Menu”. However, frequently I was getting an error when executing the short press. Unless I was actually looking at the remote, I was unaware of the error condition since it currently pops up an interactive message and waits for input before retrying or canceling. Meanwhile all of the Bluetooth buttons would continue to function. Net result was something like being able to navigate around the screen, but never being able to select something.
The WiFi connectivity was not a problem, but rather the error was to the effect of no reply from the device (I don’t remember the exact wording).
I can confirm it is an issue, but have no idea if it is being investigated.
In firmware 2.8.1 there is a resend options for commands. If a command failed the remote resends the command upto 10 seconds until it succeeded. Configuration directly at the remote.
Yeah, but for some reason on my R3 with 2.8.1 that option is labeled “Unavailable” and I can’t turn it on. It’s a problem I haven’t looked into yet and haven’t seen anyone else post about it so just checking it periodically and hoping it clears itself up.
I’m just jumping back in here to say that nothing I’ve tried has made Android TV integration stable. If the remote sleeps for any duration, when I wake it up it any Android TV integration command will fail, and the failure state will be unrecoverable without rebooting the remote, no matter how long I wait for it to reestablish its link after waking up. Again, this was never an issue with my R2. Disappointing, particularly when another alternative universal remote with much more limited functionality (but still with multi-device activities) has been seamless with the TV for weeks.
Sadly, I have deleted and reimplemented Android TV integration multiple times. No effect. I’m going to nuke the config entirely and start over, I guess.
Most TVs are disabling WiFi if not used for a certain time. If you have “unreachable” again try to ping your TV. I am almost certain that it will also fail. Another try if you have this problem start the TV with the original remote. If you see the Android animation then the TV had a good night sleep and ignored network ativities.
In my case with a Philips TV I disabled a power off timer and since then no problems at all. After powering up the TV it takes around 6 minutes before the TV is ready.
I’ve tried with the TV’s power management disabled, with the same result. The stock remote and a SofaBaton (and, historically, my Harmony Remote) worked with the same TV without any issues, though the TV stock remote is communicating via IR so I’m not sure how useful a comparison that is.
The TV only shows the Android logo when it crashes or I restart it from the wall.
Stock remote, Sofabaton and Harmony do not use Ethernet or WiFi so you cannot compare them! Stock remote normally also uses Bluetooth if the remote is paired.
If you get an error did you try to ping your TV? I am pretty sure it is not in the network anymore in this case.
