I have been using Vera Alerts for a couple years now and everything has worked very well. All the sudden about 2 weeks ago I stopped getting alerts. I went in and did the test and it comes through just fine. I tried to re register as well as got a new key for pushbulet. Anyone else having issues with this? Any help would be much appreciated.
mine is still working fine as of this morning. (VA and pushbullet)
Try to unregister and register again, that happened to me last week. If that doesn’t works (that didn’t for me) then, take note of your ID and clear the cache and all data of the app and then register again introducing your previous ID in the settings prior to registering.
Do you have a Samsung and entered to UltraPowerSaving Mode?
Many folks have had no problems … until they tried to add a new Notification, or modify one.
Then you run into the problem saving data that has been a problem in Vera for quite some time.
The latest Beta is the first time all of my test cases work …
See:
http://forum.micasaverde.com/index.php/topic,40474.0.html
I have upgraded to the firmware and uploaded the file and I still do not get any alerts. It was working perfect 2 weeks ago the only thing that changed was my phone. I checked my pushbullet profile online and the notifications just stopped. Any other ideas would be very much appreciated.
Did you you check the “Notification Configuration” after installing … followed by the Vera Reload?
Email me the output of the Report command.
I’ve also started experiencing the same issue with Pushbullet this week. The last message received was Tuesday. I’ve made no changes. I tested I can send messages ok by making a curl request as per their API using the same token I had setup in Vera, I also made the curl request directly from the Vera Plus via SSH. I’ve now upgraded to the Beta to see if this makes any difference but unfortunately not.
I set debug to 1 in the advanced settings and i’ve attached the log file output from a test message. You will see the result is showing as “closed”, if I compare this to a working alert using pushover the response contains 200 (I presume the http status) and the JSON response from the API call so something definitely not right with the API call to Pushbullet.
I went in and did the same (i think) here is the log that I got.
my last message was also on Tuesday.
so i think something has changed.
Same problem here… using pushbullet and messages stopped a few days ago…
Here’s the log:
08 12/10/16 14:39:17.664 JobHandler_LuaUPnP::HandleActionRequest device: 113 service: urn:richardgreen:serviceId:VeraAlert1 action: SendAlert <0x2e08b680>
08 12/10/16 14:39:17.664 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=113 <0x2e08b680>
08 12/10/16 14:39:17.664 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:richardgreen:serviceId:VeraAlert1 <0x2e08b680>
08 12/10/16 14:39:17.664 JobHandler_LuaUPnP::HandleActionRequest argument action=SendAlert <0x2e08b680>
08 12/10/16 14:39:17.665 JobHandler_LuaUPnP::HandleActionRequest argument Recipients=Hejsan!!!!!!!!!!!!!!!!!!!!!!!!! henrikekblad Pushbullet_Hek <0x2e08b680>
08 12/10/16 14:39:17.665 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.6004519660799583 <0x2e08b680>
50 12/10/16 14:39:17.669 luup_log:113: VeraAlert:113:SendAlert:Msg: <0x2acd5000>
50 12/10/16 14:39:17.671 luup_log:113: VeraAlert:113:ExpandRecipients:Checking:Hejsan!!!!!!!!!!!!!!!!!!!!!!!!! <0x2acd5000>
50 12/10/16 14:39:17.672 luup_log:113: VeraAlert:113:ExpandRecipients:Not a user or profile:Hejsan!!!!!!!!!!!!!!!!!!!!!!!!! <0x2acd5000>
50 12/10/16 14:39:17.673 luup_log:113: VeraAlert:113:ExpandRecipients:Checking:henrikekblad <0x2acd5000>
50 12/10/16 14:39:17.673 luup_log:113: VeraAlert:113:ExpandRecipients:Adding User Specified Profile:Pushbullet_Hek <0x2acd5000>
50 12/10/16 14:39:17.674 luup_log:113: VeraAlert:113:ExpandRecipients:Checking:Pushbullet_Hek <0x2acd5000>
50 12/10/16 14:39:17.674 luup_log:113: VeraAlert:113:ExpandRecipients:Adding Requested Profile <0x2acd5000>
50 12/10/16 14:39:17.675 luup_log:113: VeraAlert:113:ExpandRecipients:Duplicate <0x2acd5000>
50 12/10/16 14:39:17.675 luup_log:113: VeraAlert:113:SendAlert:Sending to:Pushbullet_Hek <0x2acd5000>
50 12/10/16 14:39:17.676 luup_log:113: VeraAlert:113:MessagePrefix:Initial: <0x2acd5000>
50 12/10/16 14:39:17.677 luup_log:113: VeraAlert:113:MessagePrefix:Result: <0x2acd5000>
50 12/10/16 14:39:17.677 luup_log:113: VeraAlert:113:PushbulletSend:Body:type=note&title=Vera%20Alert%20from%3A30104189&body= <0x2acd5000>
50 12/10/16 14:39:17.729 luup_log:113: VeraAlert:113:PushbulletSend:Result:closed Resp:nil <0x2acd5000>
06 12/10/16 14:39:17.730 Device_Variable::m_szValue_set device: 113 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 14:33:21 Sat Dec 10 now: 14:39:17 Sat Dec 10 #hooks: 0 upnp: 0 v:0x10d78d0/NONE duplicate:0 <0x2acd5000>
50 12/10/16 14:39:17.805 luup_log:113: VeraAlert:113:SendAlert:Memory:489094 <0x2acd5000>
04 12/10/16 14:39:17.807 <Job ID="258" Name="" Device="113" Created="2016-12-10 14:39:17" Started="2016-12-10 14:39:17" Completed="2016-12-10 14:39:17" Duration="0.140505000" Runtime="0.137382000" Status="Successful" LastNote=""/> <0x2acd5000>
Running UI5, VeraAlerts 6.43
I think they tightened the API. Previously the accepted arguments in the a URL encoded format… now they only accept JSON format … I will have to make some changes.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Will this mean I’d lose vera alert support? I would rather not update to UI7 (no one want hell break lose during x-mas 
)
Or would you consider backport it to a pre UI7 release?
I will do a u i5 port as well.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Thanks Richard!
just saw this, was pulling my hair out trying to figure out why it stopped.
any timeline on when a new version will be available?
Regards
Stuart Buchanan
pushbullet said that they have not changed their API, at least not intentionally. I told them to look at this thread. And he came back with the following.
I just ran this command: curl https://api.pushbullet.com/v2/pushes -u : -d type=“note” -d title=“A simple title” -d body=“A message” -X POST
and it worked, and that uses url encoded parameters, so I suspect it is some other issue, not the JSON request bodies.
-Chris
Co-Founder, Pushbullet
[quote=“fuzzysb”]pushbullet said that they have not changed their API, at least not intentionally. I told them to look at this thread. And he came back with the following.
I just ran this command: curl https://api.pushbullet.com/v2/pushes -u : -d type=“note” -d title=“A simple title” -d body=“A message” -X POST
and it worked, and that uses url encoded parameters, so I suspect it is some other issue, not the JSON request bodies.
-Chris
Co-Founder, Pushbullet[/quote]
It might be there SSL security. When doing a post to there website from LUA (We are limited to a very old version With Vera) the connection closes. Same arguments work fine in curl. This is new behavior.
Sent from my SAMSUNG-SM-G935A using Tapatalk
It looks like SSL could be related, their SSL cert has recently been renewed as its got a valid from date of 01 December 2016.
Do you think you will be able to look at this soon? It would be good to know if not so I can look at alternative solutions.
It would not be the Cert. It would be something like the set of allowed encryption connection protocols that is negotiated when a SSL link is established.
Vera uses old Linux and LUA sofware and may not have the most modern secure connection protocols.
Push Bullet may no longer accept the protocols that the the MCV Version of LUA supports. (A trade off when you try to harden the security of a website.)
curl on Vera can talk to Pushbullet, so I will likely have to make some additional code changes.