Android TV loses connection after wake from sleep - Internal Server Error #34

Yezariael75 · 2023-09-09T13:31:56Z

Is there an existing issue for this?

I have searched the existing issues

Description

I added Nvidia Shield over Android TV integration. Works fine but if remote goes to sleep and wakes up connection to network is lost. Only solution is to reboot the device.

How to Reproduce

Add Android TV integration with Nvidia Shield
Start activity for Nvidia Shield (Plex)
Wait until remote goes to sleep
press a button - connection lost and does no get established again until reboot of device -> Message "Internal Server Error"

I assume the android tv integration crashes in the background?

Expected behavior

Remote wakes up and establishes connection, can be used as before sleep.

System version

1.1.1

What part of the system affected by the problem?

Integration

Additional context

No response

vistalba · 2023-09-10T08:08:55Z

I run into the same issue. Also nVidia Shield. Quite annoying.

splattner · 2023-09-11T13:02:49Z

not sure if I see the same issue here. I was able to add my Android TV and initially it worked and I could use it. But then suddenly, it stopped.
Not seeing anything in the log:

2023-09-11 12:58:07.792542 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 109, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:07.787115 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":109,"msg":"entity_command","msg_data":{"cmd_id":"cursor_up","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:07.332477 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 108, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:07.326893 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":108,"msg":"entity_command","msg_data":{"cmd_id":"cursor_down","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:06.647171 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 107, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:06.641784 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":107,"msg":"entity_command","msg_data":{"cmd_id":"cursor_down","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:06.176987 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 106, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:06.171262 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":106,"msg":"entity_command","msg_data":{"cmd_id":"cursor_left","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:05.508621 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 105, "code": 200, "msg": "result", "msg_data": {}}

Rebooting the remote, also helped.

martonborzak · 2023-09-11T13:06:21Z

not sure if I see the same issue here. I was able to add my Android TV and initially it worked and I could use it. But then suddenly, it stopped. Not seeing anything in the log:

2023-09-11 12:58:07.792542 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 109, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:07.787115 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":109,"msg":"entity_command","msg_data":{"cmd_id":"cursor_up","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:07.332477 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 108, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:07.326893 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":108,"msg":"entity_command","msg_data":{"cmd_id":"cursor_down","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:06.647171 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 107, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:06.641784 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":107,"msg":"entity_command","msg_data":{"cmd_id":"cursor_down","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:06.176987 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 106, "code": 200, "msg": "result", "msg_data": {}}
2023-09-11 12:58:06.171262 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":106,"msg":"entity_command","msg_data":{"cmd_id":"cursor_left","entity_id":"D4F8292E8A2C","entity_type":"media_player"}}
2023-09-11 12:58:05.508621 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 105, "code": 200, "msg": "result", "msg_data": {}}

Rebooting the remote, also helped.

Could you please upload logs for the Core service as well when you see this issue? Does it happen after wakeup?

splattner · 2023-09-11T15:09:14Z

Nothing special there 🤔

2023-09-11 13:01:44.641620 +00:00	core	NOTICE	[uc.main.3ffd1dcd-c75e-4062-9e5a-cb127d0d01c9] activity finished
2023-09-11 13:01:44.631424 +00:00	core	NOTICE	[uc.main.3ffd1dcd-c75e-4062-9e5a-cb127d0d01c9] started activity with timeout of 30s
2023-09-11 13:01:27.948520 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 13:00:38.600669 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 13:00:07.603638 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:59:00.819214 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 12:58:39.594664 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:58:25.394299 +00:00	core	NOTICE	Contacting OTA server for dock update check
2023-09-11 12:58:25.316307 +00:00	core	NOTICE	Check OTA server for dock firmware update: UC-Dock-8C4B14AA7884
2023-09-11 12:56:58.818043 +00:00	core	NOTICE	Changed battery status: 70% Discharging, 3831mV, charger: false
2023-09-11 12:56:12.479010 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 12:55:45.601932 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:55:40.951151 +00:00	core	NOTICE	Ignoring invalid service name: intg-androidtv%2Cintg-appletv%2Cintg-bangolufsen%2Cintg-homeassistant%2Cintg-philipshue%2Ccore%2Cui%2Ccustom-ui%2Cwifi%2Cbt
2023-09-11 12:55:23.203450 +00:00	core	NOTICE	Contacting OTA server for dock update check
2023-09-11 12:55:23.133912 +00:00	core	NOTICE	Check OTA server for dock firmware update: UC-Dock-8C4B14AA7884
2023-09-11 12:54:52.787158 +00:00	core	NOTICE	[uc.main.3ffd1dcd-c75e-4062-9e5a-cb127d0d01c9] activity finished
2023-09-11 12:54:52.783074 +00:00	core	NOTICE	[uc.main.3ffd1dcd-c75e-4062-9e5a-cb127d0d01c9] started activity with timeout of 30s
2023-09-11 12:54:36.447254 +00:00	core	NOTICE	Contacting OTA server for dock update check
2023-09-11 12:54:36.384774 +00:00	core	NOTICE	Check OTA server for dock firmware update: UC-Dock-8C4B14AA7884
2023-09-11 12:54:21.954196 +00:00	core	NOTICE	Contacting OTA server for dock update check
2023-09-11 12:54:21.881136 +00:00	core	NOTICE	Check OTA server for dock firmware update: UC-Dock-8C4B14AA7884
2023-09-11 12:54:16.363177 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 12:52:22.601048 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:51:52.566939 +00:00	core	NOTICE	TODO implement activity button mapping
2023-09-11 12:51:51.601459 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:51:19.967430 +00:00	core	NOTICE	[uc.main.9ad2e351-7ce4-4899-9242-05be83070468] activity finished
2023-09-11 12:51:19.958146 +00:00	core	NOTICE	[uc.main.9ad2e351-7ce4-4899-9242-05be83070468] started activity with timeout of 30s
2023-09-11 12:51:16.955417 +00:00	core	NOTICE	[uc_androidtv_driver.main] Waiting for available entities with request id: 56
2023-09-11 12:51:10.519571 +00:00	core	NOTICE	[uc_androidtv_driver.main] Waiting for available entities with request id: 55
2023-09-11 12:51:06.879002 +00:00	core	NOTICE	[hass.main] Waiting for available entities with request id: 11
2023-09-11 12:51:04.197381 +00:00	core	NOTICE	[hass.main] Waiting for available entities with request id: 10
2023-09-11 12:50:47.638122 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 12:50:28.478487 +00:00	core	NOTICE	Changed battery status: 71% Discharging, 3862mV, charger: false
2023-09-11 12:46:49.605840 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:46:18.592648 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:45:40.305052 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 12:45:32.607533 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:44:56.802165 +00:00	core	NOTICE	Contacting OTA server for dock update check
2023-09-11 12:44:56.726083 +00:00	core	NOTICE	Check OTA server for dock firmware update: UC-Dock-8C4B14AA7884
2023-09-11 12:44:11.434673 +00:00	core	NOTICE	[uc.main.9ad2e351-7ce4-4899-9242-05be83070468] activity finished
2023-09-11 12:44:11.430164 +00:00	core	NOTICE	[uc.main.9ad2e351-7ce4-4899-9242-05be83070468] started activity with timeout of 30s
2023-09-11 12:44:03.615075 +00:00	core	NOTICE	Setting button backlight to: 50%
2023-09-11 12:43:03.099679 +00:00	core	NOTICE	Changed battery status: 72% Discharging, 3874mV, charger: false
2023-09-11 12:42:08.464154 +00:00	core	NOTICE	Sent get_entity_states: Ok(())
2023-09-11 12:42:05.740603 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] SessionAuthenticated msg
2023-09-11 12:42:05.739452 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Session state change: Authenticated
2023-09-11 12:42:05.669294 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Connected to: ws://192.168.10.240:946/
2023-09-11 12:42:05.664959 +00:00	core	WARN	[UC-Dock-8C4B14AA7884] Can't handle dock TryReconnect command in state: Connecting
2023-09-11 12:42:05.662227 +00:00	core	WARN	[UC-Dock-8C4B14AA7884] No transition for: state=Connecting, event=TryReconnect
2023-09-11 12:42:05.620109 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] WiFi connected: connecting dock
2023-09-11 12:42:05.617667 +00:00	core	NOTICE	WiFi connected: starting all external drivers
2023-09-11 12:42:05.616280 +00:00	core	NOTICE	Event: CONNECTED
2023-09-11 12:42:05.167688 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 500ms
2023-09-11 12:42:05.166260 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] on_session_disconnected: ClientDisconnect
2023-09-11 12:42:05.165243 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Session state change: Disconnected
2023-09-11 12:42:05.159292 +00:00	core	ERROR	[UC-Dock-8C4B14AA7884] Websocket server heartbeat failed, disconnecting!
2023-09-11 12:41:54.257245 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] SessionAuthenticated msg
2023-09-11 12:41:54.256059 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Session state change: Authenticated
2023-09-11 12:41:51.606821 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:41:47.151221 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Connected to: ws://192.168.10.240:946/
2023-09-11 12:41:41.766525 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 1.853s
2023-09-11 12:41:41.765186 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] on_session_disconnected: ClientDisconnect
2023-09-11 12:41:41.764235 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Session state change: Disconnected
2023-09-11 12:41:41.758282 +00:00	core	ERROR	[UC-Dock-8C4B14AA7884] Websocket server heartbeat failed, disconnecting!
2023-09-11 12:41:29.768557 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Resolved uc-dock-8c4b14aa7884.local: 192.168.10.240
2023-09-11 12:41:29.759972 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Resolving: uc-dock-8c4b14aa7884.local
2023-09-11 12:41:29.757842 +00:00	core	NOTICE	Dock URL not resolved, trying service name
2023-09-11 12:41:29.751548 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Connected to: ws://UC-Dock-8C4B14AA7884.local:946
2023-09-11 12:41:24.358424 +00:00	core	NOTICE	Dock URL not resolved, trying service name
2023-09-11 12:41:22.931029 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 1.426s
2023-09-11 12:41:22.925589 +00:00	core	ERROR	[UC-Dock-8C4B14AA7884] Error connecting to dock: TimedOut
2023-09-11 12:41:21.594619 +00:00	core	NOTICE	Setting button backlight to: 0%
2023-09-11 12:41:11.828222 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 1.097s
2023-09-11 12:41:11.826639 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] on_session_disconnected: ClientDisconnect
2023-09-11 12:41:11.825556 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Session state change: Disconnected
2023-09-11 12:41:11.822972 +00:00	core	ERROR	[UC-Dock-8C4B14AA7884] Websocket server heartbeat failed, disconnecting!
2023-09-11 12:40:59.825096 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Resolved uc-dock-8c4b14aa7884.local: 192.168.10.240
2023-09-11 12:40:59.820255 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Resolving: uc-dock-8c4b14aa7884.local
2023-09-11 12:40:59.818824 +00:00	core	NOTICE	Dock URL not resolved, trying service name
2023-09-11 12:40:59.815081 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Connected to: ws://UC-Dock-8C4B14AA7884.local:946
2023-09-11 12:40:59.473184 +00:00	core	NOTICE	Dock URL not resolved, trying service name
2023-09-11 12:40:58.630355 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 844ms
2023-09-11 12:40:58.626270 +00:00	core	ERROR	[UC-Dock-8C4B14AA7884] Error connecting to dock: ServiceUnavailable("Failed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolution")
2023-09-11 12:40:50.966657 +00:00	core	NOTICE	Dock URL not resolved, trying service name
2023-09-11 12:40:50.316582 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 650ms
2023-09-11 12:40:50.314029 +00:00	core	ERROR	[UC-Dock-8C4B14AA7884] Error connecting to dock: ServiceUnavailable("Failed to connect to host: Network is unreachable (os error 101)")
2023-09-11 12:40:49.809462 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Reconnecting in: 500ms
2023-09-11 12:40:49.809022 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] on_session_disconnected: ClientDisconnect
2023-09-11 12:40:49.808627 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Session state change: Disconnected
2023-09-11 12:40:49.807909 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] Force stopping actor
2023-09-11 12:40:49.710163 +00:00	core	WARN	[UC-Dock-8C4B14AA7884] Can't handle dock ConnectCmd command in state: Active
2023-09-11 12:40:49.709494 +00:00	core	WARN	[UC-Dock-8C4B14AA7884] No transition for: state=Active, event=ConnectCmd
2023-09-11 12:40:49.709289 +00:00	core	WARN	[UC-Dock-8C4B14AA7884] Old connection is still open, closing it
2023-09-11 12:40:49.708750 +00:00	core	NOTICE	[UC-Dock-8C4B14AA7884] WiFi connected: connecting dock
2023-09-11 12:40:49.708326 +00:00	core	NOTICE	WiFi connected: starting all external drivers
2023-09-11 12:40:49.708126 +00:00	core	NOTICE	Event: CONNECTED

and right now, after sleep and wake up, I see no problem. I'll keep oberving, and maybee someone else has a Core Log with more

Yezariael75 · 2023-09-11T15:17:47Z

Where can I get the core log?

splattner · 2023-09-11T15:32:09Z

Where can I get the core log?

in the webconfigurator -> settings -> Development -> logs

Yezariael75 · 2023-09-11T21:43:21Z

Here is the "internal server error". After restarting the remote it works again like it should.

2023-09-11 21:41:31.552080 +00:00 core NOTICE Setting button backlight to: 0%
2023-09-11 21:41:25.551601 +00:00 core NOTICE Changed battery status: 30% Charging, 3936mV, charger: true
2023-09-11 21:41:15.541773 +00:00 core NOTICE Changed battery status: 30% Discharging, 3735mV, charger: true
2023-09-11 21:41:11.650729 +00:00 core ERROR [uc.main.d4aee80b-638f-42f3-8a88-6fdf3dd64034] error executing activity command uc_androidtv_driver.main.00044BB4FC57:media_player.off (ignore error: false): Internal Server Error
2023-09-11 21:41:11.341920 +00:00 core NOTICE [uc.main.d4aee80b-638f-42f3-8a88-6fdf3dd64034] started activity with timeout of 30s
2023-09-11 21:40:55.915513 +00:00 core ERROR [uc.main.d4aee80b-638f-42f3-8a88-6fdf3dd64034] error executing activity command uc_androidtv_driver.main.00044BB4FC57:media_player.on (ignore error: false): Internal Server Error
2023-09-11 21:40:55.272552 +00:00 core NOTICE [uc.main.d4aee80b-638f-42f3-8a88-6fdf3dd64034] started activity with timeout of 30s
2023-09-11 21:40:50.526892 +00:00 core NOTICE Changed battery status: 30% Discharging, 3777mV, charger: false
2023-09-11 21:40:48.727791 +00:00 core NOTICE Setting button backlight to: 50%
2023-09-11 21:39:18.554138 +00:00 core NOTICE Setting button backlight to: 0%
2023-09-11 21:39:09.959594 +00:00 core ERROR Error encountered while processing the incoming HTTP request: AuthError("Authentication error")
2023-09-11 21:39:09.954387 +00:00 core ERROR Error encountered while processing the incoming HTTP request: AuthError("Authentication error")
2023-09-11 21:39:02.551790 +00:00 core NOTICE Setting button backlight to: 0%
2023-09-11 21:39:00.429749 +00:00 core NOTICE Changed battery status: 30% Charging, 3943mV, charger: true
2023-09-11 21:38:50.421353 +00:00 core NOTICE Changed battery status: 30% Discharging, 3745mV, charger: true
2023-09-11 21:38:45.550281 +00:00 core NOTICE Closing connection with code Policy: Authentication timeout
2023-09-11 21:38:40.413261 +00:00 core NOTICE Changed battery status: 30% Discharging, 3754mV, charger: false
2023-09-11 21:38:35.410431 +00:00 core NOTICE Changed battery status: 30% Not charging, 3950mV, charger: false
2023-09-11 21:38:34.609558 +00:00 core NOTICE Setting button backlight to: 50%
2023-09-11 21:38:16.021306 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2023-09-11 21:38:15.854202 +00:00 core ERROR Error encountered while processing the incoming HTTP request: AuthError("Authentication error")
2023-09-11 21:38:15.850005 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2023-09-11 21:37:45.367389 +00:00 core NOTICE Changed battery status: 30% Charging, 3950mV, charger: true
2023-09-11 21:34:35.204427 +00:00 core NOTICE Changed battery status: 29% Charging, 3948mV, charger: true

smarthomesydney · 2023-09-11T22:38:03Z

@martonborzak I have this error also and am using nVidia Shield pro also.
Let me know if you need additional logs.

otherguy · 2023-09-12T22:02:31Z

I have the same without an Nvidia Shield. The update to the Android TV integration finally let me add my TV, but I‘m facing this issue now.

smarthomesydney · 2023-09-13T00:54:57Z

Errors

"2023-09-12 11:35:50.289827 +00:00	core	ERROR	Error("missing field `api`", line: 0, column: 0)"

"2023-09-12 11:35:49.154044 +00:00	core	ERROR	[uc_androidtv_driver] Error connecting to driver: ServiceUnavailable("Failed to connect to host: Connection refused (os error 111)")"

2023-09-13 01:55:25.340003 +00:00	core	NOTICE	Ignoring invalid service name: ui%2Ccore%2Cintg-philipshue%2Cintg-homeassistant%2Cintg-androidtv
2023-09-13 01:54:41.900850 +00:00	core	NOTICE	Closing connection with code Policy: Authentication timeout
2023-09-13 01:54:34.737400 +00:00	core	WARN	[127.0.0.1:40920] ignoring 'ping': session not yet authenticated!
2023-09-13 01:54:29.704751 +00:00	core	WARN	[127.0.0.1:40920] ignoring 'ping': session not yet authenticated!
2023-09-13 01:54:24.487356 +00:00	core	NOTICE	No session state has been found for a valid session key, creating a new empty session.
2023-09-13 01:54:24.361257 +00:00	core	ERROR	Error encountered while processing the incoming HTTP request: AuthError("Authentication error")
2023-09-13 01:54:24.359242 +00:00	core	NOTICE	No session state has been found for a valid session key, creating a new empty session.
2023-09-13 01:54:12.561575 +00:00	core	NOTICE	[uc_androidtv_driver.main] Waiting for available entities with request id: 231

Yezariael75 · 2023-09-23T13:20:25Z

@martonborzak Any news about this? Thanks!

kennymc-c · 2023-10-01T10:34:52Z

Same problem for me but with a Sony XE9005 running Android TV 9

2023-10-01 10:04:06.183299 +00:00	core	ERROR	[uc.main.02219a2f-d9f7-4899-91b4-7108d2cf5f6b] error executing activity command uc_androidtv_driver.main.A86BAD280614:media_player.on (ignore error: false): Internal Server Error
2023-10-01 10:04:06.182286 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 32, "code": 500, "msg": "result", "msg_data": {}}
2023-10-01 10:04:06.182059 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: A86BAD280614
2023-10-01 10:04:06.179469 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":32,"msg":"entity_command","msg_data":{"cmd_id":"on","entity_id":"A86BAD280614","entity_type":"media_player","params":{}}}

vistalba · 2023-10-23T18:55:29Z

Updated to 1.4.3 and 0.92 and still running in to the same issue.
Just selected to download debug log... but showing only "Info". Looks like this:

2023-10-23 18:46:03.106933 +00:00	ui	WARN	uc.ui.entity.controller: Cannot execute command: "media_player.back" 500 "Internal server error, please try later"
2023-10-23 18:46:03.091749 +00:00	ui	WARN	uc.ui.entity.controller: Cannot execute command: "media_player.back" 500 "Internal server error, please try later"
2023-10-23 18:46:03.090768 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 69, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:03.089050 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:03.085708 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":69,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:03.077379 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 68, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:03.076424 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:03.072183 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":68,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:02.606026 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 67, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:02.604488 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:02.601270 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":67,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:02.555870 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 66, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:02.554376 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:02.551174 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":66,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:02.538041 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 65, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:02.536576 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:02.533336 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":65,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:02.305221 +00:00	ui	WARN	uc.ui.entity.controller: Cannot execute command: "media_player.back" 500 "Internal server error, please try later"
2023-10-23 18:46:02.299591 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 64, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:02.298070 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:02.294854 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":64,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:02.087003 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 63, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:02.085566 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:02.082355 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":63,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:02.031405 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 62, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:02.030429 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ
2023-10-23 18:46:02.026356 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:<-: {"kind":"req","id":62,"msg":"entity_command","msg_data":{"cmd_id":"back","entity_id":"00044BXYZXYZ","entity_type":"media_player"}}
2023-10-23 18:46:01.909052 +00:00	intg-androidtv	INFO	DEBUG:ucapi.api:->: {"kind": "resp", "req_id": 61, "code": 500, "msg": "result", "msg_data": {}}
2023-10-23 18:46:01.907342 +00:00	intg-androidtv	INFO	ERROR:tv:Cannot send command, connection lost: 00044BXYZXYZ

Is there anything I can test or provide helping to nail down this annoying issue?

MarkJenniskens · 2023-10-30T10:31:30Z

I've got a similar issue, maybe I should open a new issue. But every other day the Android integration stops working (time-out / internal server error). Sometimes rebooting the remote helps. When it doesn't i need te re-run the integration set-up to pair with the Nvidia Shield. I can reproduce the issue by powercycling the Shield.

zehnm · 2023-11-01T13:47:25Z

We found one reconnection related issue, which is fixed in the next release. We continue testing though to fix this showstopper for good.

vistalba · 2023-11-01T14:00:26Z

We found one reconnection related issue, which is fixed in the next release. We continue testing though to fix this showstopper for good.

Thanks for the update. Any ETA?
One more thing I noticed… for me the Bug just occur after the Remote was in Sleep and most probably disconnected from WiFi. So may it is related to WiFi/Remote combination? My remote does most of the time not work after waking up for 3-4 seconds.
Using UniFi AP with multiple APs. Is it normal, that the remote needs that long to reconnect?

zehnm · 2023-11-03T09:09:09Z

Closing: fixed in release 1.4.5.
We were no longer able to reproduce this issue with Nvidia Shield TV.
If you still encounter reconnect issues after wakeup, please reopen this issue.

vistalba · 2023-11-06T13:41:52Z

Closing: fixed in release 1.4.5. We were no longer able to reproduce this issue with Nvidia Shield TV. If you still encounter reconnect issues after wakeup, please reopen this issue.

After 3 days I can say that it is defintly better than before. I still run into some issues like:

after wakeup it takes 2-4 seconds until I can use the remote
after pressing a button, nothing happens and after a few seconds a message appears "internal server error" in red. Most of the time the issue does now recover from that in a few seconds. But it is still annyoing for me.

Yezariael75 added the bug Something isn't working label Sep 9, 2023

github-actions bot added the integration Integration driver related issue label Sep 9, 2023

Yezariael75 changed the title ~~Android TV loses connection after wake from sleep~~ Android TV loses connection after wake from sleep - Internal Server Error Sep 9, 2023

martonborzak self-assigned this Sep 11, 2023

splattner mentioned this issue Sep 12, 2023

Error on editing Activity #38

Closed

1 task

otherguy mentioned this issue Sep 12, 2023

Connection to Dock not established #44

Open

1 task

zehnm added this to the Roadmap October 2023 milestone Nov 3, 2023

zehnm closed this as completed Nov 3, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Android TV loses connection after wake from sleep - Internal Server Error #34

Android TV loses connection after wake from sleep - Internal Server Error #34

Yezariael75 commented Sep 9, 2023 •

edited

vistalba commented Sep 10, 2023

splattner commented Sep 11, 2023

martonborzak commented Sep 11, 2023

splattner commented Sep 11, 2023

Yezariael75 commented Sep 11, 2023

splattner commented Sep 11, 2023

Yezariael75 commented Sep 11, 2023

smarthomesydney commented Sep 11, 2023

otherguy commented Sep 12, 2023 •

edited

smarthomesydney commented Sep 13, 2023 •

edited

Yezariael75 commented Sep 23, 2023

kennymc-c commented Oct 1, 2023

vistalba commented Oct 23, 2023 •

edited

MarkJenniskens commented Oct 30, 2023

zehnm commented Nov 1, 2023

vistalba commented Nov 1, 2023

zehnm commented Nov 3, 2023

vistalba commented Nov 6, 2023

Android TV loses connection after wake from sleep - Internal Server Error #34

Android TV loses connection after wake from sleep - Internal Server Error #34

Comments

Yezariael75 commented Sep 9, 2023 • edited

Is there an existing issue for this?

Description

How to Reproduce

Expected behavior

System version

What part of the system affected by the problem?

Additional context

vistalba commented Sep 10, 2023

splattner commented Sep 11, 2023

martonborzak commented Sep 11, 2023

splattner commented Sep 11, 2023

Yezariael75 commented Sep 11, 2023

splattner commented Sep 11, 2023

Yezariael75 commented Sep 11, 2023

smarthomesydney commented Sep 11, 2023

otherguy commented Sep 12, 2023 • edited

smarthomesydney commented Sep 13, 2023 • edited

Yezariael75 commented Sep 23, 2023

kennymc-c commented Oct 1, 2023

vistalba commented Oct 23, 2023 • edited

MarkJenniskens commented Oct 30, 2023

zehnm commented Nov 1, 2023

vistalba commented Nov 1, 2023

zehnm commented Nov 3, 2023

vistalba commented Nov 6, 2023

Yezariael75 commented Sep 9, 2023 •

edited

otherguy commented Sep 12, 2023 •

edited

smarthomesydney commented Sep 13, 2023 •

edited

vistalba commented Oct 23, 2023 •

edited