Javi

I'm the frontend developer for UD Mobile so I can say with confidence that UDM Notification delivery is stable in production. As of this week UDM Notifications now include notifications about Portal Service interruptions and system connection status. Notification Creation is stable using Network Resources (the only option if you have ISY994). For eisy and Polisy you can use the Notification Node Server. The Node Server route makes things easier for users to configure but does not render the Network Resource option obsolete. The Notification Node Server uses the same APIs as the Network Resource Example. See this topic for an example of setup:

Hi Dennis, Settings>Systems>Your-System>Disabled only disables subscription startup in UDM. Is this system listed on your Portal Account? If it is not then there should be no notifications about connect or disconnect. If it is listed but there is no subscription then remove from portal.

Looks like the app is using the Basic Remote Connection Port if Port was set when "Use ISY Portal for remote connections" was switched off. If you have a backup you can reload, switch off "Use ISY Portal for remote connections" delete port then switch back on. Added issue https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/45

Sorry to keep pressing this, but have you synchronized? If that does not work please open a ticket and include a zipped copy of the App's Backup file or Send the file to me via Private Message and I'll try to replicate.

Can you verify synchronization was done? The values for enter and exit commands are the commands sent. Just tested and I can set and edit both Enter and Exit commands for State variables, can you share a screen shot of the same screen?

Hi @peterathans, I cannot replicate this behavior so please first verify you have the latest app version as I believe there was an edit bug in an initial release. Then try synchronization in case anything has changed with the system. If that does not work: Is this iOS or Android? State or integer variable?

Due to a recent iOS update we now only receive the Mobile device type and no longer receive the name given by the user. You can change the device names in Notification settings along with sending a test notification to a single device.

Still on the to-do list.

The API to send to a single device is available by request for Node Server developers. It was not included in the Network Resource Examples for reasons stated above. Jimbo's Notification Node Server uses this api, but only after checking the Device Name. So the Node Server is essentially creating it's own groups with the Device Name being the group name. We discovered the group issues during testing, it was not reported by any users until your post.

Great! We discovered a server side bug in group enrollment a few weeks ago which may have caused the issue. This issue has been resolved so please let us know if the device becomes unenrolled in a group again. In my opinion Groups are the best way to send to a single user. When you get a new device you only need to add it to the group instead of changing all your notifications. The method to send to a single device is not documented on our wiki as the prefered method is grouping.

Version 1.0.33 Removed Location updates when map view is paused which caused location to be continually monitored after viewing map. Added WiFi only UDM Location Service request, with polling interval set to a negative number. Added Continuous UDM Location Service request when polling interval set to Zero. https://wiki.universal-devices.com/index.php?title=UD_Mobile#UD_Mobile_Location_Services

That is a success message, so the call is making it to Portal. If you received a notification on test, then Portal can contact Mobile Device. To access Permissions on Android, long click the app icon then select App Info (i) icon > Permissions > notifications then verify all are enabled. On iOS this is in the iOS Settings > UD Mobile > Notifications. Are the notifications listed on the Notifications Tab? The notifications tab request notifications from server so it is independent of Notification Permissions. So, if they are not listed on the Notifications Tab, then the notification is not being sent to the correct account, device, or group. Are you sending notifications to a specific device or group? If you are please verify the group/device id is correct. If using group verify the device is in the group. If none of the above solves the issue please copy the "Actual" part of the Network Resource and post here, be sure to remove your API key before posting.

There were no production releases until today, so likely not cause by app update. Check app permissions for notifications. Notification settings have a test button, does this work? Verify API key doesn't have a space at the end.

Version 1.0.32 Changed UD Location Services Polling delay to Alarm Manager APIs. Added WiFi connect/disconnect as triggers for location update in UDM Location Services. Added Geofence Logs Delete. Added Package Update listener to restart UDM Location Services. This release will allows UDM Location Services to have an additional trigger to request location. When the device connects to WiFi location update will be requested immediately. When the device disconnects from WiFi location update will be requested after ~2 minutes.

Hi @HABit, Thanks for the report. Fixed negative entry in timer dialog for iOS in version 1.0.26 You can work around this bug by first deleting the "-" symbol before entry.

Beta Version 1.0.25 Removed background location access at Apple's request. This does not appear to affect Geofencing. Please report on UD Mobile sub-forum if geofences are not triggered.

Hi @TJF1960, Version 1.0.30 is awaiting approval from Google, this can be anywhere from a few hours to a couple of weeks. Instructions to join beta can be found here https://forum.universal-devices.com/topic/35626-ud-mobile-android/

Beta Version 1.0.30 Added Geofencing, UD Mobile Location Service, and Notification Settings to alert users when eisy disconnects from Portal. Basic Setup Example: Geofencing: Geofencing provided by Google Play Services is broken and acknowledged by Google. Play Services Geofencing will work when any app using Play Services APIs updates the System Location, but will not trigger a geofence until UDM or another app updates the system location. To get around this issue UD Mobile on Android implements a Location Foreground Service to poll the device location. UD Mobile Location Services are disabled by default. UD Mobile Location Services: UD Mobile Location Services are services to assist with Geofencing and will consume battery. UD Mobile Location Services are NOT required for Geofencing however Android may not update your geofences until another app or the Android system requests location. If you are in your vehicle with Android-Auto/Google-Maps running then UD Mobile Location Services should not be required as these types of apps will update the Android System Location. UD Mobile Location Services will run in the foreground and will be shown as actively running in Notifications and Android Settings. Polling interval for UD Mobile Location Services can be updated to any Geofence Enter/Exit commands. This will allow users to set larger Geofences to increase polling interval as the user gets closer to a desired smaller radius Geofence and decrease polling interval as they get farther from desired smaller radius Geofence. The UD Mobile Location Services may have bugs so please report any issues in the UD Mobile sub-forum. Logs for both Geofence and UDM Location Services can be found by pressing the log icon at the top of the Geofence List screen. System Notifications: Notification of System connect/disconnect from Portal is implemented in app but is not yet in production for all users. There will be a separate announcement about release date and how to disable this feature.

Hi @asbril, Geofencing in iOS is still in Beta and Apple wants some adjustments to the location permission requests before release to production, so it will likely be at least another week before it is live in the app store. Currently Geofencing on iOS issues a direct commands to any node/variable/program/etc. So there is no Occupied node, but something similar could be setup using a variable.

If the issue is only on a select number of devices, then it is likely an issue of communication from PLM to Device. Try to restore the devices or factory reset the device then include. If the issue is with all devices then it's likely PLM issue.

I'll push to the production app store today. Will likely be 1-3 days before it is live in the production app store.

Hi @DennisC, Yes, I can add any icons available from Google Fonts without royalties. If you find any that suit your needs give me the URL or name and I will add them. https://fonts.google.com/icons?icon.style=Rounded&icon.set=Material+Icons

Added to our list, but we are currently months out for new features. https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/44 While this is not implemented into UD Mobile I've done it before with tasker. Adding camera feeds to UD Mobile is high on our list, but I do not have an ETA. In case you are interested in DIY implementation. Doorbell sensor: https://voiceforiot.wordpress.com/2018/10/06/traditional-doorbell-wireless-sensor/ Triggering video, this is on a watch but could be on a phone also:

It is in Beta, we are waiting for approval of 1.0.24 which has geofence bug fixes. If no other issues are reported 1.0.24 will be pushed to production. Beta testing info: https://forum.universal-devices.com/topic/35814-ud-mobile-ios/

Yes, if you don't import backup then each device is independent just like favorites.