Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

[blamaz]

The problem

I'm still getting this error.

Logger: homeassistant.components.roku.coordinator Source: helpers/update_coordinator.py:235 Integration: Roku (documentation, issues) First occurred: September 10, 2023 at 11:23:56 PM (1 occurrences) Last logged: September 10, 2023 at 11:23:56 PM Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

What version of Home Assistant Core has the issue?

2023.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roku

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roku

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Home Assistant 2023.9.1
Supervisor 2023.08.3
Operating System 10.5
Frontend 20230908.0 - latest

Additional information

This error is happening on both of my TCL Roku TV when turn off manually or by an automation (plex media player idle timer). I can ping both Roku TV even if they're off, both TV have 'Fast TV Start' option enabled, i'm on a wired network and ip reservations fare set on the router. I do have AdGuard home blocking useless Roku DNS requests. I've enabled Roku debug logging and will add any valuable log info whenever it happen again.

[home-assistant[bot]]

Hey there @ctalkington, mind taking a look at this issue as it has been labeled with an integration (roku) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of roku can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign roku Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

roku documentation roku source _{^{(message by IssueLinks)}}

[thenakuls]

Also had this issue. Removed the device and added it again, after getting the IP address (in case it changed) and it seems to be working

[Unvented6195]

Also experiencing this with home assistant container.

Reloading the integration fails.

Adding device to integration using the same (static) IP results in the message “Device already configured” After this; however the integration can reload and work.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[blamaz]

Issue still present

[Shredder5262]

Having this issue with my roku TV

Core 2024.4.2 Supervisor 2024.04.0 Operating System 12.2 Frontend 20240404.1

`2024-04-14 14:58:57.720 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140657511515200] Invalid response from Roku API Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/roku/helpers.py", line 43, in wrapper await func(self, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/roku/media_player.py", line 481, in async_select_source await self.coordinator.roku.launch(appl.app_id) File "/usr/local/lib/python3.12/site-packages/rokuecp/rokuecp.py", line 336, in launch await self._request(f"launch/{app_id}?{encoded}", method="POST", encoded=True) File "/usr/local/lib/python3.12/site-packages/rokuecp/rokuecp.py", line 174, in _request raise RokuError( rokuecp.exceptions.RokuError: ('HTTP 503', {'content-type': '', 'message': '', 'status-code': 503})

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 239, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2543, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2580, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 971, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1043, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/scene/init.py", line 116, in _async_activate await self.async_activate(**kwargs) File "/usr/src/homeassistant/homeassistant/components/homeassistant/scene.py", line 370, in async_activate await async_reproduce_state( File "/usr/src/homeassistant/homeassistant/helpers/state.py", line 70, in async_reproduce_state await asyncio.gather( File "/usr/src/homeassistant/homeassistant/helpers/state.py", line 64, in worker await platform.async_reproduce_states( File "/usr/src/homeassistant/homeassistant/components/media_player/reproduce_state.py", line 145, in async_reproduce_states await asyncio.gather( File "/usr/src/homeassistant/homeassistant/components/media_player/reproduce_state.py", line 91, in _async_reproduce_states await call_service(SERVICE_SELECT_SOURCE, [ATTR_INPUT_SOURCE]) File "/usr/src/homeassistant/homeassistant/components/media_player/reproduce_state.py", line 60, in call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 2543, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2580, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 971, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1043, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/roku/helpers.py", line 52, in wrapper raise HomeAssistantError("Invalid response from Roku API") from error`

[rwelsh09]

I too receive this error:

Logger: homeassistant.components.roku.coordinator
Source: helpers/update_coordinator.py:347
integration: Roku (documentation, issues)

Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

Let me know if I can assist in resolving the issue.

Thanks!

[dinan5]

Same here. Thanks!

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[sumoneelse]

This still happens for me. All I needed to do was pop open my most recent Home Assistant Core log to find 11 instances in the last few days.

Core 2024.10.3 Supervisor 2024.10.2 Operating System 13.2

Logger: homeassistant.components.roku.coordinator Source: helpers/update_coordinator.py:386 integration: Roku (documentation, issues) First occurred: October 20, 2024 at 11:18:10 AM (11 occurrences) Last logged: 6:30:33 AM Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

[dinan5]

I replaced my Roku with FireTV stick. Couldn't wait for resolution.

From: sumoneelse @.> Sent: Tuesday, October 22, 2024 1:44 PM To: home-assistant/core @.> Cc: dinan5 @.>; Comment @.> Subject: Re: [home-assistant/core] Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device (Issue #100121)

This still happens for me. All I needed to do was pop open my most recent Home Assistant Core log to find 11 instances in the last few days.

Core 2024.10.3 Supervisor 2024.10.2 Operating System 13.2

Logger: homeassistant.components.roku.coordinator Source: helpers/update_coordinator.py:386 integration: Roku (documentationhttps://www.home-assistant.io/integrations/roku, issueshttps://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+roku%22) First occurred: October 20, 2024 at 11:18:10 AM (11 occurrences) Last logged: 6:30:33 AM Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/100121#issuecomment-2429886435, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARAH6EFXFJESFWLHEVVJTZTZ42FHPAVCNFSM6AAAAAA4TDPDFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZHA4DMNBTGU. You are receiving this because you commented.Message ID: @.***>

[ahahamyan]

Having the same issue. Occurring only with one of my 3 Roku Devices. I checked the device and even restarted it and it works perfectly fine. But I get this error in HA when trying to connect to it.

EDIT - I rebooted the HA instance and the issue went away. All of my 3 Roku devices are connected fine via HA.

[Dzoker2]

I'm having the same issue!

[DaveCBr]

I am having connection issues as above with all Roku devices and now also with Thin-Q devices.

Core 2024.11.2 Supervisor 2024.11.2 Operating System 13.2 Frontend 20241106.2

[DaveCBr]

I re-connected both of my Roku devices to my network and the issue was resolved. I did not locate a root cause, but I move on for now.

[Dzoker2]

Same here

Logger: homeassistant.components.roku.coordinator Source: helpers/update_coordinator.py:412 integration: Roku (documentation, issues) First occurred: February 13, 2025 at 06:33:27 (1 occurrences) Last logged: February 13, 2025 at 06:33:27

Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

[JustinTDCT]

I have 4 TV's, 2 work no issue and 2 drop afgter about 20min and i ahve to reboot the TV to get them back

[JustinTDCT]

F/U - I noted today if I turn off the TV thats when it drops; doesnt matter if I have app permission on enabled or whatever ... these are TCL ROKU TV's ... so it seems when you turn them off you cannot turn them back on without manually doing it

[blamaz]

F/U - I noted today if I turn off the TV thats when it drops; doesnt matter if I have app permission on enabled or whatever ... these are TCL ROKU TV's ... so it seems when you turn them off you cannot turn them back on without manually doing it

How to enable Fast TV Start on my TCL Roku TV

Your TCL Roku TV may not stay connected with your wireless network when powered off. To maintain the network connection and allow other wireless devices connect to your Roku device when powered off, use the steps below to enable the Fast TV Start feature on your TCL Roku TV:

Press the Home button on your TCL Roku TV remote
Scroll up or down, and select Settings
Select System, then Power 
Select Fast TV Start
Highlight Enable 'Fast TV Start', press the OK button on your TV remote.  This will check the box. 

Note: Fast TV Start uses more power than normal standby and will override default power settings.

[jzucker2]

F/U - I noted today if I turn off the TV thats when it drops; doesnt matter if I have app permission on enabled or whatever ... these are TCL ROKU TV's ... so it seems when you turn them off you cannot turn them back on without manually doing it

I think it's a relatively recent update. Have used TCL rokus for like 7/8 years with no issues and this started a few weeks ago right when the UI on the roku TV underwent noticeable changes.

[nathandace]

In the Roku advanced settings, there is a network setting to either allow full or limited remote access to the Roku. This must have been a newer setting pushed out. When I changed to full access, the integrations worked again.

[Dzoker2]

Just for reference, i have Roku Ultra with this error. The remote access setting that @nathandace mentioned have been present in Roku Ultra for some time and I can confirm that since I've set it to FULL, I have not seen this error again.

[jhemak]

Since 2025.7 I have been seeing this error (the original one from the very top of this thread) on a very regular basis (dozens of times per day). I have a Streaming Stick 4K. I was not seeing it very often previously and have not changed anything about my network or configuration. Is anyone else noticing this?

[Kdemontf]

Same error on Core 2025.7.2 with TCL Roku Smart TV. The error occurs for me when the TV is on, and switched off(standby mode). If HA is restarted with TV off, HA cannot reach API, but no error message.

[Shredder5262]

Saw this error when i just freshly booted my HA, Probably worth noteing that my roku TV is currently in an off/standby state

Logger: homeassistant.components.roku.coordinator Source: helpers/update_coordinator.py:424 integration: Roku (documentation, issues) First occurred: 9:57:37 PM (1 occurrence) Last logged: 9:57:37 PM

Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Kdemontf]

This issue still exists

[Dzoker2]

Issue still exist on my HA too