I've the 55 Inch TCL Roku TV and recently the Voice Remote stopped working but the IR remote does. I can restore the Voice Remote if I restart the set (full system restart, not just turning it off and on).
It all seemed to start since a recent software upgrade to the set and I'm uncertain as to when the set and the remote break the connection but it is usually within a 24 hour period.
Removing and reinstalling the batteries (rebooting the remote) doesn't solve this and I've swapped out the remote with another voice remote, and still have the same problem.
The only thing that restores the remote function is restarting the set.
TCL model 55S435
Software Version 11.5.0 build 4225-93
Last update was 10-18-22'
In writing this, I see there has been another update already since my last one, I'm going to try that but seeing as how the restart will no doubt reconnect with the remote, I may not know for a day if it solved the problem.
In follow-up, the latest upgrade has not solved the problem. What is curious is that the disconnect occurs overnight - or seemingly so.
I wonder if this is a hardware failure with the TV?
I guess I need to contact support directly.
JamieClaye I have the exact same problem with my TCL 50" Roku tv, if you look at the post directly above yours. It's due to something in the 11.5 firmware, and an older firmware voice remote. You only need to do a regular power-down with the remote power button, and wait about 1/2 hour. The RF voice remote will no longer work, until a full power cycle.
I bought this much newer model voice remote, and now it stays paired no matter what. I suggest you also try it. $20 isn't worth spending more time on, and I'm sure it'll work for you also:
Thanks! I missed the similar post and yes, a $20 remote certainly is hard to argue with in terms of time spent troubleshooting this.
I just hate having to replace functional hardware, grrrr.
Maybe they'll fix it. 🙂
Thanks again!
Thanks for the post and providing us with your device information.
I have passed along your concerns and details to the appropriate Roku team to investigate further.
Thanks,
Danny
