Javi

Thanks,  replicated issue.  Submitting version 1.1.79 now.

There is no real way to toggle a program, as the commands which handle running programs are runIf, runThen, runElse, and Stop.  UDM emulates the a program toggle by sending runIf (if not running) or sending stop (if running then/else).  So On is "running" and Off is "stopped".
As a work around an integer variable as boolean (0=false | 1=true) status can be created.  Enable the current program then set the variables boolean value in the then and else conditions. Create another disabled program which is triggered by UDM which has an if condition using the variable. The original program can still be used as the Display Status if needed.

Not yet, We have other PG3 fixes close to the top of our list so will look into at the same time.

It looks like status is not being populated so UDM cannot determine which direction (on/off) to toggle.  Pressing the tile when there is no status should take the user to the "Device Dashboard" which forces a query for status, after this point the app can toggle.  However it is very likely that status was missing because UDM is not receiving status updates for the device so it may not reflect the current state.
What is your eisy firmware?  If it is less than 5.8.3 please upgrade as there issues with remote connections on some previous versions.

Yes, If it is not 5.8.3 try upgrading first as there was an issue with remote connections in earlier versions. 

Thanks but I do have one. The issue is time as the flex device I have is connected to a serial cable and would take time to reset then reconfigure for serial connections after testing.
I the new version does not work please attach the Node Server's Log.

Please test the following to help narrow the issue.
Is this only favorites or Home Tab also?
If Both:
Does the Admin Console show the variable update if it value is change from UDM?
If it does:
With Favorites open showing the variable(s), does UDM show variable update if value is changed from the Admin Console?

Not currently.  As an alternative you could send yourself a notification if the garage door is left open for some time after you leave the geofence. Although It would require opening the app to close the door.

Issue found and corrected.  This may require delete all notifications as some users had duplicates.

Try factory resetting the bulb from the hue app first.

I've used OpenSprinkler for years, and am the author of the same Plugin. OpenSprinkler works great for the most part, and much better than non-connected controller.  It has fallen off the WiFi network a few times in the last 5 years (like many WiFi devices) but the programs are local so they still run, just needed to restart and it would reconnect. So I would recommend getting the ethernet adapter if that is an option in the controllers location. 
There are no "hacks" needed to connect to eisy and no cloud service.  eisy will act as the remote access so no need to open/forward ports or have a static IP or Dynamic DNS service.

Thanks for the report, I'm building 1.1.60 now, so just need to await Apple's processing/approval.
Issue caused by architecture changes.  A display node is now a group of nodes, although only one is shown to the user in the Favorites Editor.

Try reboot eisy, then synchronize UDM.

It can be a program, but be sure the "Command" is executing the correct command. Commands are Run IF, Run Then, Run Else, and Enable (Enable enables or disables a program, it does not run the program).
However if using the occupancy Node Server UD Mobile should update the node see https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server
Likely a programing issue. I would remove all variables and use the Occupancy Node as the trigger, see link above.

It is likely an invalid URL, be sure is starts with "https" and ends with "/desc".  Local connection can also be used with the http:<ipAddress>:8080/desc where IP Address is replaced with the units local IP Address (i.e. something like 192.168.1.65).

If a device is not writable then eisy cannot communicate with the device, this can affect any scenes with the device, so likely all related.
Try air gapping the device (pulling tab out until it stays) waiting some time then reinserting the tab.  Or factory reset the device.

Some of the Favorite Types require that the Display Status is linked to a command, i.e. toggle needs to know status to send the opposite command.
Command Type doesn't require a Display Node or Display Status.  If need the Display Node Can be removed by clicking Display Node then pressing delete (top right) on the Node Selection Dialog.

Thanks, please try upgrading UD Mobile to version 1.1.54 which should fix the Firebase dependency crash.  Version 1.1.54 was approved for production release this morning and beta yesterday.

The latest version of PG3 added a permission for apps which access eisy which may be related.  Is this check box available on enabled in the Node Server's configuration on web?   

Both items are on our list in one way or another, although not sure on timeframe.  

In short this is an insteon limitation with non-load bearing KPL Buttons. See Known issues: https://wiki.universal-devices.com/UD_Mobile#Scene_Estimated_Status . I updated Known Issues, but this issue has been discussed at length in the forum, so a search may shed light on some more detail.
Not Possible, the only way this would happen is if you turn the Scene off/on not the Dimming Device...the scene cannot be dimmed to a percentage from the admin console.  Even if using the "DIM" button a non-load bearing KPL Button will not turn off.
It has always been possible to control a physical device outside of a scene. For example KPL buttons and fanlink commands (low,med.high,off), would be close to impossible.

Tapping the indicator (triangle) next to the command parameter name (i.e. Group, Sound, Content) changes the selection from predefined values to variables.  This is how all programs behave and allows for saving a status to a variable then sending that status as a command parameter.   This works with integer variables as all Status and Command values are static and enumerated at a lower level.

On our list, but we don't have a time frame.
Also see the following for limitations:
 

Changed 100 to 200 on Wiki.    Too many false exits with 100 meters, although it may need to be much greater depending on location to avoid false exits.

Should be live now. 
Issued caused caused a race condition when  returning from backup dialog (System file selector) which briefly restarted subscription (value population). This caused removal the newly populated values along with removal of unused values.