Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
2019-02-25 06:14:42.018 - Started
2019-02-25 06:14:42.096 - Network status is up
2019-02-25 06:14:46.003 - Connection with Pushbullet established
2019-02-25 06:14:46.034 - Startup command line request ...
2019-02-25 06:14:46.034 - StartNormal
2019-02-25 06:14:46.112 - no matching active phrases
It doesn't seem to cause a problem (though we're still testing after the Pushbullet outage), but did we miss something during the upgrade?
Problem is on my end, I will clean it up in the next release. Should not impact how the program works for you, so please just ignore it for now. Thanks, Rob
2019-03-01 08:40:04.271 - Incoming push ...
2019-03-01 08:40:04.271 - <Title> Normal Distribution
2019-03-01 08:40:04.271 - <Body> reboot
2019-03-01 08:40:04.271 - Title did not match Push2Run's title filter - no further action will be taken
Thing is, nobody told Google Home to reboot the computer at 08:40. I checked the IFTTT activity log and it shows that the applet ran at 06:10 but not at 08:40.
We did in fact use Google Home to reboot the machine at 06:10 and that worked, and we have since verified that Google Home can get Push2Run to open the calculator, etc. (it's now 09:42), so that 08:40 message appears to be spurious. Crossed wires, perhaps?
Neither phrase ('Normal Distribution' or 'reboot') would have or could have been generated out of Push2Run itself. Also, the log shows it as an incoming push, so it did come from Pushbullet. Do you have any other ifttt applets that send pushes? If not, and if it happens again, I would suggest changing your Pushbullet access token in both Pushbullet and Push2Run.
Aha. Mystery solved. In an attempt to prevent Pushbullet's "account inactive for 30-days" issue I told it to follow xkcd and added the Pushbullet extension to Chrome so the pushes had somewhere to go. On 03-01 Randall published a comic titled "Normal Distribution".
Today, Randall published a comic named "Video Orientation", and lo and behold:
2019-03-04 07:08:15.783 - Incoming push ...
2019-03-04 07:08:15.783 - <Title> Video Orientation
2019-03-04 07:08:15.783 - <Body>
2019-03-04 07:08:15.783 - Title did not match Push2Run's title filter - no further action will be taken
I don't know if a "follow" like that will be sufficient to keep the Pushbullet account active, but I guess I'll find out. (Or, if you have some other suggestion for a "keep alive" strategy I'd be most happy to hear it.)
Well, there's nothing better than a mystery solved!
I haven't had a problem with my Pushbullet account expiring, but I pay the annual fee so that may have something to do with it.
In any case, a while back I reported the issue with expiry accounts to Pushbullet, and recently - through the whole can't connect to Pushbullet thing - I was in contact with them again and they expressed interested in looking into the expiring account issue once they worked through some other things.
Hopefully, that will be sooner than later, and as appropriate I will post an update here.
Hello. Could you please help me? I did everything as you described in your manual. Downloaded push2run, IFTTT and pushover, Pushover connection in push2run is good, After I tell commant to my google assistant, he answers: OK, I told your computer..., etc... In the push2run window shows: message received "textfield" no matching active phrases. Below is the log. Do you know where could be the problem? Thanks for answer.
2019-12-24 13:31:46.201 - Incoming Pushover push ...
2019-12-24 13:31:46.201 - TextField
2019-12-24 13:31:46.295 - no matching active phrases