mmb Posted Friday at 02:44 PM Posted Friday at 02:44 PM (edited) @Javi I recently purchased a new iPhone and, as usual, used Apple’s pairing/data transfer process to set it up. While everything transferred smoothly overall, UDMobile was the one exception. After the transfer completed and I launched UDMobile, I was prompted with two options: “Migrate” or “New Controller.” I entered the new controller IP, then had to manually sync and restore my Favorites. This was further complicated by the fact that my backup had been created under an older Polisy and didn’t reflect the upgrade to a new EISY — something I’d forgotten about. My expectation was that UDMobile’s data would migrate seamlessly along with my other apps, so this came as an unexpected surprise. Do you have any idea why this might have happened? Edited Friday at 02:47 PM by mmb Quote
atmarosi Posted Friday at 04:31 PM Posted Friday at 04:31 PM You have to 'backup' aka export the config; and then restore it on the new device. They don't back up to iCloud natively like others are doing. 1 Quote
mmb Posted Friday at 07:18 PM Author Posted Friday at 07:18 PM (edited) 6 hours ago, atmarosi said: You have to 'backup' aka export the config; and then restore it on the new device. They don't back up to iCloud natively like others are doing. Thanks, that's what I ended up doing. Another thought, when you pair the two iPhones aren't they doing a iPhone to iPhone data transfer? Edited Friday at 10:45 PM by mmb Quote
Javi Posted 1 hour ago Posted 1 hour ago Saving to the controller is on our list. UDM was built starting with ISY994 which could not handle saving the UDM configuration. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.