Javi

If you already upgraded you don't need to press force upgrade.

http://ipaddress:8080  then the path i.e. /rest/history/etc

Check out the custom toggle example. A favorite which shows one node as status and executes a program (or node command) when pressed.  Search the forum, Others have posted about setup of the same the same.
https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

Currently not possible, but similar requests have been made in the past.  i.e Tab Tiles.  
Tab Tiles are on the list but not sure when I'll have time to implement.

See the custom toggle example https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle
In short the Display Node and the Command do not need to be related, but the command should cause the Display Node to change.  The command should be a Program Run IF so it holds all logic related to the toggle.

It's due to how insteon processes scenes.  A command is not sent to individual devices it is sent to the Scene. A Scene has a predefined rampRate and onLevel (a preset). An Insteon Scene is more like a preset than a controlled group. For eisy to do this it would need to send a command to each device which would be out of sync (the same as sending a command to each device in a program).  Not only would be out of sync but would likely fail to trigger some devices due to traffic.
So to achieve what you are looking for you have two options.
1) (recommended) Create a new scene with all devices as responders, set the level to 10.  Then trigger the new scene from the program.  This will allow all devices to come to the specified level at the same time.
2) (not recommended, but this is how it would work if you physically held the switch to a desired on level) Trigger the Fade Up on the scene then Stop after some time.

The app error is a bug in the app.
We have submitted a new version to both app stores. Still awaiting approval from Google/Apple.

Thanks for testing,  Currently the chart automatically adjust to show the last few changes, however there is a bug and the time on the chart is not correct. In your case the time is likely closer to the current time.
Adding this to favorites is on my list. Along with other improvements.

There used to be, but it was inadvertently removed during a UI refresh.  Adding it back is close to the top of the list of To-Dos.
It was similar to Favorites Move to Folder. 

The Favorites page does not separate by controller, nodes from multiple controllers can be displayed on the same page. This is by design, in case users want to view status of multiple properties at the same time. 
Users can create Favorites Folders if there is a need for separate favorites pages.  This can be for seperate properties or any other reason.

As far as I know this should only happen after opening a Node's Dashboard.  If you swipe app from recents does the Home tab still show this error?  Does it only start showing the error after clicking a specific Node?
If both answers are true go to the node and find the status value which is set to a chart, then change it to "Default" or another type of view.  
If this does not correct the issue, or the answer to the questions above are false then please open a ticket and include a ZIPPED COPY of the UD Mobile Backup file so that we can investigate.

That look correct, RUN IF (Set RUN IF) should be triggered on geofence enter. 
The program itself needs to be disabled or it will run at the time in the IF condition.
This can be tested when the time is valid by pressing Trigger Enter Command.  Note that geofences may take a couple of minutes to trigger so the radius may need to be larger.

It appears move to folder was left out after the latest app refresh.  We will try to re-enable this feature in an upcoming version.

Action buttons will be shown above favorites in next update.  Bug introduced when we added transparent (scroll through) navigation and tab bars.

Please open a ticket, included the browser screenshot and a copy of the node server's log 

Try restarting the Node Server then check the Node Server's Log.   On restart the plugin will parse the codesets so any errors will be logged.
This looks correct, but the others are definitely incorrect (see https://forum.universal-devices.com/topic/34813-itach-ir-node-server-global-cache/)
I just requested a code set from the control tower database and the format does not appear to have changed.  Also be sure to press the "Send Code Set" Button, do not "select a Function" when requesting the code set.
 

There are no Default Notifications, but you can trigger a notification directly or via program.
First add the Notification Plugin if you have not already done this.  Then create a Notification Customization for entry and exit.  Finally trigger the desired notification on enter or exit.
 

Replicated, thanks.
It looks like something changed in the recent iOS update, the app is trying to push the user to login but can not launch the view so it restarts at Home Tab. 
I don't yet have a fix and can only test on the emulator as I left my iPhone cable at home. Please try to disable WiFi and Cell network which should give you time to get to the Account Settings before refresh.  Finally re-enable the Mobile Device's network and login.
If the refresh happens before you can login, remove the Account (trash icon) from UDM on UDM's Account screen.  Then go to the Controller's settings and login when prompted.
I'll push an update as soon as I can verify a fix, but could be 24 - 48 hours before approved by Apple.

This may happen if the app is deleted or app data is cleared, the new instance of the app creates a new Device.  Apple does not let this persists or transfer between apps/devices.  If you have a screenshot taken before changing the enabled value, or remember, the "Updated" timestamps it may give some clues.  Could have happened recently or long ago, the former could be the cause of your issues using Notification Groups as the "new" device needs to be added to the group.
Click the Mobile Device in the list and there should be a delete option at the top.

Yes,  eventually the Home tab will only show devices and scenes as multiple controllers will be in the controller dropdown header.

This was removed as we had too many ticket where users hide the controller from themselves.  However the most recent version on both Android and iOS now automatically show the default (last selected) controller on the home screen.

If this is no/null status then it is likely disabled in settings.
https://wiki.universal-devices.com/index.php?title=UD_Mobile#Program_And_Variable_Settings

I cannot replicate, however I notice that the strike through the equals-sign is not easy to see.   Which screen has this issue?

That's not good...I'll push a fix now to correct the issue.  Depending on Apple's review could be a few hours or days until live.

Thanks for the report, will be fixed in 1.1.67 iOS and 1.1.87 Android.