Remote Stopped Working after TV Software Update

Has there been any progress?  I'd prefer not to move over to IR from IP control.

Is simple IP turned on. If you do not see port 20060 open then the driver has no control. I just did a bar upgrade with sonys and the driver worked. Someone email me a teamviewer ID and I'll look on your system.

davep wrote:

Is simple IP turned on. If you do not see port 20060 open then the driver has no control. I just did a bar upgrade with sonys and the driver worked. Someone email me a teamviewer ID and I'll look on your system.

Simple IP is on.  As mention previously, there is Normal and Pre-shared Key as authentication options.  I have Normal selected.  I also tried both remote start options - networked standby and apps, which made no difference.

Here are the NMAP results:
Starting Nmap 7.92 ( nmap.org ) at 2025-10-15 13:57 EDT
Nmap scan report for 192.168.X
Host is up (0.00070s latency).
Not shown: 65521 closed tcp ports (reset)
PORT      STATE    SERVICE
80/tcp    open     http
5555/tcp  open     freeciv
6466/tcp  open     unknown
6467/tcp  open     unknown
7000/tcp  open     afs3-fileserver
8008/tcp  open     http
8009/tcp  open     ajp13
8443/tcp  open     https-alt
9000/tcp  open     cslistener
20060/tcp open     unknown
32500/tcp filtered unknown
33511/tcp open     unknown
34093/tcp open     unknown
44659/tcp open     unknown
MAC Address: XX (Sony Home Entertainment&Sound Products)
Nmap done: 1 IP address (1 host up) scanned in 4.55 seconds

I tried the other available TV (BikeTV, AV|2) which I haven't updated recently and all is well.  The TheaterTV (AV|7) , which I did update, isn't working.  I tested some power commands and here's the logs:

15/10/2025 14:13:07.13 · DEBUG · Server.doCommand - AV|2~Power~On from dashboard-fx-9u4m 
15/10/2025 14:13:07.13 · DEBUG · SonyTVs.doCommand - Cmd=[2~Power~On] Client=[dashboard-fx-9u4m] 
15/10/2025 14:13:07.13 · DEBUG · SonyTVs.TX >>> - BikeTV:*SCPOWR0000000000000001 
15/10/2025 14:13:07.13 · DEBUG · SonyTVs.RX: BikeTV - *SAPOWR0000000000000000 
15/10/2025 14:13:07.13 · DEBUG · SonyTVs.TX >>> - BikeTV:*SEPOWR################ 
15/10/2025 14:13:07.13 · DEBUG · SonyTVs.RX: BikeTV - *SAPOWR0000000000000001 
15/10/2025 14:13:12.13 · DEBUG · SonyTVs.RX: BikeTV - *SNPOWR0000000000000001 
15/10/2025 14:13:14.13 · DEBUG · Server.doCommand - AV|7~Power~On from dashboard-fx-9u4m 
15/10/2025 14:13:14.13 · DEBUG · SonyTVs.doCommand - Cmd=[7~Power~On] Client=[dashboard-fx-9u4m] 
15/10/2025 14:13:14.13 · DEBUG · SonyTVs.TX >>> - TheaterTV:*SCPOWR0000000000000001 
15/10/2025 14:13:14.13 · ERROR · SonyTVs.SendCommand - Cannot send command to device TheaterTV - Device not connected 
15/10/2025 14:13:14.13 · DEBUG · SonyTVs.TX >>> - TheaterTV:*SEPOWR################ 
15/10/2025 14:13:14.13 · ERROR · SonyTVs.SendCommand - Cannot send command to device TheaterTV - Device not connected I will send you my Teamviewer ID

Kyle

Thanks for looking into my system. I cycled Simple IP Control again and Port 20060 is open again, but it still doesn't work.
Per your suggestion I tried controlling the TV through the Android TV driver. I got the prompt to authorize MyServer to control the TV and enabled it.  I tried some power commands and here is the error I received (on both the Theater and Bike TVs); not sure why the two TVs are listed as unauthorized:

15/10/2025 15:42:20.42 · DEBUG · Server.doCommand - AV|35~Power~Off from dashboard-fx-9u4m 
15/10/2025 15:42:20.42 · DEBUG · AndroidTV.doCommand - Cmd=[35~Power~Off] Client=[dashboard-fx-9u4m] 
15/10/2025 15:42:20.42 · DEBUG · AndroidTV.doCommand - Reconnect to 192.168.2.54:5555 
15/10/2025 15:42:20.42 · ERROR · AndroidTV.doCommand - Error in MoveNext - Object reference not set to an instance of an object. 
15/10/2025 15:42:22.42 · DEBUG · AndroidTV.TX: ATV 192.168.2.54 - dumpsys display| grep "mScreenState" 
15/10/2025 15:42:22.42 · DEBUG · AndroidTV.RX - ATV 192.168.2.54 <<  mScreenState=ON>> 
15/10/2025 15:42:22.42 · DEBUG · AndroidTV.TX: ATV 192.168.2.54 - dumpsys activity activities | grep "mResumedActivity" 
15/10/2025 15:42:22.42 · DEBUG · AndroidTV.RX - ATV 192.168.2.54 <<    mResumedActivity: ActivityRecord{8410d0e u0 com.android.tv.settings/.MainSettings t5423}>> 
15/10/2025 15:42:22.42 · DEBUG · AndroidTV.GetDeviceType - Sony  
15/10/2025 15:42:37.42 · DEBUG · AndroidTV.CheckAdb - Checking for ADB running 
15/10/2025 15:42:37.42 · DEBUG · AndroidTV.CheckAdb - List of devices attached 192.168.2.129:55055 device 192.168.2.132:5555 device 192.168.2.235:5555 unauthorized 192.168.2.23:5555 unauthorized 192.168.2.54:5555 device   
15/10/2025 15:42:40.42 · DEBUG · AndroidTV.TX: ATV 192.168.2.54 - dumpsys display| grep "mScreenState" 
15/10/2025 15:42:40.42 · DEBUG · AndroidTV.RX - ATV 192.168.2.54 <<  mScreenState=ON>> 
15/10/2025 15:42:40.42 · DEBUG · AndroidTV.TX: ATV 192.168.2.54 - dumpsys activity activities | grep "mResumedActivity" 
15/10/2025 15:42:40.42 · DEBUG · AndroidTV.RX - ATV 192.168.2.54 <<    mResumedActivity: ActivityRecord{8410d0e u0 com.android.tv.settings/.MainSettings t5423}>> 
15/10/2025 15:42:40.42 · DEBUG · AndroidTV.GetDeviceType - Sony  
 

ensure ADB is turned on within the Sony / Android menu.  You might have to enable Developer mode (click the "About" like 7 times) to access the hidden ADB menu.
From a terminal window on myServer type: adb devices
See if the Sony TVs (running Android OS) show up and are authorized.
You can try to do a
adb connect <<IPaddress:5555>>
to manually connect it.
Accept the token request on the TV (use TVs remote control to accept)
Then run ADB Devices again to verify it's now authorized.
 

Thanks!  Developer mode was already enabled. I recycled the ADB Debugging checkbox on both TVs and reaccepted the tokens. I tried controlling the TV with the Android TV driver again this morning without changing anything and it's now working.

Going back to the original problem with IP control, I think recycling ADB Debugging on my problematic TV in the theater got IP control working again.

Dave remoted into my system yesterday and the first time, for some reason, port 20060 was closed. It had been open previously, as seen at the Nmap results above. I cycled simple IP control to open the port back up, but IP control still didn't work. I cycled ADB Debugging off and on so I could try the Android TV driver. I wasn't able to get back to troubleshooting for a few hours, but during that time Dave tried a few IP control commands and they worked.  I'm finally able to control my TV via IP again.

One other item of concern is Dave when found port 20060 was closed and I noted the TV was on the Google screensaver. We thought the screensaver might be what closed port 20060. I just let the screensaver come on to see if this was the case and Port 20060 remained open and I could still use IP control.

cjisble - try turning ADB Debugging off and on, accept the token, recycle TV power, and see if that fixes IP control.  

Kyle