Pushbullet no longer works

Plugins & Plugin Development VeraAlerts
#1

I noticed that I was no longer getting alerts through pushbullet and am not able to get it working again. Report and log dump are below. I have tested sending alerts directly from pushbullet to phone and that works. Recreated API key in case something got screwy. Still nothing. Twilio works fine. Is there a way I can spoof an API call to check if the issue is with Vera or Pushbullet?

VeraAlerts[148]
2017-01-02 18:54:40
Registration
Installed: Wed Apr 20 2016. You have 1 license, which allows for 2 active profiles.
User to Profile Mapping
User Profiles
DefaultRecipients Pushbullet
redbondc Pushbullet
veralerts_twilio Twilio
Profile Definitions
Pushbullet - Pushbullet
Parameter Value
AccessToken o.ZJFnoDUB1NJLdOpLVav3wVxxxxxxx
MessagePrefix undefined
Twilio - Twilio
Parameter Value
TwilioAccountSID AC2d514e49a294a8ac5d9exxxxxx
TwilioAuthTOKEN 181eefd8b6c785a991835441xxxxx
Caller +44121285xxxx
Called +4479719xxxxx
Operation Voice
TwilioCustomURL undefined
Device Notifications and Message Overrides
User Device Notification Name Description Message Override House Modes
redbondc Envisalink Envisalink Ping Failure Envisalink is not Tripped Envisalink Ping Failure! Automated Security and Home State will be Disabled! All
redbondc Envisalink Envisalink Ping Restore Envisalink is Tripped Envisalink Ping Restore. Automated Security and Home State will be Enabled. All
redbondc System Monitor Luup Restart Luup has restarted All
redbondc System Monitor Vera Restart Vera has restarted Vera Restart All

House Mode Legend: (H)ome (A)way (N)ight (V)acation
Scene Notifications and Message Overrides
User Scene Name Description Message Override House Modes
HotWater1hr Running scene: HotWater1hr All

House Mode Legend: (H)ome (A)way (N)ight (V)acation

08 01/02/17 18:45:26.465 JobHandler_LuaUPnP::HandleActionRequest device: 148 service: urn:richardgreen:serviceId:VeraAlert1 action: ^[[36;1mSendAlert^[[0m <0x70ddb520>
08 01/02/17 18:45:26.466 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=148 <0x70ddb520>
08 01/02/17 18:45:26.466 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:richardgreen:serviceId:VeraAlert1 <0x70ddb520>
08 01/02/17 18:45:26.466 JobHandler_LuaUPnP::HandleActionRequest argument action=SendAlert <0x70ddb520>
08 01/02/17 18:45:26.466 JobHandler_LuaUPnP::HandleActionRequest argument Message=test <0x70ddb520>
08 01/02/17 18:45:26.466 JobHandler_LuaUPnP::HandleActionRequest argument Recipients=redbondc Pushbullet <0x70ddb520>
08 01/02/17 18:45:26.467 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.5927065553077048 <0x70ddb520>
50 01/02/17 18:45:26.468 luup_log:148: VeraAlert:148:SendAlert:Msg:test <0x77a9e320>
50 01/02/17 18:45:26.469 luup_log:148: VeraAlert:148:ExpandRecipients:Checking:redbondc <0x77a9e320>
50 01/02/17 18:45:26.470 luup_log:148: VeraAlert:148:ExpandRecipients:Adding User Specified Profile:Pushbullet <0x77a9e320>
50 01/02/17 18:45:26.470 luup_log:148: VeraAlert:148:ExpandRecipients:Checking:Pushbullet <0x77a9e320>
50 01/02/17 18:45:26.470 luup_log:148: VeraAlert:148:ExpandRecipients:Adding Requested Profile <0x77a9e320>
50 01/02/17 18:45:26.471 luup_log:148: VeraAlert:148:ExpandRecipients:Duplicate <0x77a9e320>
50 01/02/17 18:45:26.471 luup_log:148: VeraAlert:148:SendAlert:Sending to:Pushbullet <0x77a9e320>
50 01/02/17 18:45:26.471 luup_log:148: VeraAlert:148:MessagePrefix:Initial: <0x77a9e320>
50 01/02/17 18:45:26.471 luup_log:148: VeraAlert:148:MessagePrefix:Result: <0x77a9e320>
50 01/02/17 18:45:26.472 luup_log:148: VeraAlert:148:PushbulletSend:Body:type=note&title=Vera%20Alert%20from%3A50101739&body=test <0x77a9e320>
50 01/02/17 18:45:26.512 luup_log:148: VeraAlert:148:PushbulletSend:Result:closed Resp:nil <0x77a9e320>
06 01/02/17 18:45:26.513 Device_Variable::m_szValue_set device: 148 service: urn:richardgreen:serviceId:VeraAlert1 variable: ^[[35;1mLastMsgSent^[[0m was: 18:40:54 Mon Jan 02 now: 18:45:26 Mon Jan
50 01/02/17 18:45:26.520 luup_log:148: VeraAlert:148:SendAlert:Memory:451389 <0x77a9e320>

#2

It’s a known issue which was discovered since PB updated some SSL settings on their end. A new release of the plugin to fix this has been submitted to Vera but is not available yet. See thread here http://forum.micasaverde.com/index.php/topic,40665.msg302452.html#msg302452

#3

Ah I missed that when I searched. Thanks, good to know I am not going mad!

#4

I’m still not getting anything on 7.21

08 01/06/17 1:42:42.135 JobHandler_LuaUPnP::HandleActionRequest device: 18022 service: urn:richardgreen:serviceId:VeraAlert1 action: SendAlert <0x2e4c3680> 50 01/06/17 1:42:42.143 luup_log:18022: VeraAlert:18022:SendAlert:Msg:test <0x2ac7a310> 50 01/06/17 1:42:42.144 luup_log:18022: VeraAlert:18022:ExpandRecipients:Checking:Pushbullet <0x2ac7a310> 50 01/06/17 1:42:42.145 luup_log:18022: VeraAlert:18022:ExpandRecipients:Adding Requested Profile <0x2ac7a310> 50 01/06/17 1:42:42.146 luup_log:18022: VeraAlert:18022:SendAlert:Sending to:Pushbullet <0x2ac7a310> 50 01/06/17 1:42:42.146 luup_log:18022: VeraAlert:18022:MessagePrefix:Initial: {title={Msg}} <0x2ac7a310> 50 01/06/17 1:42:42.148 luup_log:18022: VeraAlert:18022:MessagePrefix:Result: <0x2ac7a310> 50 01/06/17 1:42:42.149 luup_log:18022: VeraAlert:18022:VeraCurl:Cmd:/usr/bin/curl --request POST --header 'Content-Type: application/json' --header 'Content-Length: 44' --header 'Access-Token: ' --data-binary '@/tmp/log/cmh/veracurl.txt' https://api.pushbullet.com/v2/pushes <0x2ac7a310> 50 01/06/17 1:42:42.150 luup_log:18022: VeraAlert:18022:VeraCurl:Data:{"type":"note","title":"test","body":"test"} <0x2ac7a310>

#5

Still nothing.

08 01/14/17 14:15:57.320 JobHandler_LuaUPnP::HandleActionRequest device: 18022 service: urn:richardgreen:serviceId:VeraAlert1 action: SendAlert <0x2e98d680> 50 01/14/17 14:15:57.329 luup_log:18022: VeraAlert:18022:SendAlert:Msg:test <0x2ad43310> 50 01/14/17 14:15:57.330 luup_log:18022: VeraAlert:18022:ExpandRecipients:Checking:Pushbullet <0x2ad43310> 50 01/14/17 14:15:57.330 luup_log:18022: VeraAlert:18022:ExpandRecipients:Adding Requested Profile <0x2ad43310> 50 01/14/17 14:15:57.331 luup_log:18022: VeraAlert:18022:SendAlert:Sending to:Pushbullet <0x2ad43310> 50 01/14/17 14:15:57.332 luup_log:18022: VeraAlert:18022:MessagePrefix:Initial: {title={Msg}} <0x2ad43310> 50 01/14/17 14:15:57.333 luup_log:18022: VeraAlert:18022:MessagePrefix:Result: <0x2ad43310> 50 01/14/17 14:15:57.335 luup_log:18022: VeraAlert:18022:VeraCurl:Cmd:/usr/bin/curl --request POST --header 'Content-Type: application/json' --header 'Content-Length: 44' --header 'Access-Token: removed' --data-binary '@/tmp/log/cmh/veracurl.txt' https://api.pushbullet.com/v2/pushes <0x2ad43310> 50 01/14/17 14:15:57.336 luup_log:18022: VeraAlert:18022:VeraCurl:Data:{"type":"note","title":"test","body":"test"} <0x2ad43310> 50 01/14/17 14:15:57.451 luup_log:18022: VeraAlert:18022:PushbulletSend:Resp: <0x2ad43310> 06 01/14/17 14:15:57.452 Device_Variable::m_szValue_set device: 18022 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 14:15:26 Sat Jan 14 now: 14:15:57 Sat Jan 14 #hooks: 0 upnp: 0 skip: 0 v:0xb71010/NONE duplicate:0 <0x2ad43310> 50 01/14/17 14:15:57.462 luup_log:18022: VeraAlert:18022:SendAlert:Memory:372786 <0x2ad43310>

#6

At this point, I’ve uninstalled VeraAlerts.

Seems curl isn’t working on my Vera without -k, so I’ll send notifications from my scenes manually using the option.

#7

Yeah, Pushbullet notifications are still not working. Did you find an alternative? I relied on it to send an image to my phone from my front door camera when someone rings the doorbell. It was the fastest and most reliable method.

#8

Pushbullet was fixed in the last Vera Alerts release … I get then … a couple an hour.

#9

Like I stated in the other thread (http://forum.micasaverde.com/index.php/topic,40665.msg315611.html#msg315611), I am on the latest 7.21 and PB is not working. I have created a new token and updated. Uninstalled and reinstalled the plugin. I get all my other PB alerts from other systems. It seems me a few others still have this issue.

#10

Like I stated in the other thread (http://forum.micasaverde.com/index.php/topic,40665.msg315611.html#msg315611), I am on the latest 7.21 and PB is not working. I have created a new token and updated. Uninstalled and reinstalled the plugin. I get all my other PB alerts from other systems. It seems me a few others still have this issue.[/quote]

not disputing your results… but mine are working… so i’m not sure what the issue is, but mine do work. i noticed though that after a phone restart i have to launch the PB app… if i don’t launch it once after a reboot i get no alerts… once i launch it one time. i get them until i reboot again.

#11

Like I stated in the other thread (http://forum.micasaverde.com/index.php/topic,40665.msg315611.html#msg315611), I am on the latest 7.21 and PB is not working. I have created a new token and updated. Uninstalled and reinstalled the plugin. I get all my other PB alerts from other systems. It seems me a few others still have this issue.[/quote]

not disputing your results… but mine are working… so i’m not sure what the issue is, but mine do work. i noticed though that after a phone restart i have to launch the PB app… if i don’t launch it once after a reboot i get no alerts… once i launch it one time. i get them until i reboot again.[/quote]

The issue is not on my phone end. I use PB on a few devices and my computer to receive alerts from a few sources to monitor servers and service. PB is working fine. VeraAlerts pushes are the only ones not going through.

#12

The latest bugs from MCV over the last 3 updates concerning LUA code in scenes has cause people that have tried to add/modify notifications during those releases.
(A Notification is a hidden scene, and Vera Alerts add LUA code to it … that’s why its is linked to LUA code in scenes).

I can only suggest you do the following:

  1. Remove Vera Alerts
  2. Remove ALL notifications on devices and scenes.
  3. Remove ALL scenes that have (or have had) LUA code in them.
  4. Restart LUA and rebuild.

NOTE: Make sure you delete everything above … you need to get rid of the cancer (caused my MCV bugs)

#13

[quote=“RichardTSchaefer, post:12, topic:194982”]The latest bugs from MCV over the last 3 updates concerning LUA code in scenes has cause people that have tried to add/modify notifications during those releases.
(A Notification is a hidden scene, and Vera Alerts add LUA code to it … that’s why its is linked to LUA code in scenes).

I can only suggest you do the following:

  1. Remove Vera Alerts
  2. Remove ALL notifications on devices and scenes.
  3. Remove ALL scenes that have (or have had) LUA code in them.
  4. Restart LUA and rebuild.

NOTE: Make sure you delete everything above … you need to get rid of the cancer (caused my MCV bugs)[/quote]

No joy. Did everything you recommended. Then reinstalled VeraAlerts and created just a PB profile with a new access token. Same results in logfile.

#14

And you tested this from the SendAlert page ?

#15

Yep.

#16

There’s not much I can do … PushBullet tightened up the security on their servers … https via LUA on Vera does not meet there security standards (needs newer LUA release, Vera is always lagging)
It seems that curl on Vera does not work for some people … which means for some Veras … Also because curl comes from the OpenWRT software running on Vera which is also very old.
You can try taking this up with PushBullet … I do not know why they are so concerned (that they have to have the latest and greatest) about security for notifications.

The next version of Vera ALerts will have a URL profile … so you can forward this to a server of your own that sends to Pushbullet.