A Viewer for Windows, Cast, NotifyOnDemand, Push2Run and SetVol

Hi all,

I have set up Push2Run with SetVol in the screenshot provided, and I cannot work out why it doesn't seem to work at all when I trigger it with the Google Assistant. If I run the trigger manually in Push2Run, and provide manually the volume level, it works fine. But when I actually say "Hey Google, tell my computer to set volume 50", all seems fine, and I see the request show up in the bottom of the Push2Run window with the correct command and parameter, but it does not actually execute. All my other triggers work fine, just this SetVol one.

Any help would be appreciated!

Thanks!

(P.S. The trigger is on, the screenshot is only showing Off as I have the Edit Window open)

It generally looks ok.

The screenshot is however a little cut-off, does the open field read:
c:\Program Files\SetVol\SetVol.exe

also, can you try exiting Push2Run and starting it up again. Does it sill not work?

Yep it is SetVol.exe at the end, and I have tried restarting Push2Run and my PC several times.

Well, it seems to be set up fine.

Let's dive a little deeper.

Can you please create a file called c:\Program Files\SetVol\test.bat that contains the following three lines:

call setvol report
echo %ERRORLEVEL%
pause

can you then please change the Push2Run card's open field to
c:\Program Files\Setvol\test.bat

Please also change the Push2Run card's WIndows State from Minimized to Normal and give it another shot.

Please let me know what you see in the output window.

Sure, here is the output of that after telling Google Assistant to Set Volume 50, while currently at 100.

ok - so that is working fine. Can you now please change the .bat file to:

call setvol %1 report
echo %ERRORLEVEL%
pause

and again give it a test, and let me know how it worked.

Sure, here you go!

Do you have your session log from the above command as well. It looks like an 'e' got passed over instead of the number.

Also, can you please be sure you are running the most current version of the program, version 3.4.2 (which you can get from the website www.push2run.com ) - I had something similar reported as a problem a while back but fixed it in the code - so maybe why it's working for me and not you?