Javi

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

The program you have is the solution. This is a specific use case, which has a working solution. So, I'm not sure it is a good fit for inclusion in firmware.

Hi @Steve L, This is usually caused on devices which are using the Local Connection settings and have not logged into ISY Portal in quite a while. Please go to Settings-Tab > ISY Portal Accounts > Your Account, the app should prompt for login. We will try to push to the login page in the future when this error is encountered.

Thanks All. I'll give these a look over on Monday, maybe we'll have some more votes by that time. With regards to making/accepting non-licensed or altered sounds it increases probability of litigation. A $5 dollar license can save a lot of headache down the road.?

Hello All, We are looking for a few ShutterStock licensed sounds to include for notifications. Please post requests in this topic along with links. Sound files are large so we will only include 6-10. Files must be available .wav and less than 30 seconds, preferably less than 10 seconds. Currently included: https://www.shutterstock.com/sound-effects/sound-20354-horrible-clock-radio-alarm

iOS Notification sounds should be working now.

Does the test Network Resource look like the image below with x-api-key value replaced with your key? I was able to replicate a 400 error by using Mode: URL-Encoded instead of Raw Text. NOTE: The image below shows timeout at 500 this should be increased to 5000 to avoid failures.

They are used for MobiLink and Alexa/Google Assistant. The user should be able to change this if they are not set. They are not required for UD-Mobile/Admin-Console. In my opinion there are too many parameter variations for this to work well to set UI Views and we should have a param for widget type (i.e. seekbar, toggle, default) for a command instead of assuming parameters with Hints. The Nodes should be available, have you tried restarting the ISY/Polisy? If they are set then I think the issue is portal is not seeing the nodes, let's see if a reboot corrects the issue.

Favorites launch type for M1 Mac should be fixed in version 0.7.9 which should be released to beta sometime this week. Still looking into SQL in memory database. In memory database backup fixed in 0.7.9.

Thanks, I think our server missing the sound parameter when sending to Firebase , will update as soon as the sound param is added. With regards to sound, I'll see what we can do in the future.

Hi @mbking, Appears to be a bug, will look into this later this week. Hi @hart2hart, When implemented in a Node Server it will use the "Emails/Notifications -> Customizations", so these can be shared between email and push notifications. The destination ("Emails/Notifications -> Settings/Groups") is specific to Email Settings so would require firmware change. We are moving away from modules included in firmware to modules as PG3 Node Servers. Email in firmware causes issues as it requires a firmware update when the CERT expires, so I would not be surprised if this module moved to PG3 for Polisy to allow CERT updates without firmware update requirement. With that said, I can foresee a Node Server which combines Email/Push/Text as a group.

Hi @DennisC, Thanks for the report, should be fixed in 0.150.

Production 0.150 Reset home fragment query to top most query on home tab reselection. Pop fragments on same tab on tab reselection. 0.149 Added Edit lock to notification settings. Bug fixes. 0.148 Updated Navigation Controller, bottom tab click will no longer reset fragment on selected. Added notification shortcut. Added error message for devices which do not support notifications.

Not sure I understand this request, can you give an example. The API is open and can be incorporated into an existing/new Node Server (i.e. Notification Node Server). IoP supports sending existing Admin Console notifications (i.e. email notification) to node servers. This feature will allow notifications to be sent via ISY Programs. The same notification can be sent to other channels (i.e email).

Beta 0.7.8 Added Push Notifications. Notifications can be sent via network resources, PG3 Node Server coming soon. Known issues with badge number due to subscription status using notification. Badge issue will be corrected in a future update. See links below for Network Resource setup: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Notifications_Tab https://forum.universal-devices.com/topic/35626-android-ud-mobile/?do=findComment&comment=341082

It's likely the nodes do not have a "hint", the node server Developer could add "hint" or it can be done manually. However this requires that the node commands definitions conform to the device type command names (such as on (DON), off (DOF), etc.) A work around is using programs or variables.

Hi @Ravi, Welcome to the Universal Devices Forum. Is your issue related to one of our products or services (ISY/Polisy/UD Mobile)?

Thanks @sjenkins, I think the backup file is not saving the most recent changes (in memory database). I've added an issue to our issue tracker. https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/58

Hi @jdm5, Currently there is no search function. I've added your request to our issue tracker. https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/57

Very odd indeed. Can you verify un-grouping all stations from the parent node, then re-group stations has been tried?

Version 0.145 has been pushed to production. Thanks to all testers reporting program creation bugs! Beta 0.147 Added Push Notifications. Notifications can be sent via network resources, PG3 Node Server coming soon. Node server will use existing email/notification framework available in ISY Admin Console and UD Mobile, however this feature is only available on IoP (ISY on Polisy). Network Resource method available to all ISY users on 5.x with an ISY Portal Account. These instructions will be added to our Wiki before production release. Network Resource Instructions: Click the new notifications tab in UD Mobile. Click the settings (gear icon) at the top of the notifications tab main screen. If you have linked more than one ISY Portal account (unlikely for most users) you will be prompted to select an ISY Portal Account. The screenshot below shows notification settings. Use the COPY button to copy your API key. If your key is compromised (like posting an image on the forum), the RESET button will invalidate the current API key and return a new key. The Devices section will list all mobile devices linked to the Portal Account. Clicking on a Device will allow users to enable/disable/delete the mobile device, enable/disable device membership in groups, and send test notifications. Add groups by clicking the ADD button next to the group header. Clicking on a group will allow group deletion. The instructions below will send notifications to all Active devices. The "UD Notifications" group can not be deleted from the App and is intended for sending notifications from UD, such as notifying the user when their ISY is no longer communicating with ISY Portal. UD Notifications have not been implemented as of 06/10/22. When a Device is deleted from ISY Portal and has an active UD Mobile installation the device will be re-added automatically. This feature is intended to delete old devices, to exclude a device from receiving notifications please click the device in Notification Settings then disable. The UD Mobile Notification-Tab must be clicked once before the device is available to ISY Portal, so please instruct all family members to click this tab after updating to a version supporting this feature. From the Admin Console Click Configuration-Tab -> Networking-Tab -> Network-Resources-Tab. Then Add a new Network Resource. Protocol: https | POST | Host = my.isy.io | Port = 443 | Path = /api/push/notification/send | Mode = Raw Text Header: Add x-api-key with the value as your API Key copied from UD Mobile. This is a manual entry not available from the dropdown menu. Body: title=message_title&body=message_body where message_title and message_body are replaced by your desired title and body values. Click update then save, then save all network resources. Finally press TEST to send the notification. Sending a notification to a group of devices: Follow instructions above to create a notification From the Notification-Settings in UD Mobile click ADD next to groups and create a new group. Click any device in the Devices section then enable the group for the selected device. Add "groupid=group_name" to the body of the network resource, where group_name is replaced with the group ID. The group ID is in parenthesis next to the group name in UD Mobile. The group name and id may be the same. Save the network resource, then save all network resources, then test.

Beta 0.146 Added Variable Precision change (Sync required). Added create, delete, and rename variable functions.

Beta 0.145 Removed Then/Else from program folders. Added Program edit from home tab. Fixed crash after saving favorite command type. Bug fixes.

Hi @pkelley, The SSL errors shown in UD Mobile is the raw error thrown by iOS's security layer. If your router has a VPN server this may be the easiest self managed option for remote connections. Unfortunately we do not offer support for self managed SSL Certs as it creates too many support tickets. If you have not tried ISY Portal we offer a 30 day trial with a cost of about $1 a month after that time. ISY portal subscription cost is usually less than the cost of a single SSL cert.

UD Mobile subscribes to ISY, so it's possible the subscription request does a query. This would be the same as opening the AC on another PC. The only time UD Mobile requests individual device status is when opening the Node's Dashboard, this is only rest/nodes/nodeId not a query.