@ortin Can you explain a bit better the benefits and how you see the server-client communication flow for this?
Just off the top of my hat (limited time today)
I think an additional feature to push messages to a browser doesn’t necessarily make sense as the browser would already need to have an established session with the server. In such case using a dynamic mechanism like AJAX would already allow for notifications (e.g. the state of a device changing in the browser connected to the Pimatic webserver would be a good example of that).
The alternative would be to have a client app listening for incoming messages. However, I think most mobile OS-es such as IOS and Android require the sender server to register with the OS providers API framework and provide an app through the provider’s store, which will then in turn deliver the push message to the (Pimatic) app on the mobile device. Challenge here would be each Pimatic instance (read home) would require their own API key with e.g. Apple, Samsung, …
Maybe a developer with more experience in mobile app development can share some additional thoughts…I could be completely off here
"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins