Javi

I think the use case is very dependent on your connected equipment and number/age of occupants at a location. If occupancy is already established by a security system this could trigger notification if a program determines all occupants have left the neighborhood and the system is not armed. For users without another occupancy trigger this could be used to turn off/lower energy consuming appliances such a lights, thermostats, and water features or verify entry points such as garage doors are closed.

Hi @ctviggen1, With regards to instructions they say install UD Mobile then "Let UD Mobile guide you the rest of the way". UD Mobile will guide you through scanning, cable installation, Insteon Modem Installation, and/or Z-Wave connection. I understand your frustration, however the instructions were not followed. We are here to help so please let us know where in the app you encounter "Could not match section", and if you are using Android or iOS? This is likely an app bug which may not have been encountered by testers as we are outside of normal onboarding.

This is on our list for UDM. The user code changes do no use the standard command structure so it is a separate implementation.

I think this is the biggest issue, users try to use this to determine when they are at a location instead of in the neighborhood. The battery comment was regarding Android which has individual settings for global an app battery usage. Global settings may prevent location triggers, app settings will prevent network communication even if triggered. So many permissions and settings need to be changed on android and some MFG may not honor the OS level settings.

Thanks @Geddy removed status until geofence is crossed. Duplication of geofence when editing region fixed in next update.

Maybe after some other higher priority items. I've played with these in the past with mixed results and all the beacons untimely ended up in a box somewhere due to the inconsistencies.

Hi @apostolakisl, It is only on iOS currently but will be the next on our feature implementation on Android. With that said, Geofencing on Android is very dependent on the MFG and battery conservation settings and may not work well for all users. Geofence regions on Android need large minimum areas to be accurate. Somewhere between 200-1000 meters which is greater than the minimum area most people want. The lower end requires that your device is already requesting location updates (i.e. navigation) or the app is requesting location updates frequently (similar to having navigation running).

Hi @oskrypuch, Currently the app has edit locks but not a global setting to lock the app. This allows admin to hide devices/folders which they do not want others to access then locking edits so they cannot be unhidden. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Edit_Locks Pin has been requested before, however in my opinion it adds more complexity and little security. Most mobile devices already have a pin and/or biometric locks, so if somebody has access to your device then they likely already have your pin. Depending on your platform there are other ways to lock apps, there are app on Android dedicated to this purpose. On iOS I believe the Screen Time app can do this if you set the daily limit to 0. I will add this to our list, but the priority will be very low compared to other features of higher priority.

Hi @ctviggen1, The error you are getting because the system has not been approved for remote connections. Go to the Admin Console > Configuration > Portals to approve remote access. This is a security to ensure nobody other than you can access your system. With regards to the QR Code, you can generate one online using the instructions linked below. However it is not necessary, simply select Polisy as the system type and the app will not prompt for QR Code. Using this method you will need to manually select, or enter, the system as the App's System Finder has no way of knowing if a system found is the intended system. The QR Code gives the app the UUID so it compare found systems to the scanned UUID. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Damaged_QR_Code

Thanks @Geddy, I will try to replicate.

Thanks. I seen this once during development but could not replicate. If I recall correctly my test was similar to yours where after it happen once then not happen again. I'll check from a fresh install on Monday.

Hi @sjenkins, Yes, UD Mobile's Geofencing will issue direct commands to the System without needing to setup the Occupancy Node Server. I think the main reason the Occupancy Node Server was created was to work around Authentication, such as storing your Portal credentials in plain text in a Geofencing app. UD Mobile uses oAuth and does not store your Portal Credentials, so the app should refresh auth tokens if needed before sending the specified commands. The app will also send commands to local connections if they are available. As for deleting your other geofences, I would wait until we are confident UD Mobile's geofences are as accurate as the other applications. I would be great for testers to compare UD Mobile against their existing solution to verify UD Mobile works as intended. Yes, if you want status this would require setting a system variable. If you do not need status, then UD Mobile can issue direct commands to a device, variable, network-resource and/or program. Similar to Favorite Commands, UD Mobile's Geofence Enter/Exit actions can execute multiple commands. While I don't have plans to create a Node Server for Geofencing due to time constraints, I can foresee someone creating a Node Server which handles the complex logic for things like multiple users at a single location which can be triggered by UD Mobile. UD Mobile's backup, which includes geofence data, was built to handle multiple users who have different geofence commands enabled as long as the geofence names are different. Upon backup import the app should keep existing geofences enabled, so when importing onto another family member's device only previously enabled geofences should remain enabled even if these settings were different on the device which exported the backup.

There is no way to switch between system in UD Mobile, all systems work simultaneously. To achieve something similar create a favorite of type Folder for each system, then place all favorites into the correct folder. If the favorites are already created then just move into the new folder.

Beta Version 1.0.22 Added Beta Geofencing. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Geofencing

With UD Mobile there are public get repos with issues. I though I added this issue, but it was not listed. Added issue https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/43

Hi @gregkinney, Issue is known for some newer Android version, caused by intent crash in PAHO MQTT Library. I'll try to get it fixed in the next update. @brians, Currently only in Android and must be on local network. We are working a PG3 portal integration so both remote and local connections can be established. This will change MQTT topics at which point the Android integration will need to be modified. So the local only version will not be ported to iOS although will likely be first in new integration.

Please try again now.

We are looking into the issue.

Great, port is not required for ISY994 if the default of 80 is not changed.

Sounds like the SD card is on the fritz. How old is the system?

Assuming ISY finder found the system and you cannot login, try using the default user name and password of "admin".

Is this the Address the App found (search icon next to the Local IP Address) or was it manually entered? If the app found the system with the search icon, then setup an IP Reservation in you router so the address does not change. If the app did not find the system, then the app cannot see your system, check if you can connect to the system from a browser using the same IP Address.

Hi @Charles Hall, I believe I found the issue and have uploaded Android version 1.0.26 to the Google Play Store. It may be a few hours until available to users. I believe this will fix the crash, although you may still need to add your portal account in settings if the same error is shown.

Hi @Charles Hall, At what point does the app crash after reinstallation? Portal Login, Synchronization, backup import?

What is the hardware and firmware? Did this start after a firmware upgrade?