Hi Everyone, I've seen a few posts dating back to over a year ago with this issue, but this just happened about 4 days ago where Google Home says its unavailable right now, I've restarted both, rebooted the home network, check settings incase they changed (no changes).
@JuanMaddox1 Thanks for the note. This issue can occur if you are trying to use your Roku TV in a location that this feature is not currently supported, or may occur if you are using location altering software such as a VPN, etc. The Roku skill for Google Assistant is only currently supported in the US at this time.
I am having the same problem and am in the US. It started about two days ago. I have fast start enabled, everything was working fine and now Google Home says my Roku is not responding. When I pull up the Roku TV in the Google Home app, it shows the Roku as "Not Responding". I have unlinked the Roku in the Google Home app and it doesn't help. I can unplug the TV, wait about 5 minutes and plug it back in and everything will work find until I turn the TV off and come back after an hour or so and Google Home says the Roku TV is not responding. Any Suggestions?
- No, I do not see a time/clock appearing in the upper righthand corner of my Roku TV. The message about the Roku is not responding is in the Google Home app, not on the tv.
Update: When I posted my previous message, the Goggle Home was saying that the Roku TV was not available. I left the house for about four hours and when I returned, everything was working again. The Google Home turned on my Roku with no problem. This is the first time it corrected itself without me unplugging the TV and restarting it.
I’m confused if you even read our actual complaints. For everyone you continue to reply with the same things. Even asking the last poster I’d he had fast start turned on after he had previously stated he did. I am having the same issue with it not working with google home. It was fine when first installed. Then not even 5 mins later it says the roku is unavailable. This is issue needs resolved not called solved after you in no way helped the problem. This is very poor support.