Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
so if I mapped this command to a button on remote
LaunchApp.{{activeroom_{{clientname}}}}|Netflix
and created a macro named livingroom.LaunchApp
with this code
AV|{{livingroom_shieldtv_id}}~Launch~<p1>!
in it
Would it Work?
YES!
Please Log in or Create an account to join the conversation.
I've got the reverse problem. My smart remote template has the hard button calling power.familyroom | on, but my macros are still the old ones: poweron.familyroom.We want to try to reduce the number of macros being created but wasn't expecting someone to reflash a new server so soon. Instead of VolumeUp, VolumeDown, PowerOn, PowerOff it's better to have just one Volume and Power macro and pass in the options as needed.
Volume.room|up or Volume.room|up~3 (up 3 steps) Volume.room|down or Volume.room|down~3 (down 3 steps)
VolumeMute.room|on or VolumeMute.room|off or VolumeMute.room|toggle
Power.room|on or Power.room|off or Power.room|toggle
The updated smartremote, moonlight tablet and phone templates will be calling these macros.
This should not break anything for existing installs using the old macro naming conventions as the server will compensate. Since you are a little ahead of the curve modify your project hard button commands to use the new macro naming conventions.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.