chris from Pushbullet sent me the following info. so it looks like unless the version of openwrt vera uses is updated then this will start happening with more and more providers in the future
That is more likely. There were two things that changed, it now uses a SHA256 root CA, which chrome will require soon, and it uses SSL SNI which our provider required, but which is supported by about every SSL thing made in the last few years. Is the developer using TLSv1 instead of SSLv3? SSLv3 is definitely broken: https://security.googleblog.com/2014/10/this-poodle-bites-exploiting-ssl-30.html
i’ve been looking at other methods for picture messages as i was sending a picture to Pushbullet via veraalerts and this picture would be in my Android notifications and withing the Pushbullet notification on my PC and would also show the picture on my Gear S2 which was awesome when someone rang my doorbell.
but now its stopped that only leaves VeraAlert on android for receiving messages. but it does not show the picture on the notification screen and in fact doesn’t appear at all and gives a notification that it cannot connect to vera, but the picture is in the log directory. any ideas and what other options do we have for picture messages?
I have released a Fix … Plugin Version 7.21 to fix the pushpullet problems.
The problem was that Pushbullet changed some software on their server to protect certain types of security vulnerabilities.
This was actually mandated by their Web Server Provider.
The changes they made are NOT compatible with HTTPS posting in LUA (Thats what is required to send the data to the Web Server).
The reason it is incompatible is because Vera users a VERY OLD version of OpenWRT and LUA … and they do not have recent security improvements.
[quote=“RichardTSchaefer, post:23, topic:194619”]I have released a Fix … Plugin Version 7.21 to fix the pushpullet problems.
The problem was that Pushbullet changed some software on their server to protect certain types of security vulnerabilities.
This was actually mandated by their Web Server Provider.
The changes they made are NOT compatible with HTTPS posting in LUA (Thats what is required to send the data to the Web Server).
The reason it is incompatible is because Vera users a VERY OLD version of OpenWRT and LUA … and they do not have recent security improvements.[/quote]
Thanks for the fix… what is the typical ETA before it shows up in the app store?
I’m still showing 7.15
I’ve been having issues with Alerts not coming through - in part, or none at all (as has been since 11:49pm last night)
I just enabled logging on my PLEGs (which run most of the logic/notifications) and also on VA. I also unregisterred/reregistered and validated the key in both the app & Vera was correct.
I will post logs in the next day or so after enough alerts are missed.
Richard,
After reboot it was working fine until 3:48pm today. Full Vera and PLEG logs attached. VA log inside LuaUPnP. Also EventWatcher Log for good measure…
When it does work, it will work for a day or so then stop. I cant figure out why it stops but it stops dead. This morning I un-register / re-register and sent a test message from VA and it worked. But still no alerts getting from PLEG Notifications → VA Android App
The events are getting logged in Vera and Event Watcher so Vera knows they are happening.
Richard, can you please check the logs and see if you can figure out why? This is really kicking my butt and I rely on VA in real-world (make sure the kids don’t leave the house, DIY alarm system, etc)