Javi

Unless you intended to have 2 instances, the one not linked to any of your programs should be removed.

Please try synchronization,
The most recent app update should have alerted all users on first open to synchronize....should also be much faster

Fixed in the next app release for both iOS and Android.

Just tested and Groups work, are you sure the program was saved prior to testing?
You can also test from the UD Mobile Node directly.
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

The process has changed as the automatic change to Favorites causes issues in some processes if the user leaves or the app directs user to a webpage.
New process is listed here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Show_Favorites_at_launch

UD Mobile is not yet fully compatible with eisyUI, so local creds must be legacy credentials and port 8080 until further notice.

Issue corrected for UD Mobile iOS in app version 1.4.5 and greater.  Should be released within the next week.

See https://forum.universal-devices.com/topic/45966-favorites-gone/#comment-399961

Please synchronize.

Might be a bug in Favorites tab at startup, try pressing the Favorites tab button.

Currently no, while Portal (ISY Information) has your public IP Address it is not shown in app.
Have you tried a service like dyndns? It is supported my some routers, or software that runs on an always connected server/pc. This way you will not need to enter the IP Manually.

Currently there are no "tabs", but is on our list.
There are "Folder" Favorite Types, which also support a display node.
See: https://wiki.universal-devices.com/UD_Mobile#Type

Should be fixed in the latest release.

I think it may just be unintuitive,   #71A6FA is not the default (ios version tint color) it is an example. Try pressing the delete button at the top of the color edit dialog.

Some of the synch changed so possible app error. However more likely the NOde Server in slot 5 is not configured correctly.

Not yet,  we are in the process of migrating to new iOS APIs, but have not yet refreshed home/favorites screen.   Should be fixed on some other screens.

Not directly,  but if you have an application with can call a url you can use the Portal Geofencing Node Server.
The following link is how UDM can work with the Portal Geofencing Node Server. The NS can also be triggered with a portal URL, which is how 3rd party Geofencing works with eisy.  https://wiki.universal-devices.com/UD_Mobile#Occupancy_v2.0_Node_Server
I have played with iBeacons in the past as presence detection but it was too unreliable to triangulate using signal strength, but it may work if only requiring detection instead of triangulation.   

Hi Bob,
I don't follow exactly, but I think there is a simple solution.  KPL buttons can not be controlled programmatically (unless it is the button with the load), they must be controlled from a scene.   So, if I understand you want to issue a command to the scene,  If this is true use type "Command" then for the command set the Scene to "ON".
https://wiki.universal-devices.com/UD_Mobile#Favorite_Custom_Toggle
With that said check out the 5.x fan example which simplifies KPL Buttons, so you only need 3 (high, med, low) and only one can be lit at a given time, pressing the lit button will turn the fan off.  Then UD Mobile can control the fan module directly and the KPL Buttons will remain in sync.
https://wiki.universal-devices.com/ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

Thanks,
Fixed open device dashboard for folders in both Android and iOS in next app version.

Glad you like the charts!
Incorrect time is due to a bug in firmware, I think it is now fixed on our side for the next firmware release. So feature is still beta until firmware release.

Node Def:
<nodeDef id="MQSW" nls="SWITCH"> <editors/> <sts> <st editor="ONOFF" id="ST"/> </sts> <cmds> <sends> <cmd id="DON"/> <cmd id="DOF"/> </sends> <accepts> <cmd id="QUERY"/> <cmd id="DON"/> <cmd id="DOF"/> </accepts> </cmds> </nodeDef> Editor:
<editors> <editor id="BOOL"> <range subset="0,1" uom="2"/> </editor> <editor id="ONOFF"> <range uom="78"/> </editor> <editor id="TEMPF"> <range max="176" min="-40" prec="2" uom="17"/> </editor> <editor id="HUM"> <range max="100" min="0" prec="2" uom="22"/> </editor> ........ </editors> Summary: Editor ID "ONOFF" is missing  min/max or subset
Added pull request for developer
https://github.com/Trilife/udi-mqtt-pg3x/pull/16

Thanks. Reporting here works better. I can search the apple crash reports, but don't usually start there. There are major changes in versions > 1.2.8 in preparation for removing synchronization requirements with firmware 5.9.x. So possible there are other bugs.
I could not replicate but my commit history show something similar on the July 9th so likely did not make it into the last release.  I'll push version 1.2.12 to beta now, but may be a few days until live.
 

I'm not sure, the sounds are included in the app's package so should work unless the user has changed setting on Android OS. Did you happen to customize the sounds on Android?  Maybe the file no longer exists?
https://wiki.universal-devices.com/index.php?title=UD_Mobile#Android_2

Hi Everyone,
 
See the following for an update:
 

Most customizations should remain intact if the UUID is cleared in UDM (see link below) and the new Credentials (IP address, remote URL, and auth) replace the existing credentials. 
The node-address + SQL-Controller-Table-Base-Column-ID (as UDM supports multiple controllers) are the unique identifiers.  The controller SQL-Controller-Table-Base-Column-ID is tied to the UUID however the UUID is not part of the Unique identifier.  UD Mobile allows users to "clear" the UUID so the SQL-Controller-Table-Base-Column-ID remains intact when the UUID is cleared. UD Mobile will add the new UUID to the existing SQL-Controller-Table-Base-Column on Synchronization if the UUID is cleared.
At a higher level if the node-address does not change then customizations will remain intact.  If synchronization prompts to "remove cached values" after replacing the UUID then create a backup before removing cached values. If customizations/favorites are removed restore the backup then adjust any customizations which were removed to point to the new node-address before synchronization again. 
Insteon should be safe in most situations, other protocols/node-servers have enumerated node-addresses so they are susceptible to Address change. So keep node servers in the same slot and add all required parameters prior to synchronizing UDM.
https://wiki.universal-devices.com/index.php?title=UD_Mobile#Migration