GatorGuy
Member
I already implemented push notifications via IFTT. The problem is that the Tesla web browser implements a very old draft version of WebSockets, which I have seen, does not support a reliable enough connection, along with forcing me to deploy another server that supports the draft version of WebSockets just to make this work. I have been holding off on this feature until we get a newer browser.
So what is the preference of pushbullet? Is this what people want to use? AFAIK pushbullet requires login auth, and since the Tesla Browser does not support persisted cookies, and ABRP does not store the auth token server side, how do you stay signed in? Do you have to log in every time?
Doesn't have to be Pushbullet but it is capable of mirroring all phone notifications automatically.
I have no idea how it works. This thread here is where he mentions a little how he did it. Android Notifications in Car
He says:
The Pushbullet API is not too complicated, but the Tesla browser limitations are. I had to write an own proxy to keep encrypted connections between the browser and the Pushbullet servers, and you can use it too if you want. Send me a PM for details.