Jimbo.Automates

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

The notification node server 3.6.7 is released. There are still issues with this version which requires a new release of PG3/PG3x which is not out yet so existing users, please hold off updating. I will update this post when the new version is released to fix the issue. If you intend to only use the UD Mobile node, or convert you existing ones, then you can install and give it a try. The existing Pushover and UD Portal nodes do not function correctly with the IoX 5.6.2 and current PG3/PG3x. This finalizes the support for a new UD Mobile node which will be utilized in the UD Mobile app to make it easy to add notifications. We have also added support for allowing any length of System Customizations to be used, the previous limit was 80 characters. This completely eliminates the need to use REST interface thru IoX network resources. There is now also a "Free" version which has limited features and can be automatically installed by UD Mobile for new users. It does not support failed retries, and is limited to 8 messages a day. Thanks to @Michel Kohanim, @Chris Jahn, @bpwwer, @Javi and @bmercier for all the help getting this done and almost working. There is also an issue for current users of "Send Sys With Parameters" in a program. When you view the program you can only see the ID number of the System Customization you have referenced, but the edit window at the bottom will always show the System Customization ID number one. Then to actually utilize the longer text in a message you will need to edit the program line to set the proper System Customization, and save it. UDI have fixed the Admin console, so in the next release this will not be an issue. 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. There is also a bug in the Admin Console which results in the notification name not showing up in the Program line, it shows the notification number. Hopefully this will be fixed in the next release as well. See the README for more information, the news post Instant Notifications!, and Official Documentation

If you already have notification node server installed, you don't have to do anything. You can update to the latest, but please hold off, we just discovered an issue for existing users.

The UDMobile video shows that it installs the "Free" version of the Notification node server the advanced functionality is available with the Paid version. I'm not aware of a wiki page describing how to update PG3 node servers, but one should be created if it's not available.

No it's been an issue for a long time. Was hoping it would magically get fixed when the new version is released. Sent from my Pixel 6 Pro using Tapatalk

I still have the issue...

You did nothing wrong. I did. But this will not affect anything. I'll fix it in the next release. Sent from my Pixel 6 Pro using Tapatalk