R3, Android integration - "Service Unavailable"

General
1

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?

2

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.

Ralf

3

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.

4

I have all power savings and related settings on the TV disabled. Still no good.

5

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.

6

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.

Where are logs stored on the device?

7

Settings, development.

8

Thx.

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.

1 Like