Pushbullet Connection and IFTTT Good, but No Command Execution

[Ginseng]

Hi all,

I had Push2Run working on my PC a while ago, but then didn't for a while and my Pushbullet account became deactivated due to inactivity.

Today I decided to set it up again, as Push2Run was still installed on my PC. I deleted my old Pushbullet account, made a new one with the same credentials/login method, generated a new API access token, added that to my Push2Run settings, and re-linked my Pushbullet account to IFTTT.

However, when I execute a command, it doesn't work. I tell my Google Home to "tell my computer to [command]", to which it responds "OK, I will tell your computer to [command]". But then, nothing happens.

Push2Run seems to be good as well, and I just re-made my Pushbullet account as well so I'm not sure what the issue is. Here is my session log:

2020-02-27 15:12:53.959 - Push2Run version 3.0.0.0 started

2020-02-27 15:12:53.968 - Windows UAC notify feature is off

2020-02-27 15:12:53.968 - Administrative privileges are effectively enabled

2020-02-27 15:12:54.030 - Current network adapter is Ethernet

2020-02-27 15:12:54.051 - Network status is up

2020-02-27 15:12:55.195 - Connection with Pushbullet established

Meanwhile, my Pushbullet and IFTTT look fine:



If someone could shed some light on what's going on, that would be great!

Thanks,
Gin

[RobLatour]

Can you please go to IFTTT, click on the picture of a person's head (top right), and click on Activity.

What is it saying in terms of the applet you are running?

[Ginseng]

As an update, this has since been fixed. Had to close everything down and start it back up again after 30 minutes.

Not sure as to the root cause, but one of the services that Push2Run uses to operate needed some time to update its authentication and use the new access token that I'd generated. After that, it has been working since then.

[RobLatour]

Great, thanks for the update.

[Milesley]

How long did it actually take to update the authentication? Are we talking hours here?