Roku remote pro not voice command not working
- 11 months ago
We're grateful to have you here in the Roku Community, ECDC!
Thank you for sharing your concern about the voice command feature on your physical Roku remote. We're here to determine the cause and find you the best resolution.
If you have factory reset your Roku Ultra manually, which is located on the back or bottom of your device, the physical Reset button is either tactile or a pinhole design that requires a straightened paperclip; you have to press and hold the reset button for about 10 seconds only.
When the factory reset is complete, most Roku devices have an indicator light or status LED that blinks rapidly.
Furthermore, if you only have one physical Roku remote paired to this device, you can't remove this remote effectively. If you want to reboot it, you may try this:
If your voice remote has a rechargeable battery, follow the steps below below to reboot your remote
- If your rechargeable voice remote has a pairing button, press and hold the pairing button on the back of the remote for 20 seconds.
- If your rechargeable voice remote does not have a pairing button, press and hold the Back and Home for 20 seconds.
For references, here are the support articles dedicated to this:
- How to fix your Roku voice remote that is not working
- How to system restart or factory reset your Roku streaming device
Please keep us posted on how it goes!
Best regards,
Carly - 11 months ago
Hello! Danno1377,
Thank you for your post in the Roku Community!
We understand you are experiencing issues with your Roku remote Pro voice command not working. We are happy to assist.
Since you have tried all the possible troubleshooting steps to fix your Roku remote, please provide us with the following information being asked by @RokuCarly. Once we have this information, we can pass it along to the appropriate Roku team for further investigation.
In the meantime, you can use the Roku mobile app to control your streaming device.
We look forward to working with you to help resolve this issue.
Thanks,
Arjiemar