No one will help, Google sends me to Roku, Roku sends me to Google, Google sends me back to Roku, Roku sends me to TCL, TCL sends me back to Roku....I went in circles for a week so I gave up, they obviously don't want to help
That's, ummm, "interesting". I've always found voice commands to be too inconsistent to bother with except for having alexa power on/off and maybe start some of the apps (recognizes some, doesn't some). But, it looks like each app handles voice differently. YouTube seems to not recognize "pause" at all whether send from the remote, the phone app, or alexa. Amazon Video recognizes the word but doesn't have it as a command and doesn't do anything. Plex recognizes the word and pauses, but unless pronounced very carefully when using the remote it would mistake it for "I was", exit from the app and do a search instead. It always worked from the phone app or alexa, though (alexa being easier since it's always listening).
I’m absolutely willing to bet it has nothing to do with your TV and has everything to do with either Roku, the YouTube app or some mixture of the two (probably more the YouTube app). Saying this as a developer of sorts myself. Interestingly, you can reproduce this issue strictly with the Roku on it’s own (with the YouTube app loaded) as described in another thread by simply using the Mic button on the remote control.
As it turns out @JakeK1 the YouTube app does support voice; it’s just that every single thing you say (except explicitly for those commands that appear to be specific to control, e.g. pause, play, resume) result in searching while in the YouTube app. And, I reckon that the Google Assistant integration funnels into the same functionality, hence the oddly buggy but consistent failure.