@Smart-Communities, I know this isn't exactly what you were thinking, but I'm using your IP address placeholder idea in this video as an example of one way to share scripts with placeholders for things like IP address you'd store in config files. You could run a command like this remotely or locally to configure the IP:
roku ip 192.168.1.10
Then a command like this to simulate the down button on your roku remote:
roku keypress down
This article give a list names of other roku buttons.
@rem roku.bat
@echo off
echo %1 %2 %3 %4
if "%1"=="ip" goto :configip
if "%1"=="keypress" goto :keypress
if "%1"=="0" goto :findremote
if "%1"=="off" goto :findremote
goto :done
:configip
echo|set /p="%2" > c:\tools\rokuip.config
goto :done
:keypress
set /p IP= < c:\tools\rokuip.config
curl -XPOST http://%IP%:8060/keypress/%2
goto :done
:findremote
set /p IP= < c:\tools\rokuip.config
curl -XPOST http://%IP%:8060/keypress/FindRemote
goto :done
:done
echo Done.
This video shows that, and shows how to pass a number from 0 to 100 with Alexa using the TRIGGERcmd Smart Home skill by saying:
Alexa, roku on tv zero.
That works because Alexa interprets that as setting the dim level to 0 for the "roku on tv" device because roku is the command's voice word and tv is the computer's voice word.
Be aware if you use Google Assistant, when you say 0 it sends off as the parameter because it figures if you're setting the dim level to 0 percent, that's off. That's why I added this line after I recorded that video:
if "%1"=="off" goto :findremote
In hindsight 0 / off seems pretty arbitrary to assign to the making your Roku remote start beeping.
Also I acknowledge this a script so it's coding, so it doesn't solve the problem in the original post.
