Dub Posted August 3, 2022 Posted August 3, 2022 (edited) @JimboAutomates Just got this setup and working last night thanks to a suggestion from @MrBill in another thread to someone else. I was just at the point of starting some notifications and didnt like the depending on email or text. Great job! Lots of Options and Highly Configurable. Also thank you for the ability to use Network Resources and custom content. Very well thought out. Great documentation too. I like how in the NS Config page it brings my specific variables like my IP address and Pushover Service Node Names in. Is it expected behavior to not see a subject line when using Custom Notification from Polisy? I get the api app name that I created in the pushover dashboard. I changed the name in pushover and it changed in the subject line on the next test send. Also, there may be a small typo on the PG3 NS config page that produces the same behavior as above, but for Network Resources. The parameter for the Subject line is capitalized in the example for the path, but changing it to lowercase seems to correct the issue and will send the custom subject line. This is when using Network Resources to send a request to the node server. From the config guide on PG3: /send?node=po_dub&Subject=My+Subject&monospace=1&device=1&priority=2 With lowercase s this sends the subject line: /send?node=po_dub&subject=My+Subject&monospace=1&device=1&priority=2 *Edit(Add) went back and looked at the config documents on Github, the "subject" parameter there is in lower case in the example code. My assumption is now this a typo on the NS config page and hopefully this helps someone. I accidentally typo'd a parameter experimenting with pure NS to Pushover api with similar results before installing this NS. This is the example of the Network Resource that does send a subject line: Edited August 4, 2022 by Dub aka WHaas Note added about typo on parameter
MrBill Posted August 4, 2022 Posted August 4, 2022 @Dub aka WHaas Are you using this with Pushover or one of the other options? With Pushover I don't use subject lines, but do have a few unique methods. I haven't moved over to PG3 yet tho, and I know the PG3 has more options that just Pushover.
Dub Posted August 4, 2022 Author Posted August 4, 2022 30 minutes ago, MrBill said: Are you using this with Pushover or one of the other options? Thank you @MrBillI do want to be clear as possible when tagging Jimbo and appreciate your help always. Yes I am using Pushover. Would really like to hear your methods as it was another post of yours about Jimbo's Notification NS that helped me see the value and robustness of it.
MrBill Posted August 4, 2022 Posted August 4, 2022 Here's how I do it. For starters I don't use subject at all with Pushover. Instead using the Pushover website I created multiple "Applications". One for each "type" of notifications I send. This will group the notifications like this in the app: The first two are miscellaneous type messages from ISY and Polisy that don't fit into one of the other categories below. and Home Assistant and Router Status don't even originate from Notification node server. To do this you create multiple Service nodes in the Node server, once service node for each message "type" Then under the Notification Controller Node, you will see each message category listed: now to route messages to each category use a simple /send command such as /send?node=po_wtag on the Network Resource. Again I don't use subject, so nothing to include there. As far as the other parameters such as Sound, priority etc.. I don't set those via the /send command... instead I use the node... remember that after setting a drop-down you MUST press the button to the LEFT of the drop-down. now that those are set, for the message category I also create a program to keep them set that way, which is essentially making them defaults. ServiceNode.wtag - [ID 01CB][Parent 016D] If '{hide}Node Servers / Notification Controller / Service Pushover wtag' Device is not all Or '{hide}Node Servers / Notification Controller / Service Pushover wtag' Priority is not Normal Or '{hide}Node Servers / Notification Controller / Service Pushover wtag' Format is not HTML Or '{hide}Node Servers / Notification Controller / Service Pushover wtag' Sound is not Quack Then Wait 3 seconds Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Device all Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Priority Normal Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Format HTML Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Sound Quack Else - No Actions - (To add one, press 'Action') So this program says if any of the defaults get changed then wait 3 seconds and change them back. ---- With some of the categories, I actually want to be able to change the sound and/or priority at the time of sending. For with Door Control so I expand the wait to change back to defaults to 30 seconds: ServiceNode.doordc - [ID 01C6][Parent 016D] If '{hide}Node Servers / Notification Controller / Service Pushover doordc' Device is not all Or '{hide}Node Servers / Notification Controller / Service Pushover doordc' Priority is not Normal Or '{hide}Node Servers / Notification Controller / Service Pushover doordc' Format is not HTML Or '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound is not Door Open Then Wait 30 seconds Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Device all Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Priority Normal Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Format HTML Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound Door Open Else - No Actions - (To add one, press 'Action') //Door Check Tally does do 15 second sound overrides at the end of the cycle. then in the program "Door Check Tally" which is part of the "goodnight" routine Then Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound Magic Wait 2 seconds Resource 'NotificationNS.doordc._TallyZero' Wait 10 seconds Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound Door Open Enable Program 'dc00._trigger.0' Else Run Program 'dc16._tally1' (If) the sound actually changes based on it being a "good" result that we can ignore, or a "bad"result that means we need to physically intervene. So the above program segment changes the sound, sends the notification then changes the sound back. If we failed to change the sound back, the ServiceNode.doordc program would do it at the end of 30 seconds. 2
Jimbo.Automates Posted August 4, 2022 Posted August 4, 2022 @Dub aka WHaas Sorry for my delayed response. Thanks for the Praise, very much appreciated. >> Is it expected behavior to not see a subject line when using Custom Notification from Polisy? I need to confirm this, it's not under my control, it's how the ISY processes it. If there is anything in the body then only the body is sent, otherwise it uses subject. I should add more info about that in the doc, but it's such a new feature in the ISY that it wasn't completely understood. >> Also, there may be a small typo on the PG3 NS config page that produces the same behavior as above, but for Network Resources. The parameter for the Subject line is capitalized in the example for the path, but changing it to lowercase seems to correct the issue and will send the custom subject line. This is when using Network Resources to send a request to the node server. Yes, I have noticed that before and keep forgetting to fix it... That info is generated on the fly by the code. @MrBill Thanks for providing your expertise. With the new options to send with parameters you don't have to worry as much about changing the defaults and changing them back, you can just call them for the one message: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification#send-sys-short-with-params 2 1
MrBill Posted August 4, 2022 Posted August 4, 2022 43 minutes ago, JimboAutomates said: With the new options to send with parameters you don't have to worry as much about changing the defaults and changing them back, you can just call them for the one message: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification#send-sys-short-with-params Nice to know it's been expanded for PG3. I haven't gone there yet....
Dub Posted August 4, 2022 Author Posted August 4, 2022 3 hours ago, MrBill said: Instead using the Pushover website I created multiple "Applications". One for each "type" of notifications I send. @MrBill Thank you. I like that idea. I trying to not let my exploration of the capabilities hinder future manageability, so I appreciate you tell me that its working well for you. So many power features. Now I have to find some good PNG files 😀. Thank you for the other ideas as well, I am still learning the best way to send them. I have used the NR based on another thread I read where you recommending sending them to the NS instead of the PO api since Jimbo NS will retry. 1 hour ago, JimboAutomates said: Sorry for my delayed response. No problem at all I'm sure I couldn't afford real time support 😂 Thank you following up and let me know if you find a way to have a subject with the Custom Notification please let me know. Otherwise there are enough options there for great functionality and give me what I need. I do appreciate your time and effort in responding!! 1
MrBill Posted August 4, 2022 Posted August 4, 2022 11 minutes ago, Dub aka WHaas said: Now I have to find some good PNG files 😀. i think some of mine are from https://www.flaticon.com the rest are favicons from Ubiquiti, wireless tags etc. Other than Mickey and Goofy but that's another story 🤣 14 minutes ago, Dub aka WHaas said: I have used the NR based on another thread I read where you recommending sending them to the NS instead of the PO api since Jimbo NS will retry. this is true, however i have a very small handfall that the ISY sends with out the notification node server. On is an ISY boot message that's sent both ways ISY -> Pushover direct and thru the Node server -> Pushover... if I don't get both then something is wrong and I need to investigate. Another is I watch the heartbeat of the notification Node server, and if it fails send a message directly from the ISY because the node server is down. hb.NotificationController - [ID 0028][Parent 016D] If 'Node Servers / Notification Controller' is switched On Or 'Node Servers / Notification Controller' is switched Off Then Wait 11 minutes Resource 'ISYnotification.NotificationNS.Missed Heartbeat' Else - No Actions - (To add one, press 'Action') 1
Recommended Posts