Javi

It appears like you are looking for tabs. I've added to our list although not sure on timeframe. https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/90

Hi All, I believe we located an issue in UD Mobile. Version 1.1.25 was released to the App Store and should be live within the next 24 hours.

Please send me a PM with the app's backup and I'll take a look. Alternatively open a ticket and include a zipped copy of the app's backup.

Hi All, I'm looking into the issues, for the most part nothing in the app's Geofencing changed so it may take time to identify the cause. As far as I can tell this started happening on iOS 16.7. Please let me know you have a lower iOS firmware which may help narrow the issue.

The URLs were likely saved by the user. Finder will not find a system which is not on the network (i.e. Portal). The only way portal URLs would be populated is if the user pressed save after manually input a remote url (i.e. Portal). In this case the url is Saved not Found. The same is true if a local url was saved. If using UD Mobile you can try the app's finder to check the url. Go to Settings Tab > Systems > Your System > Local Connection Settings (expand if needed) > press the magnifying glass icon next to Local IP Address to start the finder. Note that UD Mobile only has the numerical Local IP Address, port and path need to be appended in finder, i.e. http://<ipAddress>:<port>/desc or http://192.168.1.99:8080/desc.

Let me know if the missed fences continue. I think they were being missed due to the same crash.

I believe the issue is caused by IoX Finder, not firmware. It should be safe to ignore until fixed.

All, I believe I found the root cause, 1.1.23 was accepted so should be live in production soon. Beta is still awaiting approval from Apple.

Hi @SteveBL, My apologies, I never received notifications as a crash report is not generated. iOS is terminating UDM because the cleanup process is not terminating within 5 seconds. I cannot replicate this on any of my devices. So I'm going to try a few things but can't test solution myself. Please let me know if this persist in the next version 1.1.23

Most favorites can be migrated assuming the node addresses are the same. Go to the existing system's settings from UD Mobile >Settings Tab>Systems> Your System, scroll to the bottom and click clear UUID. If you have local connection settings, set the Local IP Address for the new system. If the app did not force you to select the system from Portal correct the remote url. In Remote Connection Settings click the search icon next to the remote url and select the new system. If using a different portal account delete the portal account from remote from remote connection settings and login to the new account. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Migration

Enable in settings https://wiki.universal-devices.com/index.php?title=UD_Mobile#Program_And_Variable_Settings

Yes. Thanks.

Thanks for trying. At this point our only option is a iPhone System Diagnostic reports. Is there a Jetsam logs at about the same time as the crash Settings > Privacy > Analytics & Improvements > Analytic Data? If there is please send to me. If there is not a Jetsam log, please gather a sysdiagnose. Instructions to generate a sysdiagnose report attached. Then send to me with the exact time of the crash. sysdiagnose_Logging_Instructions.pdf

While the issue could not be replicated, I did observe memory leaks coming from the app's XML Parsers. This may be causing iOS to terminate the app when backgrounded. Let me know if the issue persists in version 1.1.22

All, I've reviewed the Apple's crash reports with user descriptions matching this issue however they are all empty and have no logs. If anyone has a system where this happens everytime, or very frequently, and is willing to allow remote diagnostic please let me know. If interested please open a ticket or send me a Private Message. Include a description on how to replicate, system UUID, and a UD Mobile Backup (Backup must be zipped to attach to ticket). I will then give instructions to approve remote diagnostic after we link to our diagnostic portal. Diagnostic approval must be done from a local connection, approvals cannot be done from Portal. Thanks

With regards to the Zigbee error. It should be removed in the next version of UDM. I see multiple reports of this crash. Will investigate today. It may be helpful, but always better if I'm told how to replicate. Some of the crash reports contain no more than the Model, Firmware, and user notes and are missing logs. I don't check Apple's reports often, unless someone says a crash report was submitted. Firebase is usually much better, although this crash is not showing in Firebase, likely because the app is backgrounded when the crash occurred.

How do you "close it"?

This should correct the issue.

Looks like a naming conflict. Version 3.2.4 was labeled as 3.2.5. This may affect the Notification Section and Firmware Sections of UDM. If you are stuck in a loop please swipe app from recents. We will try to push PG3 upgrade soon to fix.

If you have a UDM backup it can be reloaded. Then go to the system settings, login to portal prompted. Ignore/Cancel any error or synchronization messages until the items below are completed. Change the Remote URL by pressing the search icon next to the text entry box then select the new eisy (this is a list of systems from ISY Portal). Do the same for the local connection settings (this is a list of systems found on your network) if they were used in the previous installation. Finally scroll to the bottom of the page and press "Clear UUID" (this removes the UUID from memory, if not cleared synchronization will fail as the app does not want to synchronize unrelated systems). Save and synchronize system, clear any items if prompted at the end of synchronization.

Please post a screenshot of the UD Mobile error message. What is the system firmware version?

EDIT: An installation issue has been replicated.

The quoted answer was for this statement The Scene was "Controlled" not the KPLs. So if the IF Condition of the Program is looking for the KPLs to be "Controlled" then the program will not trigger. If the Program IF Condition is looking for "Status" should be triggered, assuming the condition is fulfilled.

There was no functional changes to the Node Server only version number from 2023.01.09 to 2023.1.9 as the the zeros were causing issues in PG3x parser. It should be fixed now. The IR code posted above works when tested, i.e. I see the blaster flashing. It is possible the code is incorrect if it is flashing but does not work. Were the Custom Parmas saved the code saved after it was entered?

Not yet, still on my list