Javi

There was an issue with the version number causing issues with the license record in the past, which could be related. Please open a ticket and include your system's UUID so we can check the license record.

Sounds like a bug. Please send me a Private Message with a copy of the UD Mobile backup file or Open a ticket with and attach a Zipped copy of the UD Mobile backup file. Also note that if you have any advanced icon configurations they have a higher priority to Favorites Icons, so Advanced icons must be deleted.

Thanks for the feedback. I think it may be more compatible for all thermostats to implemented this request as a separate view (thermostat #2 ?) in the future. There are too many inconsistencies in Node Servers to automatically implement as some Node Servers do not map the Current Modes correctly, and some thermostats do not have a single commands for setpoint up/down. To be sure I understand, you would like both heat and cool setpoints to move together?

As @DennisC suggests, use Favorite of type command. Similar to the following although in this case it will not be a program.....unless you want custom toggle capability. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

Please open a ticket and include your system's UUID so that we can do a remote diagnostic. I'll add you UUID to our diagnostic portal then give you instructions to approve diagnostic request.

The log is from PG3, a 403 is usually a credential error. Please first try to login to portal. From the PG3 Home Page got to System > Switch Portal Profile. Then login to your Portal Account. If that does not work, then try to upgrade system firmware. Then try to login to Portal.

Set the enter/exit commands in UD Mobile Geofencing to the occupancy 2.0 Node Server. Discussed here:

Does this happen after clicking Admin Tab > Plugins or only when clicking a Node Server from the list?

Great Currently not possible. Folders do allow display Nodes which can show status and sometimes execute a command when the top of the tile is pressed, however the command must be tied to the status value for this to work. Commands on folders are not currently exposed to users.

Assuming iOS this is Apple's Documentation https://developer.apple.com/library/archive/documentation/2DDrawing/Conceptual/DrawingPrintingiOS/LoadingImages/LoadingImages.html#//apple_ref/doc/uid/TP40010156-CH17-SW7 Can you provide a URL which does not work?

Beta 1.1.30 Added custom thermostat view. During testing the view must be set manually, in the future this may be done automatically assuming the node server conforms to Thermostat. Enable the custom thermostat view from the Node's Dashboard (the view with all node's status and command), select setting (gear icon at top, same location as image below), select Dashboard View, select thermostat. This should work with most thermostats, Ecobee and Honeywell Node Servers appear to work, although the current status (heating/cooling/idle) on the ecobee does not appear to conform to thermostat status so icon for status may be static (non-changing).

Please follow @Jimbo.Automates instructions below first. OK. Let us work one issue at a time, solving this first issue may solve the ELK issue, so don't worry about controlling ELK in the following test. I only want to see if UD Mobile can communicate with the plugin software. From UD Mobile got to Admin Tab > Plugins. Do you get an error here? If you do dismiss the error alerts, does the app show your installed node server(s) or is there a blank screen? If there is a blank screen then UDM cannot communicate with the Plugin Software. So please first verify the eisy firmware is up to date. In UDM > Admin Tab > Firmware select update (or upgrade) if available, if not select "Force Upgrade" then wait for the upgrade to complete. After firmware upgrade is complete you may get a notification asking to reboot, if you don't get a reboot notification please reboot anyway after about 5 minutes of firmware update completion. Reboot from UDM > Admin Tab > Reboot. After reboot please try Admin Tab > Plugins again. If you get an error please post a screenshot.

Currently the log/error-log are not available from UD Mobile. Both are available from ISY Portal without using Admin Console. my.isy.io > Select Tool (next to system UUID) > Logs

Thanks. Does the app appear to work as normal after you dismiss the error messages?

Hi All, The UDM is available for M series Macs in the app store. Currently no plans on supporting UDM on older Macs, too much work for our small company. AC will continue to work with all Macs. UDM is available in the Amazon App store (Android). Most newer windows 11 PCs support Windows Subsystem for Android which is automatically configured if the user downloads the Amazon App store from the Windows Store. However I have not had time to test/enable the App for Desktop. This is high on my list, alas is not completed. Currently no plans on supporting UDM on Windows outside of Windows Subsystem for Android. AC will continue to work with all PCs. The Android and iOS apps are native to their respective platform. This will allow us to customize the views for larger screens, i.e. desktops, at some point. While native apps will work well to accommodate larger screens in the same code base it also created an issue where the databases backups for each platform diverged slightly. So, currently UDM backups from different platform (iOS/Android) will not work on the other, this only affects favorites. I hope to get the database back in line, but I don't have a time frame. UDM has most of the most used AC functions. UDM also supports all nodes (specifically node servers), status, and commands. To ensure UDM supports all nodes/status/commands the initial focus was function over form so the app is not a beautiful as some of our competition. We are currently working on beautifying the app. While UDM supports many AC functions, the AC will still be needed in some situations for the foreseeable future.

Is this Android or iOS? Does this issue persist? If I recall correctly sometimes Android will display "Client is null" error in the Plugins (PG3) section after an unexpected disconnect, but will then start working shortly after.

Thanks, If I have not already responded to the ticket please post the ticket number.

@sumguy, very sorry for the trouble. We have a few reports of entries and exits happening at the same time. Some of these are due to iOS blocking network, which will be logged in Geofencing Logs as a timeout when iOS allows the app to access network again. We added a hard timeout for these network calls to prevent the request if the network is blocked. However the hard timeout was missing for credential refresh, which should be fixed in 1.1.29. Although it is very possible this is not the issue as is the case with the OP's logs. @tmorse305, The logs do not appear to show any issues with the processing for commands mentioned above. In this case it appears iOS notified the app of both entry and exit at about the same time. There is not much we can do about the timing in this situation, however It is possible the app logged these out of order due to threading. Version 1.1.30 of UD Mobile will lock the thread to try to prevent entry exits becoming out of order if triggered at about the same time.

The node server is getting terminated (Disconnected), and hopefully restarted (Connected) automatically. A good place to look for the an error is the Node Server's log. This may also happen for a short period after firmware upgrade, node server upgrade/install/uninstall or reboot. Being as this is not related to UD Mobile, @Geddy can we move this to PG3 or Sensibo subforum.

I think I have seen a similar issue. The app does not "store" the fence crossing, iOS is pausing network connectivity. The latest version of UD Mobile adds logs to assist with isolating these issue so that we can report these issues to Apple. There was an issue with the last few versions of UD Mobile on iOS which caused background geofencing to be inconsistent which may have caused your issues. Apple also has a history of breaking Geofencing with iOS upgrades, iOS was updated a couple of weeks ago. This could be related to the version (APIs) the apps target or the iOS firmware running on your phone. It is also possible (as evident from the last few versions) that we have an error in the app. We would like this to run as smooth as possible, alas for some users it does not appear this is happening. In order to find issues in UD Mobile or allow us to have enough data to report iOS issues to Apple we need logs. If interested in helping us please follow the recommendations in my previous post then send us the backup (log) file.

Try replacing https with http, http://192.168.1.107:3000, to remove browser security error for local connection

Thanks for opening a new topic. The last few versions of UDM for iOS had Geofencing issues for some users, version 1.1.27 was released Friday Night. This could be the cause of any issues before UD Mobile was updated. iOS automatic app updates usually occur between 0-3 days after release. In the previous post it shows a fence at 100m, please try the smallest fence at 500m, to see if false/entry exist persists. If false entry/exit persists we can look at the logs, if it does not then try slightly decreasing radius until the issue returns. This will show the minimum fence required in your area. Fence accuracy depends on many factors such as cell-tower/wifi density, elevation, and obstructions. Some locations may have accurate readings at 200m and others could be 1000m. My personal experience in a density populated area, 200m works well except in my basement. When my phone is in the basement (obstruction) I will get false entry/exist for anything less than ~1mi. If an entry/exit is missed again please check the logs (Setting-Tab > Geofence > Document Icon at the top) after 1 hour, it is very possible an error is logged. If the error is not self explanatory please send me a Private Message or open a Ticket and attach a copy of the UDM backup file and we can review the logs. Note that attachments to tickets require file to be zipped. Unfortunately iOS does not send UDM WiFi status and UDM cannot request WiFi information when the app is in the background/suspended/not-started. Apple also denied our request to run processes in the background related to Geofencing altogether and we have no other reasons to run background processes. So, unless Apple changes their policies, UDM cannot use WiFi as a trigger or request location itself as UDM does not receive location updates unless iOS notifies UDM of a fence crossing.

Hi @EJones01, I removed your backups and images as they contain sensitive data. Please send to me via Private Message or open a ticket. Backup must be zipped if attaching to ticket.

By default UD Mobile does not request program status at startup. Change this behavior in Settings Tab > Systems > Your System > Program and Variable Settings.

Reboot Polisy