Phone Notifications

ronny3050

@tnorling thanks for the information! You’re indeed correct in stating that there is a ratelimit associated with requesting pushes. It indeed seems like an unsolvable issue, given that once we request a push, the JSON response is already sent, even if it is streamed. :(

The json response comes in whenever a new event occurs, however, we could maintain a stack of current pushes and dismissals. The wait time could then be dynamic shortened if a dismissal is found in the stack.

Will this work?

tnorling

@ronny3050 I’m not sure if I quite understand. It seems to me that any time there is activity on pushbullet we get a ping saying “hey look at me, I have new information for you” and then we check to see what event occurred and act accordingly. And from what I understand any time pushbullet notifies us of activity it counts towards the ratelimit because that’s when the websocket gets opened. So unless it’s dependent on when you read the JSON, the only way I see us limiting the rate at which we make requests is by periodically checking the JSON and parsing the new information rather than listening for new activity. Which kind of defeats the purpose.

Of course I could be wrong about all this, I’m not super familiar with websockets or the API. We might be stuck with the way it is, but it works well enough as long as your phone isn’t receiving a ton of notifications at one time.

malicious_banjo

The very first time I set up this module I was getting notifications. After about ten minutes my log started reporting rateLimit errors, and notifications stopped coming in.

Since then, notifications don’t work at all. I’ve tried resetting all my tokens and starting over, I’ve completely removed/reinstalled the module, still nothing. I even bought a month of pro to see what would happen.

The log isn’t reporting any problems, it’s basically like my mirror doesn’t even know it’s connected to my account. Any ideas to fix it?

ronny3050

@malicious_banjo do you use Pushbullet a lot? There’s a limit on how many requests are given out per user.

If you use Pushbullet outside of this module, it is possible that you ran out of requests.

Seems like a good course of action will be to custom create an Android app that will push notifications.

ronny3050

@tnorling what do you say we create our own mobile application for both Android and iOS that can push notifications. This way, we won’t have to rely on Pushbullet and can control push limits.

malicious_banjo

@ronny3050 Nope, I made a PushBullet specifically for this module. The error returned after just two notifications on the mirror.

I can get a single notification to appear now, but only from the “Send Test Notification” button from the Mirroring menu on the Pushbullet app. The console will output null and then after that, nothing more.

ronny3050

@malicious_banjo the more I think about it, the more convinced I get that we should have our own application. The issue is I am not very knowledgeable in the workings of Pushbullet which will always limit my abilities to solve issues like this.

Do you think it is reasonable to have a widget installed on your Android phone that pushes notifications instead of relying on PushBullet?

malicious_banjo

@ronny3050 Seems perfectly reasonable to me. Would it abandon the usage of the PushBullet API/Access Token completely?

ronny3050

@malicious_banjo Yes, it will. It will be a lot of work, but I think it would work well due to the following advantages -

Phone call alert with caller ID
App for both Android and iOS
No relying on push limits/month
Issues can be resolved in an easier fashion

malicious_banjo

@ronny3050 Sounds great. I just finished my mirror a few days ago so I’m quite new to this community; have they’re been a fair amount of issues concerning this module? I’m guessing some kind of recent update to PushBullet is throwing everything out of whack?