Javi

Ok, So when you open the app are the status blank or incorrect? If incorrect, please run an additional test by swiping app from recent apps (remove from memory), then open again. Are the status values still incorrect?

Please try UD Mobile Android version 1.4.6 or greater when available in the play store, likely within a few days. Replaced deprecated Network Lookup. Added manual trigger buttons, similar to iOS.

If on testflight please let me know if version 1.4.4 corrects the issue. Currently still awaiting approval from apple.

This is not normal behavior, and if it has been happening for years then not related to the UDM app. Is this only some devices or device types (i.e. zwave, insteon)? Does it also happen in the Admin Console?

This is the app version, what is the eisy firmware.

We firmware release coming soon which corrects most if not all of the issues with 6.x. I don't think this is the same issue referenced above. The above issue is not status value, this appears to be devices not updating status values. What is your firmware version?

Please open a ticket and include UUID .

The event subscription (status updates) is not working, so the message is likely correct. What is your firmware?

What is your firmware. This is a bug in ISY994 firmware, which was caught in the app in a previous iteration. Although I'm not sure which firmware version it was corrected.

Please share a screenshot

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

Until fixed please click the Favorites tab even if already selected, which should load favorites.

Instance is the slot number, So Family 10 (node Server), instance 60 (slot 60).

Please synchronize.

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

Thanks for the update, I have at least one other user reporting something similar....Unless you opened a ticket last night.

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.

What firmware? This is a message sent by eisy, attached to the PG3 (Plugins) group. I thought it was removed in recent firmware 5.9? If not disabling that group should stop the notification, but also any other PG3 Started/Stopped/etc notifications.

This is a bug in UDM for Android API 35 (maybe 34 also), will be fixed in the next release I'm not sure I follow, but I think the same can be done by removing the variable and program from the equation?/ If the color is associated with the temperature in the display node the use calculation in UD Mobile. see https://wiki.universal-devices.com/UD_Mobile#Comparison i.e Something like if status >= 0 degrees set color to blue, if status is >= 55 degrees set color to green, and if status is >=75 set color to red. Where >=75 is evaluated first, 55 second, and 0 third.

No. There is a content length limit for remote connections to Plugins, which may be the cause. If you have setup local connections in UDM, try when local, may require swiping app from recents to clear cache.

These are benign errors for the user, but useful for Node Server developers. The NLS file has a "ST" definition which could not be parsed. Appears the "NAME" is missing or is something other than "NAME" https://wiki.universal-devices.com/Polisy_Developers:ISY:API:NLS:Language_Support ST-<nodedef.nls>-<st.id>-NAME GEN-<nodedef.nls>-<st.id>-NAME ST-<st.id>-NAME e.g. ST-ST-NAME = Lamp ST-MYDRAPES-ST-NAME = Drapes

Ok, the error is consistent No network access or the Android OS is not allowing UDM to access the internet. UD Mobiles target version changed in August from 34 to 35 so this may be related. Along with a deprecated network check function. Although I don't see any of these issues on my Pixel, the deprecated function may be the cause. Added to our list, but may be a couple weeks before it makes it to production. Notes: Every time UDM encounters no internet it waits 30 seconds multiplied by the number of previous checks up to 6. However it looks like there is a feature(?) in the app which cause the command to be sent even without internet after the 450000 (6 loops) is reached. Looks like it is held in the network queue until the OS gives the app internet access, when the app is opened.

What is the message in the UDM Geofence log this time around?

I use a Pixel 9 Pro on 16 also, so should be similar. You described 3 different errors which are not necessarily related. 1) there are no specified commands for this geofence trigger” > The Geofence does not have commands for the Trigger Type (Enter Exist). Maybe this was fixed when you reentered the commands? 2) No network > The app did not have access to Internet when it tried to execute a network call, then says it will reattempt in 30 seconds. 3) Reattempt after 30 seconds did not happen, but the app did reattempt after it was opened. This is either due to the app crashing in the wait period or the Android operating system stopped the app (i.e. Battery Saver). The latter seems more probable unless you received a crash message. For issues 2 & 3 sometimes the phone needs to be restarted, not sure why but has worked for other users.

Makes sense. There are 2 issues, Property Value Formatting and Missing Property Values. We are still looking into the cause of both issues. Missing Property Values has been replicated on Portal Connections when going through EisyUi***, EisyUi local, and Admin Console Local on port 8443. ***Firmware 6.x and greater use EisyUi for portal connection and the Admin Console when Local on port 8443. Local connections on UD Mobile uses port 8080 so does not use Eisy UI, same with Admin console when using port 8080. If using UD Mobile on Portal clicking into the Device Dashboard will perform a new Property Value Query. While not ideal it is the current work around until fixed.