Javi

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.

With regards to UD Mobile favorites, the easiest way is to verify you have migrated and everything is working and connected to Portal. Then DO NOT add the new system to UD Mobile, only reset the UUID, Portal URL, and Local URL (if using local connection settings) Create an App backup in case of error Clear UUID from the existing (old) system at the bottom of the System Configuration Screen Reset URL(s) by pressing the search icon (magnifying glass) next to Remote URL and Local Url (if using local connections) https://forum.universal-devices.com/topic/41219-move-favorites-from-isy994-to-eisy-device/

UD Portal API Key or Pushover API key?

Scenes have no status, so it cannot be ON or OFF, it can be controlled to ON or OFF. UD Mobile has an Estimated status which can be configured the way you want, by disabling calculation for the button with is On when you want the scene to show an Estimated status of "OFF"...you may need to trigger the scene at least once before the app is updated.

Please be specific. We have many enhancements in the pipeline and we prioritize based on user feedback. There are also many advanced features which require some understanding of UD Mobile and IoX to accomplish. Both homekit and roomie are iOS only apps, so UDM is already better if you have an Android phone. The great thing with the Node Server platform is UD Mobile does not need to include any features for new Node Servers. If a developer creates a Node Server it will automatically work with UDM no matter how unique the status or commands definitions. Passion for the one app is mine also, and UDM controls everything in my home aside from choosing content from Netflix/HBO/ect apps. A/V, Lights, fans, sprinklers, water control/sensing, security, dog door....... all controlled from UDM but mostly automated in IoX. IMHO the "No Hub" is a marketing gimmick. If you need a router for WiFi, or an iPad on your network...you have a Hub, and one that may require replacement every few years.

There is no silence. The API's for integration are publicly available here. I developed an Android app, Go2ISY, which was one of the first to integrate version 5 apis a few years ago....before being hired by UD. Depending on the integration it may be difficult for some to integrate some device types. A Node Server can be almost any Thing, which may be hard to integrate into software supports a small number of Things. What Roomie Remote feature(s) are the most useful? Maybe there is a way UD Mobile can do the same or we can add to our list..

I believe it will remain, jimbo will need to confirm.

The new node is a simplified version with better command names. This is intended for direct integration into UD Mobile to allow users an easy way to setup notifications. We will make a formal announcement as soon as everything is ready.

For iOS there is no other way to lookup location when the app is in background as Apple has this locked down. Apple already denied our request to run in the background for Geofencing purposes by stating the Geofencing APIs are all that is needed and we had to remove background tasks. The Geofence APIs do not allow us to poll location only receive events from iOS. So, I would need proof that iOS does not handle this properly in order to contest Apple's denial. We have an open issue in UDM with timeouts, however I have yet to be provided new logs since the most recent update. The latest update contains more details regarding to narrow the issue. We do have polling on Android as we have proof Android does not handle Geofences on all devices. Without seeing logs I can only speculate as to the cause. If this is caused by no internet, then you could workaround. If caused by iOS blocking connection, then UDM or iOS needs to be fixed. If you are having intermittent connection failures on entry you could add additional fences with smaller radiuses which only have the enter command. If you are having intermittent connection failures on exist, then you could add additional fences with larger radiuses which only have the exit command.

As @MrBillsuggested. No need to add the other devices to the scene. A separate program is needed if the current program is being used to to trigger physical button presses. Most important part is that it is disabled as it would cause a vicious loop if it is automatically evaluated.

For a UDM Custom Toggle the condition needs to be Status. Control implies physical touch of a button. The program also needs to be disabled so it does not run in a loop. The next issue is how the condition (toggle) is evaluated. In your program you are using a physical button as condition. So this button needs to be switched on/off in the actions (then/else) or it will always be evaluated the same. In your program this will need to be a scene as keypad buttons do not have direct control. To simplify this lets remove all the lighting controls and only focus on the status and condition evaluation. Because this is an insteon keypad we need a scene (again as keypad buttons can not be controlled directly) So our standard keypad scene (without modifications to controls) Our DISABLED Program Our UDM Command Button. Notes: This uses Display Node of the Keypad Button Scene and Display Status of Estimated Status to show user if the toggle is on or off. But this could be changed to the Keypad Button itself. The program is set to command "Run IF" Now that the toggle is working you can add other actions.

I think you need Status not Control as the If conditions. In the currently condition both switches would need to be physically controlled at the same time to be true. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

Create a UD Mobile backup first just in case anyone synchronizes incorrectly from Settings Tab> Backup. Go to the existing (old) system's settings in UD Mobile >Settings Tab>Systems> Your System. Scroll to the bottom and click clear UUID. Then click the search icon next to the remote url and select the new system. Finally synchronize. Ignore errors as they are all true as the UUID was cleared. If you had both the new and old systems in UD Mobile delete the new system as the old system now has the new system's credentials.