Javi

Version 2022.07.01 Fixed defined Custom Parameters not populating on install.

The web interface is limited and does not have admin/polyglot features. Admin Console can be launched with Portal credentials and URL.

Should be fixed in version 2022.07.01

Invalid chars use "{}" not this "()". Copy the resource body I posted and it should work.

This is only substituted when sent. Update -> Save (single resource) -> Save (all resources) -> Click the name of the resource -> Test

Looks correct, you can test the network resource and see the result.

This is possible with both network resources or using a Node Server. Both options require Admin Console setup as this has not yet been added to mobile UI. EDIT: Added instructions to our wiki here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Variable_Substitution Network Resources: Network resource variable evaluation is on a seperate thread and is evaluate when run. So if this is triggered by a program and the variable changes before evaluation the new value will be shown. This is not the case when using the Node Server https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables title=My Test Title&body=My Test Body ${sys.time} Node Server: Node Server developers can use the subject line of the current Notification framework. The Notification Node Server recently added UD Mobile notifications with this parameter. See the following post for an example. The notification node server allows users to use the Notification Subject Line. This is evaluated during program run so does not have the same issues as network resources.

Added issue: https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/62

Thanks, replicated. Python may not be configured for Tk

Beta: 0.8.2 Added notification time created parameter. Resort notification list. Added delete all notifications. Removed deleted notifications while waiting for server response. Fixed view size for empty view subtext. Added delete device function. Fixed test notification sending to all devices.

On android the sound file name (xxx.wav) is used as the notification channel ID, the name of the channel is the sound file without the .wav suffix. On iOS this is the actual sound file which is played. Due to the differences in platforms this scheme appeared to work the best for both platforms.

Nice find! I may have disabled the notification channel settings while testing for Android Auto. So, I'll have to go back and test this.

Delete All is on the list, will add mark-all to list.

Will look into this, I think the grouping issue is related to the modifications for Android Auto. Time is added in the next release (parameter was just added this week). Disable what? Yes, To guarantee the fastest delivery of notifications Android requires Notification Channels, which include a sound, to be setup prior to notification receipt. Will add to my list.

To send a notification to a group of devices instead of all devices. or Although not included on the wiki you can send a notification to an individual device. The issue with this is when you change phones the device id changes, so you would have to change all the notification to match the new id. If you create a group for your device, when you get a new phone you will just have to add the device to the group instead of changing all notification to match the new id.

https://wiki.universal-devices.com/index.php?title=UD_Mobile#Group_Setup Basically you add a group in the groups section (bottom of the settings page), then click on one of the devices (devices section is above groups section), then enable membership in the group from the Device page.

Added delete all to the list, on iOS there is also a third option of swiping all the way to the left which takes it down to one step. @Steve L's issue is common, for this reason history exists. Notifications older than 3 months will be deleted automatically. There is also an acknowledgement parameter, if the notification in the list has a filled circle by the icon the notification has not been acknowledged.

There is a PG3 Node Server which requires Polisy, there is/was a PG2 version if you are already running PG2. Note that PG2 is depreciated so will not be getting additional updates/features. I do not believe adding the node server interferes with existing Module, but I would ask on the ELK forum topic. This only if using the 994i with Polisy and not IoP (ISY on Polisy). Alternatively you could use programs/variables to work around the limitation in UD Mobile. If mapping elk status to variable values the variables values can be mapped to text using Individual Status Mappings to show text values (i.e. armed/disarmed/ect.) and icons. Programs as Favorites Command Type commands could allow arm/disarm on button press similar to the Favorite Custom Toggle Example.

@Blackbird, At this time we plan to support modules included in Polisy, others as Node Servers.

Beta 0.7.9 Fixed Favorites launch type crash on M1 Mac. Fixed backup for in memory database Beta: 0.8.0" Fixed Favorites folder title save on favorite click, Added notification sounds. Beta: 0.8.1 Fixed multiple Notification Settings windows opening. Added Notification Badges. Changed notification list order. Fixed notification settings showing multiple windows. Bug Fixes.

Hi @MrBill, Thanks. The issue is at the OS level for notifications, .wav is the only file type supported for notifications on both platforms when the apps are not in the foreground. There are legal issues to consider if the file is altered/converted. I doubt anyone would report us but it is easier to have unaltered/licensed files. We will try to add the ability to insert custom sounds in the future, but it has a lower priority to some other features.

Thanks to All, I really liked @MrBill's suggestions of animal sounds, but could only find rooster and hawk sounds, on shutterstock, without background noise. Sounds (please note app version numbers) : https://wiki.universal-devices.com/index.php?title=UD_Mobile#Sounds Setup: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Sound_Setup

Great. I think the delay of device addition may be related to the original issue of expired portal credentials. We'll add a test for this in a future build.

It looks like it was sent, please check the notification tray. There is a bug in the current version of UD Mobile, notification are not shown in app until refresh (click another tab, then return). Also verify the device is working by clicking notification settings -> device name -> send test notification

Use Mode "Raw", update, save , then save all network resources before testing.