@Giorgio-Chiodi at the moment, the Pushbullet API is not mature enough to allow pushes to NodeBB... But it will be, soon!
However, this brings up the problem of which category to push to... 🙂
@pwFoo Agreed -- at current, the underlying library (Pushbullet) doesn't support that, although they're looking into implementing it...
Could notifications devided into a notification manager (should a notification be send?) at nodebb side and a notification gateway (for example pushbullet) to really send a message?
@julian is this plugin still premium?
@Kacper-Domański oh good lord I forgot about open sourcing it! Let me get right on that..!
@julian Updated OP for you
Has this been verified on v0.5.2-dev?
Can't seem to get OAuth working. What should "origin" field be set to when creating client keys?
@hek Err, actually, you know what, I haven't been getting pushes to my phone lately, but I think that might be because I got a new phone...
I haven't been getting any pushes either (and haven't changed my )
@fuzzmz Looking into it now mhmmmm
v1.1.1 published, should be fine on latest NodeBB now
After adding 1.1.1 I still get a 404 on the "/pushbullet/auth" url on the forum. So unless pushbullet does a POST request (which nodebb picks up) something still seems to be wrong.
Are you sure /pushbullet/auth is a valid express-route?
@hek As far as I know the
allowed_origin value was not there when I originally set up Pushbullet for NodeBB. It's still empty now for this install, and it seems to be working fine. Let me fix up another bug I found and I'll take a look at the
/auth route, thanks!
v1.1.2 is out, although I can't seem to reproduce your bug @hek. Are you trying to access
/pushbullet/auth manually? You should only be sent there by Pushbullet after granting authorization, and the url should look something like this:
@julian in my case i'm landing on approve pushbullet site and when i click approving small wheel starts turning and never stops
redirect_uri set properly in https://www.pushbullet.com/create-client ? Do you have the proper API id and secret saved into NodeBB (and was NodeBB reloaded after saving?)
@julian i was missing "http://" now working smooth
And now i'm getting notifications from this one too, sweet!
Excellent, glad to hear!
Got it working in our prod-env now. I have no idea why I couldn't get it started in stage.