Jimbo.Automates

You aren't able to select Armed Status in UDM to show this? Sent from my Pixel 6 Pro using Tapatalk

Yes open your area node and set armed status. You can create a favorite to armed status to make it easier. Sent from my Pixel 6 Pro using Tapatalk

Yep,. sailing away. Back home Tuesday. Sent from my Pixel 6 Pro using Tapatalk

Yes I realize it's showing you the link to 127.0.0.1:8080. You need to change that to your IoX IP address. For some reason I can't download your PDF on my phone while on a catameran in the Caribbean, I'll have to look when at a computer at home. Sent from my Pixel 6 Pro using Tapatalk

Change 127.0.0.1 to the Polisy/eisy address . PG3 used to give us the real IP but not anymore I guess. Sent from my Pixel 6 Pro using Tapatalk

I've never seen this happen with the ELK NS. If you have the issue please download log package and PM it to me. I'll try to test when I am home from vacation. Sent from my Pixel 6 Pro using Tapatalk

Sorry, I can't do anything about the order of the list. That has also been reported to UDI.

Yes, as mentioned in doc https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#system-customizations "This feature allows sending messages defined in the Admin Console Configuration->Emails/Notifications->Customizations" The issue with it showing the ID in the Admin Console has been reported to @chris UDI and will hopefully be fixed in a future release of the Admin Console. BTW, you don't need a unique customization for each Leak Sensor, just create one and reference like the example in that section of the doc mentioned above.

Great, glad it's working. Sounds like I need to update my documentation? Sent from my Pixel 6 Pro using Tapatalk

Did you restart the nodeserver after adding the groups? Then once it fully completes the restart the open the admin console (if you already have it open, then close and reopen) Sent from my Pixel 6 Pro using Tapatalk

You can just copy/paste the subject and body of your network resource into a Customization, then edit your program and change from running the NR to sending a notification using that Custom Content. Would be nice if I created a how-to guide for that...

You are testing Control, not Status in your program? Status always changes, but control is handl with send on/off for. Sent from my Pixel 6 Pro using Tapatalk

Yes, there is an option on each zone "Send On For” Sent from my Pixel 6 Pro using Tapatalk

Your program looks correct, control action should come first. You can't add the elk log to a notification but you can add any of the driver values. Sent from my Pixel Tablet using Tapatalk

There should not be much delay. I assume you use a program? Do you trigger off the control event? I do something similar with some doors which I put the zone in a scene instead of using a program. But when I tested it a long time ago there really wasn't much difference between a program or a scene. Sent from my Pixel 6 Pro using Tapatalk

Thanks @MrBill, yes this is available @Morris Hansen

They're all working now from the Home app. I had an old Polisy which was offline still in the account so I deleted it and put my main eisy as the default then relinked again. Wasn't working at first but now seems to be okay. Sent from my Pixel 6 Pro using Tapatalk

I relinked again and devices still show as offline in the home app. Voice commands are working now but have been very inconsistent. Ticket submitted #21944. Sent from my Pixel Tablet using Tapatalk

Great! I'll try to look into allowing user name as well since that would be nice. Sent from my Pixel 6 Pro using Tapatalk

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.