Commands not executing due to poor formatting? Enlighten my smooth brain, please

[marky310]

So I recently dislocated my knee and the need to get rest has me hating any time I need something from my PC, which led me to this excellent app. I tried setting it up and I double checked I followed the setup but I can't seem to run any voice commands, with the log telling me it's not in the right format:

2020-08-02 02:34:43.294 - Push2Run version 3.0.3.0 started

2020-08-02 02:34:43.348 - Windows UAC notify feature is off

2020-08-02 02:34:43.350 - Administrative privileges are effectively enabled

2020-08-02 02:34:43.868 - Current network adapter is Ethernet 3

2020-08-02 02:34:44.065 - Network status is up

2020-08-02 02:34:45.554 - Dropbox monitoring begun for C:\Users\marky\Dropbox\Apps\Push2Run\

2020-08-02 02:36:36.863 - Incoming Dropbox trigger ...

2020-08-02 02:36:37.866 - Processing Dropbox file: C:\Users\marky\Dropbox\Apps\Push2Run\Command.txt
2020-08-02 02:36:37.866 - File contents:
Push2Run_MunsterDog

start the calculator
August 2, 2020 at 02:36AM

2020-08-02 02:36:37.870 - Incoming file does not contain the expected information in the right format
2020-08-02 02:36:37.874 - The first line should identify the computer(s) for the command to run on
2020-08-02 02:36:37.875 - The second line should contain the command
2020-08-02 02:36:37.877 - For example:
2020-08-02 02:36:37.878 - Push2Run_MunsterDog
2020-08-02 02:36:37.879 - open the calculator
2020-08-02 02:36:37.882 - August 02, 2020 at 02:36AM
2020-08-02 02:36:37.883 - No further action will be taken
2020-08-02 02:36:37.884 - Deleting : C:\Users\marky\Dropbox\Apps\Push2Run\Command.txt

2020-08-02 02:37:51.942 - Incoming Dropbox trigger ...

2020-08-02 02:37:52.943 - Processing Dropbox file: C:\Users\marky\Dropbox\Apps\Push2Run\Command.txt
2020-08-02 02:37:52.943 - File contents:
Push2Run_MunsterDog

start the calculator
August 2, 2020 at 02:37AM

2020-08-02 02:37:52.943 - Incoming file does not contain the expected information in the right format
2020-08-02 02:37:52.944 - The first line should identify the computer(s) for the command to run on
2020-08-02 02:37:52.944 - The second line should contain the command
2020-08-02 02:37:52.944 - For example:
2020-08-02 02:37:52.944 - Push2Run_MunsterDog
2020-08-02 02:37:52.944 - open the calculator
2020-08-02 02:37:52.945 - August 02, 2020 at 02:37AM
2020-08-02 02:37:52.945 - No further action will be taken
2020-08-02 02:37:52.945 - Deleting : C:\Users\marky\Dropbox\Apps\Push2Run\Command.txt

I get the notification that it created the "command.txt" file but then it instantly disappears, which is reflected in the log. I'm sure its something I'm completely blind to, but if anyone could help me correct what I'm doing wrong, me and my knee would definitely appreciate it

[RobLatour]

ok so that is weird.

It appears you have everything set up ok, but in the command file that IFTTT is sending you there is a blank line right after the first line:


2020-08-02 02:37:52.943 - Processing Dropbox file: C:\Users\marky\Dropbox\Apps\Push2Run\Command.txt
2020-08-02 02:37:52.943 - File contents:
Push2Run_MunsterDog

start the calculator
August 2, 2020 at 02:37AM

I thought it may have been due to the length of your title field, but tested on my machine and it was not (everything is working fine):

2020-08-03 16:09:25.082 - Processing Dropbox file: C:\Users\Rob Latour\Dropbox\Apps\Push2Run\Command.txt
2020-08-03 16:09:25.082 - File contents:
Push2Run_MunsterDog
open the calculator
August 3, 2020 at 04:09PM


Can you please go in and edit your IFTTT applet, I'm think there may be something in it that we are not seeing; like a white space after the <br> in the first line. For example, what is in your IFTTT applet is really Push2Run_MunsterDog<br>(space)

Please check that and let me know if that helped.

[marky310]

You are a genius, sir. I erased any spaces in between and now its working perfectly. Now I don't have to grab my crutches every time I forget to turn my pc off. Thanks so much

[RobLatour]

Great, glad to have helped ...

and thank you for including all the screenshots, it made what would have otherwise been a difficult issue to track down issue much easier to solve.