EventGhost

Posted: **Tue May 27, 2014 8:11 pm**

Yes, now I understand exactly.
Everything you need is {eg.event.payload[0]}.
That you type into the text box in the configuration dialog of action System:Copy string to the system clipboard.

Pako

Posted: **Tue May 27, 2014 9:10 pm**

Thanks, that works! I don't know what I was doing wrong before, oh well!

Now, my next question is how do I trigger an action any time a link is pushed? Right now, if I use an event from the log, only that exact same push will trigger an action. I'd like it so that ANY link pushed to eventghost will trigger something. Is this possible?

THANKS!

Posted: **Wed May 28, 2014 3:46 am**

therealbiglou wrote:Right now, if I use an event from the log, only that exact same push will trigger an action. I'd like it so that ANY link pushed to eventghost will trigger something. Is this possible?

Yes, it is of course also possible.
You have to use the event as PushBullet.Link.*.

Pako

Posted: **Thu May 29, 2014 8:12 am**

Hi
Im still getting regular messages from pushbullet
I think it may be when my phone is getting a message but that its not showing up in eventghost but I cant be sure.
This is on logging level 3

Code: Select all

08:46:37   PushBullet: Haven't seen a nop lately, reconnecting
08:46:37   PushBullet: WebSocket closed
08:47:12   PushBullet: Haven't seen a nop lately, reconnecting
08:47:12   PushBullet: WebSocket closed
08:47:47   PushBullet: Haven't seen a nop lately, reconnecting
08:47:47   PushBullet: WebSocket closed
08:48:22   PushBullet: Haven't seen a nop lately, reconnecting
08:48:22   PushBullet: WebSocket closed
08:48:57   PushBullet: Haven't seen a nop lately, reconnecting
08:48:57   PushBullet: WebSocket closed
08:49:32   PushBullet: Haven't seen a nop lately, reconnecting
08:49:32   PushBullet: WebSocket closed
08:50:08   PushBullet: Haven't seen a nop lately, reconnecting
08:50:08   PushBullet: WebSocket closed
08:50:43   PushBullet: Haven't seen a nop lately, reconnecting
08:50:43   PushBullet: WebSocket closed
08:51:18   PushBullet: Haven't seen a nop lately, reconnecting
08:51:18   PushBullet: WebSocket closed
08:51:53   PushBullet: Haven't seen a nop lately, reconnecting
08:51:53   PushBullet: WebSocket closed
08:52:28   PushBullet: Haven't seen a nop lately, reconnecting
08:52:28   PushBullet: WebSocket closed
08:53:03   PushBullet: Haven't seen a nop lately, reconnecting
08:53:03   PushBullet: WebSocket closed
08:53:38   PushBullet: Haven't seen a nop lately, reconnecting
08:53:38   PushBullet: WebSocket closed
08:54:14   PushBullet: Haven't seen a nop lately, reconnecting
08:54:14   PushBullet: WebSocket closed
08:54:49   PushBullet: Haven't seen a nop lately, reconnecting
08:54:49   PushBullet: WebSocket closed
08:55:24   PushBullet: Haven't seen a nop lately, reconnecting
08:55:24   PushBullet: WebSocket closed
08:55:59   PushBullet: Haven't seen a nop lately, reconnecting
08:55:59   PushBullet: WebSocket closed
08:56:34   PushBullet: Haven't seen a nop lately, reconnecting
08:56:34   PushBullet: WebSocket closed
08:57:10   PushBullet: Haven't seen a nop lately, reconnecting
08:57:10   PushBullet: WebSocket closed
08:57:45   PushBullet: Haven't seen a nop lately, reconnecting
08:57:45   PushBullet: WebSocket closed
08:58:20   PushBullet: Haven't seen a nop lately, reconnecting
08:58:20   PushBullet: WebSocket closed
08:58:55   PushBullet: Haven't seen a nop lately, reconnecting
08:58:55   PushBullet: WebSocket closed
08:59:30   PushBullet: Haven't seen a nop lately, reconnecting
08:59:30   PushBullet: WebSocket closed
09:00:05   PushBullet: Haven't seen a nop lately, reconnecting
09:00:05   PushBullet: WebSocket closed
09:00:41   PushBullet: Haven't seen a nop lately, reconnecting
09:00:41   PushBullet: WebSocket closed
09:01:16   PushBullet: Haven't seen a nop lately, reconnecting
09:01:16   PushBullet: WebSocket closed
09:01:51   PushBullet: Haven't seen a nop lately, reconnecting
09:01:51   PushBullet: WebSocket closed
09:02:26   PushBullet: Haven't seen a nop lately, reconnecting
09:02:26   PushBullet: WebSocket closed
09:03:06   PushBullet: Haven't seen a nop lately, reconnecting
09:03:06   PushBullet: WebSocket closed
09:03:41   PushBullet: Haven't seen a nop lately, reconnecting
09:03:41   PushBullet: WebSocket closed
09:04:17   PushBullet: Haven't seen a nop lately, reconnecting
09:04:17   PushBullet: WebSocket closed
09:04:52   PushBullet: Haven't seen a nop lately, reconnecting
09:04:52   PushBullet: WebSocket closed
09:05:27   PushBullet: Haven't seen a nop lately, reconnecting
09:05:27   PushBullet: WebSocket closed
09:06:02   PushBullet: Haven't seen a nop lately, reconnecting
09:06:02   PushBullet: WebSocket closed
09:06:37   PushBullet: Haven't seen a nop lately, reconnecting
09:06:37   PushBullet: WebSocket closed
09:07:12   PushBullet: Haven't seen a nop lately, reconnecting

Posted: **Thu May 29, 2014 9:02 am**

Probably it is a problem caused by the transition to the new API.
Obviously this is a case with which I was not encountered and therefore I could not react to it.
Logging level 3 unfortunately says nothing. Please switch to the level 5.
I hope it will be enough to find the cause.

Pako

Posted: **Thu May 29, 2014 11:06 am**

Logging at 5 doesnt add a lot but maybe it helps?

Code: Select all

12:01:13   PushBullet: Haven't seen a nop lately, reconnecting
12:01:13   PushBullet: WebSocket closed
12:01:13   PushBullet: Adding push messaging listener
12:01:48   PushBullet: Haven't seen a nop lately, reconnecting
12:01:48   PushBullet: WebSocket closed
12:01:48   PushBullet: Adding push messaging listener
12:02:23   PushBullet: Haven't seen a nop lately, reconnecting
12:02:23   PushBullet: WebSocket closed
12:02:23   PushBullet: Adding push messaging listener
12:02:58   PushBullet: Haven't seen a nop lately, reconnecting
12:02:58   PushBullet: WebSocket closed
12:02:58   PushBullet: Adding push messaging listener
12:03:34   PushBullet: Haven't seen a nop lately, reconnecting
12:03:34   PushBullet: WebSocket closed
12:03:34   PushBullet: Adding push messaging listener
12:04:09   PushBullet: Haven't seen a nop lately, reconnecting
12:04:09   PushBullet: WebSocket closed
12:04:09   PushBullet: Adding push messaging listener
12:04:44   PushBullet: Haven't seen a nop lately, reconnecting
12:04:44   PushBullet: WebSocket closed
12:04:44   PushBullet: Adding push messaging listener
12:05:19   PushBullet: Haven't seen a nop lately, reconnecting
12:05:19   PushBullet: WebSocket closed
12:05:19   PushBullet: Adding push messaging listener

Posted: **Thu May 29, 2014 11:12 am**

Phil wrote:Logging at 5 doesnt add a lot but maybe it helps?

It is strange and it unfortunately does not help.
So I do not know what to do.
You can attach the beginning of the log after restarting EventGhost?

Pako

Posted: **Fri May 30, 2014 10:03 am**

New version (0.0.17) released.
Only bugfix.
Pako

Posted: **Fri May 30, 2014 12:57 pm**

Thanks for your help Pako, much appreciated.

Posted: **Fri May 30, 2014 4:53 pm**

New version (0.0.18) released.
Only bugfix (when 'title' parameter is missing in a received "Mirror").

Pako

Posted: **Fri Jun 06, 2014 7:24 pm**

For those of you who are Popcorn Time users, I created a guide to add Chromecast-like functionality to it using Pushbullet. You can find that here: http://www.reddit.com/r/PopCornTime/com ... et_to_add/

Posted: **Sun Jun 15, 2014 4:32 pm**

OK, so I try to control Screamer Radio favourites station via Pushbullet.

I have 13 favourites station. Push is a note, with title set as favourite number.

When I set python script:

Code: Select all

fav = eg.event.payload[0]
eg.plugins.ScreamerRadio.SelectFav(fav)

And push 3 as note title I've got strange error:

Code: Select all

      Python Script
         Too large number (3 > 13) !

Why? 3 is not bogger than 13?

Posted: **Mon Jun 16, 2014 3:48 am**

hoStage wrote:Why? 3 is not bogger than 13?

Because we do not see the quotation marks.

In fact, it is like a "3" > 13.
Help is easy. Do this as follows:

Code: Select all

eg.plugins.ScreamerRadio.SelectFav(int(fav))

Pako

Posted: **Sun Jun 22, 2014 10:28 am**

Reply To Text Messages Right From Your Computer

Posted: **Sun Jun 22, 2014 10:40 am**

New version (0.0.19) released.
News:

first version for release r1669 and later (no need to install libraries)
mirror notifications are customizable now (colour, monitor, alignment)
introduced a new event "ReplyAllowingMirror"
added an action "Send reply to mirror"
if there is a possibility to send a reply, then on the mirror notification is a new button Reply

Notes:

It only works with EventGhost release r1669 or later
You can delete the folder "lib" (from the directory ...\EventGhost\plugins\PushBullet).

Pako

EventGhost

PushBullet plugin (Pako)

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin

Re: PushBullet plugin (Pako)

Re: PushBullet plugin (Pako)

Re: PushBullet plugin (Pako)

Re: PushBullet plugin (Pako)

Re: PushBullet plugin (Pako)