Pushover issue I can't figure out

I have pushover installed per the instructions as virtual device, but for some reason I get no notifications after setting up HSM to text me using pushover every time there is status change. I checked and rechecked the settings, but no matter what I don't get any notifications. HOWEVER, if I add a notifier to use pushover every time motion is detected with a sensor, or some other device, I get pushover texts normally. I must be missing something in my HSM setup that is preventing pushover from sending me texts but I can't see what that could be. Anybody having a similar issue who could point me in the right direction? Thanks!

Maybe a screenshot of your HSM configuration would help us help you?

1 Like

sorry! here they are:



no matter what I use to change the HSM status (keypads, deashboard) I do not get any pushover alerts, but I do get them using notifiers (which I set up to alert me when motion is detected or contacts are open). Thank you for your help!

Looking at how HSM is configured, it appears it will only send notifications to your Pushover device if there was an "Arming Failure/Bypass-Warning Alert" . Have you tested that specific scenario versus a normal HSM status change?

yes, this is what is happening! I cannot, however, figure out where exactly I need to go to set up a text sent via pushover to alert me when HMS status is changed (and not just when an intrusion or a bypass contact is detected while arming)...I would like to be sent a text so I can disarm/arm the system via the dashboard after I leave the property. Thanks for spotting my mistake.

I have never found a way to do this WITHIN HSM. I use rules to send notifications on arming changes.

1 Like

THANK YOU! I think this is where I was going wrong. Since I saw there was a way to send myself a text alert using pushover from within HSM, I kept looking to see if I could also add notifications on HSM status changes within the app itself, but this is not the case. I have to set up a rule for this. I believe I had tried to do this using Rule Machine but did not see an option for HSM status as a condition but I guess I must've missed this option? I think this also threw me off (not finding an option for HSM status under Rule Machine, which made me think it should be found within HSM). I'll try again tomorrow. That you so much for your help!

You’re welcome! It confused me, as well!

Hello all,

I have used Pushover for HSM for a long time, but recently no notifications. I keep getting the following log (I'm using a water sensor device in this log to see if I get a notification when the sensor is wet):

dev:7282022-11-18 08:40:52.007 AMerrorjava.net.UnknownHostException: api.pushover.net: Temporary failure in name resolution on line 255 (method deviceNotification)

dev:7282022-11-18 08:40:51.946 AMdebugSending Message: [Secondary Sump Pump Failure wet - 08:40 AM - 11/18/2022] Priority: [null] to [All Devices]

app:432022-11-18 08:40:51.819 AMwarnAlert Water Secondary Pump Sensor wet

dev:3892022-11-18 08:40:51.750 AMinfoSecondary Pump Sensor is wet

I would appreciate some ideas as to what I'm doing wrong.

I have uninstalled Pushover from my android phone.

I've deleted and reinstalled the "firmware" Pushover driver.

I've registered and re-registered my cell on Pushover numerous times.

I've registered my wife's cell as well.

I don't get a "notification" when I send a "text" via the Device dialogue.

Thanks for any suggestions.

The issue appears to be related to the Pushover driver not being able to resolve the name of the cloud pushover server. Have you recently made any networking changes to either your Hubitat hub or your home network? If you have a complex LAN setup, with multiple VLANs and Firewall Rules, I could foresee things like this getting blocked.

Please use DHCP on your Hubitat hub and reserve an IP address for it in your router's DHCP server settings. This will ensure the hub's TCP/IP network settings are configured correctly.

One quick test you can try, assuming you're using a C5/C7 hub, is to go into SETTINGS, NETWORK SETUP, then click NETWORK TEST

type in the following to the PING command and run it. It should look like the following.

Thanks for the quick reply. I just wanted to add that I did recently change my hub's ip from dynamic to static using the Hubitat settings.

Also, Pushover (via Windows) does send my cell a notification message, so I know the link from Pushover to my android cell does work.

When I "ping" through Network Test this is what is returned:

ping: api.pushover.net: Temporary failure in name resolution

Yep! This is the issue. If you want to continue using a truly static IP address on the hub, using the hub's option to do so, please make sure you enter a DNS server address. While it may appear that there is a DNS server address, chances are good that there is not one really there... Try typing in 1.1.1.1 and saving the settings. But I really believe folks should just stick to DHCP and let the router assign the same IP address consistently by reserving one.

Maybe I'm showing my novice skills here, but when I "ping" using the Hubitat Network Test this is what I get:

PING 1.1.1.1 (1.1.1.1) 1250(1278) bytes of data.
1258 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=26.3 ms
1258 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=25.1 ms
1258 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=24.7 ms

--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 24.654/25.331/26.285/0.694 ms

Use 1.1.1.1 as the DNS Server address in the Network Setting "Static IP" settings area.

Then try pinging the api.pushover.net via the Hub's utility again.

Did as you suggested:

PING api.pushover.net (45.63.37.132) 1250(1278) bytes of data.
1258 bytes from api.pushover.net (45.63.37.132): icmp_seq=1 ttl=237 time=80.5 ms
1258 bytes from api.pushover.net (45.63.37.132): icmp_seq=2 ttl=237 time=80.1 ms
1258 bytes from api.pushover.net (45.63.37.132): icmp_seq=3 ttl=237 time=80.7 ms

--- api.pushover.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 80.109/80.434/80.718/0.250 ms

Then I "dipped" my water sensor in a glass of water and !!!! Pushover notified me!!!!

Thanks both of you for your time and suggestions! BTW the "static IP" dns was set to 8.8.8.8. When I changed it to 1.1.1.1 it all worked!

We're going out of town this weekend for a while. Where we live our sump pumps fire every 45 to 60 seconds. Not having sensors working makes me lose sleep!

I'm truly relieved.

Regards, and Happy Thanksgiving!

1 Like