Javi

Yes, please upgrade to the latest version of UD Mobile and the option will be available. For anyone else with Polisy: Polisy can be migrated to PG3x PG3x also allows remote connections to PG3 (plugin software) although a reboot may be required.

https://wiki.universal-devices.com/index.php?title=UD_Mobile#PG3_to_PG3x_Migration

Please also try rebooting Mobile device. Then synchronize when prompted. If this does not work please open a ticket and include your UUID and we may be able to perform a remote diagnostic.

Eisy contains most of the prerequisites for this to function Update to the latest version of UD Mobile and the app will alert you to anything that needs to be upgraded. If a firmware upgrade is required it should be done while on site. See https://wiki.universal-devices.com/index.php?title=UD_Mobile#Updating_System_Firmware for tips.

UD Mobile installs and configures the Notification Plugin (Notification Node Server) If you already purchased the Node Server you will just need to update to the latest version as your purchased version has more features. However because UDM uses a new command your existing notifications will not show in My Notifications, although you can see them all from linked programs from the Node's Dashboard in UDM. This feature also requires updates to IoX and PG3. So like all updates it is recommended you are on site in case a physical power cycle is needed.

Production 1.1.7 Added basic Notification Node Server setup and configuration. See the following video for instructions or our WiKi for some common issues when upgrades are required. Allow Widgets (slider/switch/etc.) for commands with multiple parameters. This should allow widgets for most Z-Wave devices. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Missing_Widget Automatically open System Folder if there is a single system on Home Tab.

Production Version 1.1.12 Added basic Notification Node Server setup and configuration. See the following video for instructions or our WiKi for some common issues when upgrades are required. Geofence will now retry when active network cannot be determined. Added Active Network check before most ISY connections. Allow Widgets (slider/switch/etc.) for commands with multiple parameters. This should allow widgets for most Z-Wave devices. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Missing_Widget Automatically open System Folder if there is a single system on Home Tab. Favorites status and values are now a single line. This will prevent resizing Favorites when loading.

Try clearing browser cache

What hardware is this? A System reboot should fix the issue. The cause is usually a client which fails to unsubscribe.

Hi @scote, Please try disconnecting the power source, wait a few seconds, connect power source, wait 5 minutes for system to be fully online, try again with synchronization.

Thanks, should be fixed in iOS 1.1.5 and Android 1.1.10 Fixed wrapped button text center. Fixed typos. Moved Reboot to Reboot View for screen-on, and system reboot requirements.

Replicated an issue which may be related. Some Android devices or versions do not timeout when OS does not find WiFi Access Point, added to issues. Some common causes are listed in troubleshooting https://wiki.universal-devices.com/index.php?title=UD_Mobile#Troubleshooting

Android OS Geofencing is broken on most devices, see this post, so UDM has its own location service. Usually if you have Google navigation (Maps) running Android OS geofence should trigger within 2 minutes, if not then UDM location services will update at the polling interval or whenever WiFi connects or disconnects. Disconnect waits some time to allow exist of fence. So, If Android OS Geofencing is broken on your device you have a few options such as running Google Maps cuando estas en auto or adding additional fences . Add additional fences with larger/smaller radiuses which increase/decrease polling interval. For example add multiple larger geofences which on enter sets polling interval lower and on exist sets polling interval higher, then when entering the "real" fence set polling back to default.

If the system is linked to Portal please send me the UUID in a private message and I'll run a remote diagnostic. I have a little extra time today, or anytime during business hours.

The backup file contains the full log, it can be sent to me via Private Message or as an attachment to a Ticket when zipped. The screenshot of the log above does not show any events at 2:14 PM, or the previous triggered crossing. The logs are automatically deleted, so issues must be recent or they may have been removed from logs.

Appears that the app is crashing. If the following does not work please open a ticket and include your UUID and we may be able to perform remote diagnostic. We have encountered a handful of users who created a vicious loop in a program which causes UDM to crash. The usual culprit is the Query Program which users try to fix but create an action to run itself causing a never ending loop, but this could be any program. eisy is much quicker than ISY so the events queue in UDM until events overflow memory in a few seconds. Please check for running programs in Admin Console then stop and disable any programs stuck running. Stopping and Disabling the program may take some time as the AC is likely having the same issues as UDM. The PC has more working memory and processor speed so it may be a few minutes before overflow is triggered.

Not sure, the posted image of the log does not show the app registered any geofences. I would need to see the full log to check for errors. The logs are limited to ~70 most recent entries. If the issue is network related (i.e. timeout), we can try to find a solution. If the device believes you are in another location, then increasing fence radius is usually the only way to correct the issue. Both my wife and I have Pixel 6 phones, and mine frequently registers about a quarter mile away when location is requested. This caused a similar issue where it could take a few queries before the location is accurate which triggers the fence crossing. My Wife's phone is accurate with 200m radius and mine is only accurate with a 700m radius. So, radius is very much device dependent even with the same model phone.

On Android I believe you can use Tasker to trigger Bluetooth connected/disconnected and for transportation modes (or whatever it is called) like biking, walking, and driving. The former should be easy to implement and track by updating a variable using REST. The latter is based on a percentage of confidence which may be more difficult. Currently these items are not on our list for UD Mobile. We had UD Mobile working with Android Auto in the past but Google rejected our app as it did not fall into the accepted Android Auto categories. They recently added a category which may allow us to resubmit, although I do not have a timeline. Currently a user can hide items then lock edits. For example, add items you would like the family member to access to Favorites, hide the system on the Home Tab, then disable edits. Now they only have access to Favorites and will not be able to change anything on the Home Tab, Admin Tab, Settings Tab, or any Top Menu.

Is your system linked to ISY Portal? If not please add to Portal, the system does not require a subscription it simply needs to exist. After this is added try again. If that does not work please open an incognito browser, which will prevent any saved data from interfering with login (in Chrome this is the 3 dots at the top right > new incognito Window). Then open developer tools (in Chrome this is the 3 dots at the top right > More Tools > Developer Tools). Click the network Tab in Developer Tools. Now go to the PG3 web interface and attempt to login. Do you see any network requests (under Name) in red?

Yes iTach IP to Serial. Have not tested on anything else as the URTSII is too far from UD Equipment. I do not recall any node servers, other than eISYIR, using hardware ports. I think the Somfy NS worked hard wired in PG2 and RPI, not sure if it works with Polisy/eisy. Maybe someone else knows better.

Forwarded your suggestion to Sales.

I've been using an iTach with RTSII and network resources, setup long before Node Servers existed. At the time it was the best solution for the price. The range on the RTSII is also not great, needed a repeater in 1200 sq per main level home (basement and main level automated). The home was built in the 40s and has expanded metal on all walls to hold plaster which may be part of the issue. Something to consider when calculating total cost.

For new installations of UDM the app will guide you through initial setup, for existing installations go to Settings Tab > Systems > Add (top right). We don't want the app looking for new systems everytime it is started as this could cause delays. If transferring your setup from isy to eisy the migration instructions must be followed as this may require some manual intervention depending on your ISY firmware.

Reboot Polisy. The error is caused by too many frontend clients having connections and/or failing to close connections to Iox (not PG3). It could be a coincidence that you installed a Node Server at the same time, or it could be that one of the clients is crashing due to unrecognized data. So if reboot does not fix the issue, then you will need to start eliminating clients to find which one is not behaving correctly.

This error is usually related to clients (i.e. Admin Console, UD Mobile, HA integration, PyISY) not calling unsubscribe from the ISY event stream (subscription) when it stops viewing or perceives there was an error. This causes all available subscriptions to be used so new clients (i.e. Admin Console) can not start properly. Usually a reboot corrects the issue, or waiting some time. Waiting some time assumes the client causing the error is acting properly or it may continue using available subscriptions (event streams) which will continue lockout. PyISY, used by the HA integration, was a usual suspect in the past but I thought it was fixed. So if the issue persists after reboot try disabling the HA integration or any Node Server using PyISY.