Hi there everyone!

I have not attempted to enable a Priority 2 Pushover alert to date and have used Priority 1 till now. I just installed a Zooz DC signal sensor tied into my linked smoke/CO detector system. Everything works well with Priority 1 but if I try to use Priority 2 I get an error for TCP Client. I assume this is a iPhone limitation but just wanted to see if others might have been through this or have a workaround. I did try to do some searches and did not come up with anything related.

Thanks as always for your thoughts!

Best,

Stan

Edited 5 hours ago5 hr by sdynak
Added details, corrections and screenshot added

Pushover is mentioned and the post is under ISY994. But also email is mentioned. And iPhone.

I don't understand all the links and what the chain looks like. Provide the technical details... If its pushover on a 994i than likely you're using network resources to create the notification, show that if so.

If not, what facility are you using for pushover notifications?

Hi Paul..

Apologies for any confusion.. I made assumptions based on my use of Pushover as I only use it with network resources for Pushover alerts on my iPhone. The screen capture is a result running a test for the network resource. I don't know how resource uses the Pushover backend such as the email error that is displayed.

I am doing this on my ISY and was not sure what other section would be more suitable but happy to move it there if there is a better place to create it.

It will work fine until I change the priority to 2.

Config in Network Resources:

POST /1/messages.json HTTP/1.1

Host: api.pushover.net:443

User-Agent: Mozilla/4.0

Connection: Close

Content-Type: application/x-www-form-urlencoded

Content-Length: 145

token=XXXX(replaced from actual)&user=XXXX(replaced from actual)&priority=1&sound=persistent&device=Stan_iphone&message=Home Fire Alert!!

Edited 5 hours ago5 hr by sdynak

When you change the priority, there are new parameters you have to add to the string..

• retry = how long in seconds to wait and retry if the message isn't received

• expire = how long in seconds until pushover gives up

&priority=2&retry=60&expire=3600

Both are "academic" in that I can't image what that would prevent. But pushover won't budge until you send them

Thanks Paul..

Although I don't get an error when including those changes now I lose the sound and the alert changes to time sensitive losing the red exclamation. Here is a screenshot of my home screen showing both the priority 1 in red and the priority 2 that looks plain.

I'm not as concerned as the exclamation but no alert tone bypass would be an issue.

I did try changing orders like putting the sound right after priority and after the retry/expire and didn't seem to change that.

Here is my last test line:

token=XXXX(replaced for forum)&user=XXXX(replaced for forum)&priority=2&retry=60&expire=3600&sound=persistent&device=Stan_iphone&message=Home Fire Alert!!

Edited 2 hours ago2 hr by sdynak

So what you show there has worked for me and in the past. The new variable in the equation, for me, is Apple. I think they have their own handling for priority alerts? Check the ios settings for the pushover app for critical alerts

Many thanks Paul.. I’ll check more into that and might reach out to Pushover if nothing obvious turns up.

You got me further than before :). Thank you