Hi.
I'm guilty of being a new user! So please forgive if the answer to my question is obvious (but not to me).
I have a Google Assistant (GA) command to make my PC sleep and use the Push2Run Dropbox interface as I had an existing Dropbox account.
The links all work fine and if I state the command directly to GA - all good.
So I added the GA command to my GA "Goodbye" routine so that the PC would be put to sleep mode when I leave home. Works fine.
BUT
If the PC happened to already be in Sleep mode when I say GA Goodbye, it seems that the following occurs:
1. GA triggers the IFTTT applet which creates the Dropbox command file in the Dropbox cloud.
2. When I come home and wake the PC, the Dropbox Cloud updates the local Dropbox folder with the command file - which was created previously
3. Push2Run sees the command file and acts upon it - and immediately puts the PC to sleep again
Is anyone aware of a way to overcome this? EG by Push2Run somehow ignoring the aged file, or by deleting it prior to Push2Run seeing it?
Any advice will be appreciated.
Thank you.
Possible timeout on Dropbox command file?
Re: Possible timeout on Dropbox command file?
Welcome.
This problem was first reported a few days ago by another user, and I just released a new version of the program to address it.
For more information, please see: viewtopic.php?f=7&t=859
But to summarize, to correct this, you will need to:
1. download and install version 3.0.2 form the website ( www.push2run.com )
and
2. update your IFTTT applet as described in step 14 here: https://push2run.com/setup_dropbox.html
and that should be it.
Hope this helps.
This problem was first reported a few days ago by another user, and I just released a new version of the program to address it.
For more information, please see: viewtopic.php?f=7&t=859
But to summarize, to correct this, you will need to:
1. download and install version 3.0.2 form the website ( www.push2run.com )
and
2. update your IFTTT applet as described in step 14 here: https://push2run.com/setup_dropbox.html
and that should be it.
Hope this helps.
Re: Possible timeout on Dropbox command file?
Seems to have resolved the problem Rob!
Thank you for your quick response.
Thank you for your quick response.
Re: Possible timeout on Dropbox command file?
Hi.
This has been working for for a while - but suddenly my Command.txt files are being created as Command (1).txt, then 2, 3 etc. So the file name does not match what Push2Run is looking for. Screen snip attached.
I have double-checked my IFTTT applet and it is unchanged - still says to create Command.txt.
Any thoughts/suggestions?
Thank you.
This has been working for for a while - but suddenly my Command.txt files are being created as Command (1).txt, then 2, 3 etc. So the file name does not match what Push2Run is looking for. Screen snip attached.
I have double-checked my IFTTT applet and it is unchanged - still says to create Command.txt.
Any thoughts/suggestions?
Thank you.
- Attachments
-
- Capture.JPG (23.62 KiB) Viewed 3903 times
Re: Possible timeout on Dropbox command file?
Can you please include a copy of the contents of your session log after you issue a command.
To get the copy of the contents of your Push2Run session log, Please go to the Push2Run main window, click on View - Session log and then on the window that pops-up ‘Copy to clipboard’, after that you will be able to paste (Ctrl-v) the contents of your clipboard into a reply post.
Thanks
To get the copy of the contents of your Push2Run session log, Please go to the Push2Run main window, click on View - Session log and then on the window that pops-up ‘Copy to clipboard’, after that you will be able to paste (Ctrl-v) the contents of your clipboard into a reply post.
Thanks
Re: Possible timeout on Dropbox command file?
Thanks Rob - session log follows:
2020-04-22 08:53:02.920 - Push2Run version 3.0.2.0 started
2020-04-22 08:53:02.948 - Windows UAC notify feature is on
2020-04-22 08:53:02.961 - Normal privileges are in effect
2020-04-22 08:53:03.198 - Current network adapter is Ethernet
2020-04-22 08:53:03.338 - Network status is up
2020-04-22 08:53:03.935 - Dropbox monitoring begun for C:\Users\Electric\Dropbox\Apps\Push2Run\
2020-04-22 10:07:50.900 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 13:38:11.168 - Current network adapter is Ethernet
2020-04-22 15:46:10.513 - Incoming Dropbox trigger ...
2020-04-22 15:46:11.568 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 15:47:00.184 - Incoming Dropbox trigger ...
2020-04-22 15:47:01.225 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 15:47:57.837 - Incoming Dropbox trigger ...
2020-04-22 15:47:58.872 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 15:49:31.656 - Incoming Dropbox trigger ...
2020-04-22 15:49:32.698 - Dropbox file contents:
Push2Run_Electric
make pc sleep
April 22, 2020 at 03:49PM
2020-04-22 15:49:32.789 - action completed
2020-04-22 15:49:41.285 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 18:27:59.030 - Current network adapter is Ethernet
2020-04-22 18:28:01.926 - Incoming Dropbox trigger ...
2020-04-22 18:28:02.941 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 18:35:09.809 - Incoming Dropbox trigger ...
2020-04-22 18:35:10.827 - Dropbox file contents:
Push2Run_Electric
make pc sleep
April 22, 2020 at 06:34PM
2020-04-22 18:35:10.910 - action completed
2020-04-22 18:35:18.660 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 18:36:21.021 - Current network adapter is Ethernet
2020-04-22 18:36:22.942 - Incoming Dropbox trigger ...
2020-04-22 18:36:23.957 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 18:36:23.963 - Incoming Dropbox trigger ...
2020-04-22 18:36:24.975 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 18:38:46.955 - Incoming Dropbox trigger ...
2020-04-22 18:38:47.983 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 19:37:10.443 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 19:39:51.017 - Current network adapter is Ethernet
2020-04-22 20:36:43.951 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 20:53:18.021 - Current network adapter is Ethernet
2020-04-22 21:25:11.372 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 21:56:58.032 - Current network adapter is Ethernet
2020-04-22 08:53:02.920 - Push2Run version 3.0.2.0 started
2020-04-22 08:53:02.948 - Windows UAC notify feature is on
2020-04-22 08:53:02.961 - Normal privileges are in effect
2020-04-22 08:53:03.198 - Current network adapter is Ethernet
2020-04-22 08:53:03.338 - Network status is up
2020-04-22 08:53:03.935 - Dropbox monitoring begun for C:\Users\Electric\Dropbox\Apps\Push2Run\
2020-04-22 10:07:50.900 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 13:38:11.168 - Current network adapter is Ethernet
2020-04-22 15:46:10.513 - Incoming Dropbox trigger ...
2020-04-22 15:46:11.568 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 15:47:00.184 - Incoming Dropbox trigger ...
2020-04-22 15:47:01.225 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 15:47:57.837 - Incoming Dropbox trigger ...
2020-04-22 15:47:58.872 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 15:49:31.656 - Incoming Dropbox trigger ...
2020-04-22 15:49:32.698 - Dropbox file contents:
Push2Run_Electric
make pc sleep
April 22, 2020 at 03:49PM
2020-04-22 15:49:32.789 - action completed
2020-04-22 15:49:41.285 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 18:27:59.030 - Current network adapter is Ethernet
2020-04-22 18:28:01.926 - Incoming Dropbox trigger ...
2020-04-22 18:28:02.941 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 18:35:09.809 - Incoming Dropbox trigger ...
2020-04-22 18:35:10.827 - Dropbox file contents:
Push2Run_Electric
make pc sleep
April 22, 2020 at 06:34PM
2020-04-22 18:35:10.910 - action completed
2020-04-22 18:35:18.660 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 18:36:21.021 - Current network adapter is Ethernet
2020-04-22 18:36:22.942 - Incoming Dropbox trigger ...
2020-04-22 18:36:23.957 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 18:36:23.963 - Incoming Dropbox trigger ...
2020-04-22 18:36:24.975 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 18:38:46.955 - Incoming Dropbox trigger ...
2020-04-22 18:38:47.983 - Incoming filename did not match Dropbox filename in options- no further action will be taken
2020-04-22 19:37:10.443 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 19:39:51.017 - Current network adapter is Ethernet
2020-04-22 20:36:43.951 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 20:53:18.021 - Current network adapter is Ethernet
2020-04-22 21:25:11.372 - Current network adapter is Loopback Pseudo-Interface 1
2020-04-22 21:56:58.032 - Current network adapter is Ethernet
Re: Possible timeout on Dropbox command file?
PS - there was one successful result after I manually cleared the Dropbox folder. The problem might be somehow related to the prior issue where a command is issued after the PC is already sleeping and for some reason the prior Command.txt file is still present.
Re: Possible timeout on Dropbox command file?
ok thanks
When Push2Run receives the Command.txt file it processes it, and then deletes it.
That seemed to work in one case above, but after that other files were coming in called Command (1),txt, Command (2).txt etc.
I suspected what is happening is that you have another computer/cell phone/something that also has access to your dropbox but is not being kept in sync. That is to say, when Dropbox deletes the file on your PC, it does get deleted through synchronization on your other machine.
I'll see what kind of workaround I can do, in the meantime, perhaps you can check to see if that is perhaps the case for you.
Rob
When Push2Run receives the Command.txt file it processes it, and then deletes it.
That seemed to work in one case above, but after that other files were coming in called Command (1),txt, Command (2).txt etc.
I suspected what is happening is that you have another computer/cell phone/something that also has access to your dropbox but is not being kept in sync. That is to say, when Dropbox deletes the file on your PC, it does get deleted through synchronization on your other machine.
I'll see what kind of workaround I can do, in the meantime, perhaps you can check to see if that is perhaps the case for you.
Rob
Re: Possible timeout on Dropbox command file?
Hi Rob.
Yes multiple devices have access to Dropbox but that has been the case all along so I am unaware why a synchronisation problem would suddenly occur.
It is possible though that Google Assistant could issue multiple commands while the PC is asleep. Could this account for the anomaly?
Regards,
Peter.
Yes multiple devices have access to Dropbox but that has been the case all along so I am unaware why a synchronisation problem would suddenly occur.
It is possible though that Google Assistant could issue multiple commands while the PC is asleep. Could this account for the anomaly?
Regards,
Peter.
Re: Possible timeout on Dropbox command file?
Hi pjmcnally,
I’ve coded and tested what I believe should be a fix for the issue you have reported. If you would like to try it out the beta can be found here:
Push2RunSetupv303beta.exe
If you do try it out, I would appreciate your comments.
I’ve coded and tested what I believe should be a fix for the issue you have reported. If you would like to try it out the beta can be found here:
Push2RunSetupv303beta.exe
If you do try it out, I would appreciate your comments.