I’m just learning this whole home assistant thing, and wanted to try out the push notifications.
Searching everywhere it seems the html5 push notifications is what I need to use (https://www.home-assistant.io/components/html5/)
But, what I don’t understand is why do I have to configure anything with Google to have LOCAL push notifications?
I mean I have a browser window open, I can give the browser permission to show notifications, and the website I’m viewing just pushes it to the browser. There is no need for any 3rd party to route the notification through.
Is this cannot be done? Or am I missing something?
Ok, so let me reply to my own question. I don’t know what the original intent was to make the Google route mandatory, but I’ve modified the code and now it works without Google as a simple local push notification both on desktop and on Android in Firefox.
I also wondered, but implemented the whole Google thing (Stupid cow that I am). And then realize that the whole point of choosing Home Assistant was to own my data and not give data to others like Google!
Dont know exactly how but it seems possible to make this a custom component right?
It probably is, since this is the original component with one more line of code added, and fixing the indentation for that.
But what would be better is to have the developer of the html5 push modify the the original code. Although that would probably require a bit more work since I don’t know if this breaks Chrome or not.
If you know an official way to talk to component developers please let me know and I’ll talk to them about this patch.
I had assumed Google was used as browser needed some pinned cert.
If your saying this is not needed and you figured out the patch…sir…You Are My Hero!!!
So unfortunately it seems my method is still not local only. It uses mozilla’s push services.
But at least the added benefit is that you don’t have to configure any parameter and don’t have to use google.
But my main goal was to use it locally only. It seems that would require more work maybe on the frontend side too.