Javi

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?

Hi @fustesj99, Please go to Settings-Tab > Systems > Your System Name. When this screen is opened it will run diagnostic on portal connections. Do you get an error? If the app prompts to synchronized please cancel then press the Test Remote Connection button at the bottom of Remote Connection Settings. Do you get an error here?

The THEN section did not run if the Status is false, the else section ran. Think of last run as last evaluated.

Version 1.0.23 Added Program Schedules Quick Look on Home Tab. Added Linked Programs from Node's Dashboard. Quick Look: See all programs with schedules from the Quick Look > Schedules section. Quick Look section is on the same Home Screen as "Devices and Scenes" Folder. While Quick Look > Schedules should locate all programs with Schedules it is possible the app misses some with conditions or actions not yet mapped in UD Mobile. Linked Programs: See all programs linked to a node from the Node's Dashboard (Screen which shows all status and command values for a node)> Settings (Top) > Linked Programs. While Linked Programs should locate all program where the node is in the Status, Control, or Command conditions/actions it is possible the app misses some with conditions/actions not yet mapped in UD Mobile.

Not out of the box, but the eISYIR Node Server support IR with Flirc IR dongle connected to a USB port on eisy.

I run something similar for a small home and have for years. Some here may say this is not a good idea, but as long as you understand the limitations it may be better than no monitoring. I think most here would recommend ELK as it integrates with ISY and will not have these limitations. Some of the things I have encountered over the years are below. Keypads: Insteon keypads may not work to enter a code, while I've seen others do this it never worked well in my tests due to how the insteon protocol communicates. I found using keypad door locks work better. There are still a few times a year where the keypad doesn't communicate with ISY and the alarm would trigger. Unlocking the door again usually succeeds but having a button to disarm on your phone will save a lot of headaches. Battery backup: All automation equipment and networking equipment need to be on a battery backup. Error checking: While it is easy to write programs for arm/disarm/ect. It is much more difficult to have good error checking and display errors to users. Does the system still arm when a window is open? How do you show the user this error? How do you override this single sensor if a battery is dead or device is malfunctioning? Will writing all of these programs/variables/notifications save you more money/time than purchasing an Elk? Other users: Don't expect anyone outside of the house to understand the system and it's quirks. Your sitter/parents/children/neighbor/friends will encounter issues and will be irritated/confused when the alarm is triggered without a standard security system keypad there is no easy way for them to see or correct the issue. Wall mounted tablet: This may allow you to mitigate some of the issues above but has issues also. I built an Android app a while back to use the ISY as a security system. It worked well until the tablets battery starts to swell or needs to be reset/restarted for some other reason like it's not connecting to Wi-Fi. This could be the perfect solution if you purchase hardware made for this type of application....but would likely cost more than a all equipment needed for an Elk installation.

I think I may have used this language when describing how UD Mobile implements nodes. It was along the lines of, if Elk Module where to be implemented into UD Mobile It would be similar to a faux Node Server. I said this as the app implements Programs and variable as faux Node Servers with respect to how Node Server developers define status and controls using Nodes Server definition files. I don't think, at this point, a faux Node Server will be built as the ELK Node Server already does the same or better and the ELK Module doesn't exist on eisy. If using ISY994 you could always set variables for status and use Programs to control the ELK module. Using custom mappings you will allow you rename the variables status and program command using UD Mobile Favorites.

If not updating from UD Mobile wait 30 min. UD Mobile will check the upgrade status as soon as the system comes back online, as the system may be online but upgrade not compete. UD Mobile also suggest reboot if system doesn't come back online. Alternatively you could check /desc update tag (requires previous version > 5.5.5) if system is back online to verify upgrade is completed.

This is by design. The force update will upgrade to the latest version even when not showing as available. Think of this as staged rollout, with those following the forum having the ability to jump to the top of the list with a forced upgrade. Note: this is the same as upgrade from AC.