Javi

Portal Licenses are tied to the Controller not the account, so you just need to remove the controller from your account (or revoke locally) if you sell. The new owner just needs to add the controller to their account and approve locally. UD Mobile works with local only connections: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Local_Only_and_VPN

Yes, The Advanced config is linked to a node property not a favorite. If only a boolean is required then the program route will work without the need for more variables, but you will have more programs. If this was a real device, not a variable, I would suggest the Favorite Type Picker which would show the command dropdown. Another option may be the Virtual Node Server.

The Advanced Status (list) is linked to the Node (variable) property (value). So the Home Tabs and any favorite with this node (variable) as the Display-Node will use the same Advanced Status (list) as the list is linked to the Node Property not the Favorite. I don't quite follow what you are trying to achieve, so the following is based on the assumption that you want to show the status on each button along with a different color. If you don't need status then remove the Display Node and use Color in the favorite's editor, not the Advanced Status. To show 3 different colors for the same node property you will need a work around as this is not a common situation. UDM is very flexible so there are a few ways to do this. Using 3 variables which are all set to match the tracking variable. This can be done in a program, something like if state_var_1 changes set var_2 to equal state_var_1 && set var_3 to equal state_var_1. Now you have a separate node which has its own Advance Status list. Using programs with only an IF statement to match the desired status. Then in the Program's Advanced Status list change the color based on Idle-True and Idle-False (i.e. is desired status true or false).

What is the app version? Version 1.2.8 was released this morning with bug fixes.

Issue should be fixed in iOS app version 1.2.7. Usually takes apple a couple of days for review before going live. Thanks

Thank Guys, I had a few reports of this issue but could not find a Firebase crash log. @Geddy 's Apple report actually came through with the crash log. I don't even check there often as the reports usually fail to include the crash log.

It's still on our list, but can be done from the Admin Console. Scenes in version 5.x are much more complex than Scenes in 4.x (see the 5.x fan example). Also for insteon the Scene information is written to the Controllers/Responders so may take some time depending on the number of changes. Each Scene-Controller-Settings has an on-level setting for each responder in the Scene. The Scene-Settings also has an on-level setting for each responder in the Scene. So changing the on-level for each Responder manually may not be intuitive or may not work as desired without changing many properties. So, if you set the Scene-Settings on-levels' for each responder, it will only work if you trigger from eisy. Setting on-levels from a Scene-Controller-Settings will only work when triggered from that Controller. What are you trying to do? There may be another way to accomplish the same without getting too deep into the settings every time a change is needed.

Should be fixed in the next version Android 1.2.28 and iOS 1.2.6. From what I can tell this is only an issue with displaying the formatted value, the mapping should still work.

Understood, and yes the numerical IP is more reliable than eisy.local. We have encountered home networks which stop routing to dot local and Mobile devices which stop routing to dot local. Usually corrected by restarting the Router or the Mobile device. With regards to reset local credentials: They are managed by iOS keystore so loss of local creds should correlate to lost remote creds. The app will use "admin" for local username or password if it cannot obtain a stored value from iOS keystore. iOS Keystore may (but not always) loose values or the app may lose the key if the app is uninstalled, backup is imported (if the controller ID is not the same), or the controller is recreated (deleted then added) in UD Mobile. Being as keystore is managed by iOS there are a few reasons (such as corruption or security related change on the device) that keystore may fail to return a value, but I think this a low probability. So there are a few ways keys or values may be lost. My guess is one of these things happen and the app prompted to re-enter remote credentials (i.e. login) at some point in the last 2 months. This is the only report I have for this issue without the user changing something, so I'll keep an eye out. Let me know if it happens again without an import or reinstall.

@dbwarner5, Based on the screenshot it does not appear the app lost local connection settings. There was a new setting (switch) added which produces that error message. If you try to enable automatic detection but have already defined a WiFi network then the app will show an error saying you need to remove defined networks for Automatic Detection. Note that it will always be more accurate and faster if you have a reserved ip and a defined WiFi network in UDM. If no wifi network is defined the app may still use the remote connection when Automatic Detection is enabled. The likely cause for connection error is the app cannot connect to the eisy.local address. My suggestion is to add the numerical IP address in the app with an IP reservation in your router. If permissions were changed, it was the user or iOS which changed the setting, the app cannot change iOS permissions.

We have updated examples on creating and modifying notifications. These new examples show both the AC and UD Mobile at the same time. Setup: https://youtu.be/KSmx-XIquAw Sending to a specific Group or Device: https://youtu.be/z4pquLcI2Es Creating your own notification content: https://youtu.be/KSmx-XIquAw?t=165 FYI: there is a bug in custom content prior to 5.9.1 which will not show customizations after a missing ID (sequentially). This can be fixed by adding a new customization until all the gaps are filled.

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

Do the logs show any errors? Currently on android there is not copy, just screenshots. I recommend deleting before leaving or entering the boundary then checking the log for an error message. If there is an error message it may be self explanatory, if not let us know what it says or share the screenshot, but paint over any sensitive lat/long data.

Found issue, fixed in next version.

iOS or Android?

Reference https://github.com/JavierRefuerzo/iTach_IR_Node_Server?tab=readme-ov-file#general Only one configuration is needed per device (not per code). Please post the value input into the node server, it's possible they changed the format so the Node Server cannot parse. Being as there is only a single value the delimiter between codes may not match, if I remember correctly it is a double space or maybe a double new line.

Not in app, currently only at the top of Admin Console. Is on our very long TODO List.

Not changes, and I use android and it triggered this morning. Have you tried restarting the Android Device? Also verify Location is enabled on Android Device. UD Mobile has location permission. And the Geofence inside UD Mobile is enabled. There is also a bug on some android devices/versions which requires the "(Experimental) Force Geofence updates.." to be turned on. So you may want to turn this on to see if it starts working This was never implemented on Android, still on my TODO list

Ok, thanks.

Thanks for the information, I was not aware that enabling developer mode allowed commissioning to move forward. Did you install a developer profile also (this is a file import you would know if you did it) ? As for the crash, please open a ticket. This is likely not related to the app itself so will need to be handled by someone else.

Currently not with iOS, only Android.

Was this resolved in the ticket? Notes: Cancel any alerts/warnings/sync-request in controller settings. Scroll to the bottom and press clear UUID. Be sure to update Remote and Local URLs to point to the new controller.

Please post a screenshot of the error message

The UDM Synch error is fixed in the next app update. It can be ignored until that time as it is only stating there are no matter devices.

The notification is generated from the box itself, so there is an update. The app does not know the version, it pulls the version from a server, but looks like server was not updated with the current new version.