i searched but didn’t find this already. hopefully i didn’t suck up my search 
i’d like ha to be able to receive pushover.net events. currently the integration only does notify out. many systems use pushover to notify about things that are happening. i’d like to catch them and automate responses with homeassistant and/or display them on the dashboard.
Pushover??
Do you mean push messages?
And what protocols?
Often the Integrations are made to solve these and if it is standard protocols, then HA have those built in too.
pushover is a name of a service:
ha already support pushover in one direction (outbound):
it’d be very helpful to have it support receiving pushover notifications.
I do not see an api for a listener on the pushover site.
My guess is no such one exist, because that would undermine their business model.
sorry that’s not correct. here’s the api:
https://pushover.net/api/client
it’s not at all in conflict with their business model. any subscriber needs to have a license. (which is cheap. $5 lifetime for consumer subscribers… volume business senders are where they make their money).
seems like you’re not familiar with this service… maybe get to know it and you’d understand this request and value of it more.
I tried to get to know it by looking through their website.
I am not an user and probably never will be, because I prefer local things and see no point in using a cloud service to get notifications to HA when their most likely is a direct way to do it instead, which will remove possible failure points.
That said. Your feature request is valid enough, but I think the likelihood of an official integration is slim. A third party integration would be a viable option.
Why do you say that?
Because the interface to the service as a sender is a webhook, which means it could just as well be made directly to HA that also use webhooks, so all it does is add an extra layer and an independence on a cloud service.
On the other hand it is an easy integration to make, but this also talk for a third party integration.
Unlike some folks here that seem to offer their opinions without n=1 experience, I have used the Pushover service for many years with Home Assistant. And I have found it to be a useful and quality service. That said, to your goal. I read through their documentation for this new service and here are couple points that you might consider:
A couple of alternatives that come to mind:
Does not Home Assistant’s Nabu Casa interface have a way to call to your Home Assistant from outside?
A long while back, I see to remember that Home Assistant supported some of Google’s public facing push messaging services, you might explore there.
Another option would be using a public MQTT service.
Good hunting!
thanks @dproffer.
regard to #3. there is a very subtle but important thing here. i thought the history of where this term came about it was about the company/business sending and catching their own event at the user side, hiding it from the user. didn’t think it was an issue for a user to catch and decide what to do.
but you’re right that the language is vague and could be (mis?)interpreted to mean the user cannot also catch it and act on their own behalf.
for me, the issue is that the sender (which i don’t control) is sending pushover. and others are sending email.
i’ve seen several folks wish homeassistant could catch and react to email. pushover could bridge that.
i wish i could get the sender to convert to mqtt… or something else that can stay local. but sadly i can’t 
btw… i recognize that some folks may scoff at how terrible those other senders are that i don’t control… but one of the things i really value about homeassistant is that it abstracts away all the dirty and inconsistent muck… most of us have a heterogeneous set of devices in our homes… of varying quality/age/etc. and homeassistant puts a more consistent clean abstraction on top of them.
homeassistant already supports things like ifttt inbound, and webhooks inbound. i think pushover is pretty similar to these and would love to abstract away the interface and build automation on it in a consistent way.
Yes, I too use a scrape of some incoming emails for a automation or two. It works, but seems a bit ‘Dixie cups and strings’.
Sure seems like there should be a solution via Nabu Casa webhooks, not as low cost as the Pushover solution might be, however it would be ‘in the family’.
Good hunting!
This guy’s nice HA component might give you some ideas for the email scrape route:
I’d love to have this
then give it a vote…
I did not know that was a thing. done 
to be clear the use case:
I dont want to expose my HA to the internet, not even with nabu casa. So webhooks is not an option
you could use a public MQTT server. But HA can only subscribe to one MQTT broker at a time, so this is also NOT an option
My use case is to monitor a remote HA server that sends a heartbeat and also a watchtower container that sends notifications on certain events.
Something like subscribing to notifications of any kind through a third party like pushover would be a really good solution.
I think this would be a great feature, I could then direct my pushover alerts to HA and have them broadcasted out to my google speakers rather then my cell phone.
Where did you get the information about the WebHook? According to the documentation, the connection is established via a WebSocket! That’s something completely different.
https://pushover.net/api/client#websocket
The process would be as follows:
The first two steps are a one-time process performed when adding the integration.
There are likely already integrations in HA that use WebSockets.
The only problem I see is retrieving/processing the messages. When HA registers for the first time, there could be thousands of messages already on the server, which would then be fetched. This needs to be prevented or handled somehow.
Sorry, typo.
It is websockets I meant.