Jimbo.Automates

Thanks, I'll try to take a look when I return home from traveling. Sent from my Pixel 6 Pro using Tapatalk

Issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/18 I'll look into it when I have time. Sent from my Pixel 6 Pro using Tapatalk

As mentioned in the first paragraph of the OP, there are issues with Pushover notifications which require a new release of PG3/PG3x to resolve, which is not out yet. Specifically Sounds, Devices, Hopefully soon. Are you on PG3 or PG3x? Michel has mentioned the fix may only be released with PG3x so you would need to do the conversion. But, if you don't get a notification for Pushover, that likely means the Priority is set to "Low" or "Lowest" that's a feature of Pushover, where notifications are not given for those. At least that's how it works on Android. The issue is many of the drivers are not being passed thru PG3/PG3x, so you lose the Priority, Format, ... settings which means it takes the defaults from the "Service Pushover ..." node. Click on that node and make sure the Priority is "Normal". Change it in the dropdown, then save it by hitting the "Priority" button.

It's mentioned in the release announcement. Due to the issue mentioned in the first paragraph, you will get this message in the PG3 UI. This version of PG3 3.1.31 will not work properly with Pushover or UDPortal nodes, Please upgrade modules and restart PG3. tisyVersion=5.6.2 isPG3x=True pg3Version=3.1.31 This is because the new version of PG3/PG3x is not out yet, hopefully soon. Sent from my Pixel 6 Pro using Tapatalk

Yes, that's usually the ST driver ${sys.node.#.ST} https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables

For that node server, the humidity is likely in the CLIHUM driver. So you can add ${sys.node.node_address.CLIHUM} where node_address is n002_ followed by the "Address" shown in the the PG3 UI screenshot you posted.

This is fixed in 3.6.9 Sent from my Pixel 6 Pro using Tapatalk

If you want to see the value, you would have to add the specific node address Transmitter Low Battery: ${sys.node.n009_zone_20.GV12} Where zone_20 is the zone you want. But then you have to create a separate customization for each node.

Yes, if you run the program it will always show that way. It has to be triggered by IoX when the status of the node changes.

I am at this moment in the process of converting almost all of my notifications from Pushover & NR's using Notification NS into UD Mobile with System Customizations. I have feature requests for @Javi and @bmercier that would make my conversion perfect Allow High priority messages which ring thru on DND and are highlighted in the notification Allow sending with fixed width fonts, makes it easier to line up text Allow sending formatted messages in HTML or Markdown or ? (This would eliminate the need for #2) Allow Android Auto/Car Play to show messages. (This is the only reason I use telegram)

That's perfect! Didn't realize the Polisy would need a reboot. Good to know. When the actual node triggers the program the # will be replaced with the actual node. But now I realize we should probably change the subject to include the node name that triggered it. ${sys.program.#.name} ${sys.node.#.name}

Sorry, that is odd. Please set log to debug mode in PG3 Notification Node Server config page, do those steps over again, then download log package and PM or email it to me.

That's odd, it shouldn't happen with the UD Mobile, when did you first install the notification node server? The only way I can think of that would cause this would be if the node server was installed when it had the UD Mobile feature added but before your IoX version was 5.6.2. To fix it. In the admin console, delete the UD Mobile node. In the PG3 UI restart the notification node server, wait for the UD Mobile node to show back up, then in the admin console "Update" that line in the program, and save it.

Is this to the UDMobile node? Is notification node server the latest version 3.6.7? Sent from my Pixel 6 Pro using Tapatalk

You are welcome, yes, you would have to add them all. There is no way I'm aware of to pull the message sent tot he keypad or log. Someday I could possibly automate creating programs like this but I don't think ELK gives us the info on which zones are wireless... To save some typing, here is the subject: ${sys.program.#.name} and the body: Box Tamper: ${sys.node.#.GV11} Transmitter Low Battery: ${sys.node.#.GV12} Security Alert: ${sys.node.#.GV13} Lost Transmitter: ${sys.node.#.GV14} Fire: ${sys.node.#.GV15}

Here's how to do it with the notification node server.

Download Log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

The notification node server 3.6.7 is released which fixes an issue with UD Mobile crashing when opening the Notifications. Also, see OP for latest information.

Yes, there are issues that are fixed in PG3 but it's not yet released, hopefully it will be today. Sent from my Pixel 6 Pro using Tapatalk

Thanks @bpwwer The node server has custom config information generated on the fly, but I thought it set the initial data in startup to the .md file, but I'll have to check. Sent from my Pixel 6 Pro using Tapatalk

Oh, that's not good. @bpwwer are you aware of this issue?

Sorry, I'm not a technical writer... Writing clear documentation is difficult. But I fixed it last night in 3.6.6 to show more docs, You should see the below, but if not the doc is at: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/POLYGLOT_CONFIG.md

That's great to hear! If you have any questions/issues with using the notification node server ask here https://forum.universal-devices.com/forum/316-notification/ But if it's directly related to UD Mobile then keep it in this sub-forum.

The notification node server 3.6.6 is released, see OP.

The blog that was sent out today details the advantages of using the notification node server. Sent from my Pixel 6 Pro using Tapatalk