Javi

Hi @lhranch, App Transport Security (ATS) is disabled by iOS for local loads (1), so this appears to be something out of the control of the app. My best guess is it has something to do with the private DNS causing iOS to flag the connection as not local. I do wish I had a better answer as this situation will be very difficult to debug without being on site. If your ISY has not been connected to our portal service in the past please try the free, no credit card needed trial, if you would like to verify functionality before you purchase an SSL CERT. While it is possible for the apps to disable ATS it would make all connections less secure and we would have to meet the exception requirements (2) during app review which we likely do not meet. (1) https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity/nsallowslocalnetworking " ATS doesn’t block local loads by default in newer versions of the OS" (2) https://developer.apple.com/documentation/security/preventing_insecure_network_connections#3138036 "The app must connect to a server managed by another entity that doesn’t support secure connections." Portals provided by UDI and Third parties support secure connections, and UDI controls the firmware. So, this does not apply. Apple has also mentioned this will be removed in the future. "The app must support connecting to devices that cannot be upgraded to use secure connections, and that must be accessed using public host names.". ISY firmware does support secure connections, so this exception does not apply.

Android Alpha 0.62 Rebuilt Favorites creation and edit screens to allow icon selection during creation. Rebuild icon selection with icon names. Other UI improvements and bug fixes.

Hi @Pcarp, Please send us an email and let us know which folder has the issue and attach a copy of the app backup so we can investigate. Our email is located in the app in Settings-Tab>About>Email-Support. Backup can be created from Settings-Tab>Backup. Backup copies do not contain credentials as they are stored in the device keystore. Thanks

Hi @DPerry, We are still working on setup instructions for existing ISY's, there is automatic discovery, setup, and ISY Portal account creation for new ISY's. Minimum firmware is 5.0.16. Local Connections on UD Mobile should work in any situation, including with the MobiLinc Portal installed. Local connection settings are below Remote Connection settings in Advanced. If you are only using on the local network you can select "Only use Local Connection" to avoid wifi checks. The search icon should find you ISY. Remote requirements are in the link you posted. The ISY Portal has Smart speaker, IFTTT integrations, and Remote Connection capabilities. ISY Portal and UD Mobile work together and will have a greater integration in the future, however ISY Portal is not and will not be a requirement. See here for more information https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal:_Integration_with_Amazon_Echo.2FGoogle_Home.2FIFTTT

Hi @auger66, Thanks for verifying. If it is encountered again please create a backup and notify support (Settings>About>Email Support).

Hi @lhranch, It could be helpful if you can capture your phones network this may require routing your phones connection through the device running WireShark (MitM). Below is a sample of a successful rest/time request for the local network 192.168.1.9 is the ISY. This is local network search (M-SEARCH): I'll try to get version 0.2.9 pushed to Alpha testing Monday or Tuesday to remove the hard coded "code=8" error, this should show the actual failure cause. Based on our conversation I gather the remote connection is trying to connect then failing because of the CERT (immediate code=8). The local connection appears to time out (delayed code=8). If you would like to join our alpha test group and check if the error messages on version 0.2.9 please follow instructions here https://testflight.apple.com/join/xHtzI5R3

Thanks for verifying. At this point I am not sure of the cause, the app should function similar to a browser for the rest/time (test connection) call as it is a high level call using iOS defaults (HTTP). I'll ask around to see if anyone else has insight into the issue. ISY Subscription sockets (TCP) are managed by the app (low level), however these are not started until after the application has synchronized with the ISY.

Great! I am wondering if the private DNS is not allowing a direct local connection and instead using the https settings. I based on a previous comment made about your router's connection warning when you were away from home and I assume you MobiLinc connection does not specify port 80. So I do have a few additional questions. Was a security warning presented in the browser? Was the numeric local IP Address used for this connection and did it specify port "80" ?

Looked at the code base and "Code 8" was hard coded at some point for some errors...I'm sure I had a good reason at the time ?‍♂️. Version 0.2.9 will have better descriptions of the errors, although it will be at least a week before it is in production. I ran some additional tests and can only produce a delayed (10-30 sec) "Connecting to Network...." when the IP Address in not assigned (time out), attempting to connect to any device on the network which does not accept requests at the specified port or contains invalid credentials causes the app to immediately fail and return. DNS lookup is provided by the OS, so we can start at this point. When using the "Test System on Local Network" button the app sends a rest request to the ISY (rest/time) to verify a valid response. Can you make a request from your phones browser to verify the iOS can communicate with the ISY? This should also prompt for the local credentials, if there is not prompt for local credentials please use an incognito tab so we can also verify credentials. http://192.168.1.9:80/rest/time Where 192.168.1.9 is your local ip address and 80 is the port. In the example above the exact address entered into the app is "http://192.168.1.9", port would be empty or set at "80". Thanks

Hi @lhranch, I apologise for the setup difficulties and thank you for verifying the local connection error. It does appear your device has the required local connection permission. I'll have research this issue to see if we can find a solution as I am not able to reproduce the issue. At this point it looks as if we will need to verify connections manually. Can you verify Admin-Console>Configuration>System>Network-Setting "Http Port" and "IP Address" match, IP Address must me prefixed with "http://". Just for this test select "Only Use Local Connection" to bypass System Network Relations checks. After credentials are entered what error do you recieve when pressing "Test System On Local network". I do understand if you do not want to pursue the app due to the CERT requirement, we do try to provide all available options to users. ISY Portal does not require a Static public IP Address or Port forwarding. Static IP addresses are usually a premium service from ISPs or require a service (DYN DNS) to monitor your changing IP Address. The cost for either of these services is usually more than ISY Portal (≈$11 yr) not to mention the CERT or security implications by opening a port on the router. Most mid/high grade routers have the ability to run a VPN server which will remove the CERT requirement as the app will use HTTP. This still requires the Static IP Address or dynamic ip monitoring. This will allow connection to local devices without opening ports.

Hi @auger66, Thanks for the details, there does appear to be a bug. I have a few Insteon leak sensors and all report there status in the iOS app, so I can not replicate the issue. Can you verify you have tried performing a synchronization again? If the issue is not resolved by a new synchronization and you have a portal account we can run a remote diagnostic, send me a PM with your UUID and I will provide additional instructions.

Hi @auger66, All Nodes supported by the ISY are supported by UD Mobile so there is no need to setup a variable. Did you get errors during sync? If you did not get sync errors: Does the Admin Console also has a status for the device? If the Admin Console does have a status for the device please try to synchronize the app again, although rare sometimes data is dropped during sync. If the Admin Console does not have a status for the device please press the link button on the Device to trigger a status, this is needed if the ISY is rebooted or power cycled. If the issue persists please open a ticket. If the device does show a status and you are referring to the toggle indicator (blue dot), this is only available for devices which have a status (ST) value and have on (DON) and off (DOF) controls. If this is a favorite; status (ST) must be the selected value when creating the Favorite.

Hi @lhranch, The app will try to connect to a remote ISY for a security handshake. If you do not have a Trusted CA Signed SSL Certificate the SSL handshake fails and the app throws an error. We will try to get a better error message for this scenario in a future version.

Hi @lhranch, If you have "Only use local connection" checked (as evident from the red background on remote connection) the app is instructed to only use the local connection. This setting is for users who do not want to use remote connections or VPN. Can you post a screenshot of the error you are getting for the local connection search when you are on the same local network as the ISY?

Hi @lhranch, The app requires an iOS permission, "Local Network", to search for a Device on a local network, this is only needed to search for the ISY and not for direct local connections. A dialog should have been presented by iOS asking for permission, if permission was denied or dismissed iOS will not show it again and it must be granted from iOS settings. The app is not notified when the permission is accepted or denied, so if permission is granted during a search please use the Try Again button. If permission is denied all M-SEARCH request fail immediately, if the app has permission the search should continue until canceled or an ISY is found. There are issues on Android with M-SEARCH which can persist until a device reboot, I have not encountered the same on iOS but it may be worth trying.

Hi @lhranch, This is odd, can you verify the Http Port in Admin-Console > Configuration >System? Was the local IP Address found using the search icon?

Hi @lhranch, Local and remote connections are independent of one another but can be combined in the app as local connections will usually be a few seconds faster getting subscription data (node values) on initial startup. There is one thing that may be different in remote connections with UD Mobile compared to third party apps as we are a first party author. Our apps require a Trusted CA Signed SSL Certificate for direct HTTPS connections. Apple And Google have warned developers that bypassing SSL Security may lead to removal from their respective App Stores and may not be supported at all in the future. Apple set a timeline for this but is overdue in removing a developers ability to bypass SSL and states this option will be removed in the future and currently should only be used by third party developers whom do not control a server or device to which the app connects. Being as we are the first party this exception does not apply to us. Even if we were to find a way to to meet this requirement and bypass SSL it may be gone at any point in the future thus creating more support issues for us. Remote connection on UD Mobile can be achieved in 3 scenarios. First is our managed method using ISY Portal. ISY Portal has competitive prices of $23 for the first 2 years and renewals cost of $20 for two years. If your ISY has not been associated with the ISY Portal in the past we offer a 30 day free trial. Second is an unmanaged direct connection. The unmanaged method requires a Trusted CA Signed SSL Certificate. The Trusted SSL CERT is required for reasons stated in the following post (https://forum.universal-devices.com/topic/32627-trouble-with-initial-setup-error-domain-code8-null/?do=findComment&comment=311979 ). Instructions on adding a CERT to your ISY can be found here: https://www.universal-devices.com/docs/production/ISY994 Series Network Security Guide.pdf . There are methods to add a Self Signed CERT to the Trusted Key Store on Android, however it is beyond the scope of our support and may require root on some devices. Finally a local connection can be established on a remote network if running a VPN Server on the same local network as the ISY. To use this method select "Only use Local Connection" in the local connection settings. Setting this option will instruct the App to ignore remote connection settings and only use the local network. Please do let me know if this answers your questions or if you need additional information.

Hi @ISY4Me, I'm not sure I understand, I see no way to disable a Scene. Some additional information: The Scene Estimated Status Calculation is a feature of UD Mobile and not the ISY. This may not work in every situation and/or may require nodes to be excluded from calculation in order to be a useful feature, this is true for some battery powered devices or controllers which are not responders. If you would like to remove an item from calculation press the calculator icon when the scene is opened in UD Mobile. Excluding all items from calculation will remove the calculated status and the toggle indicator. The app will have to be closed then reopened if all items are excluded as status is only updated when a new value is posted, closing the app will clear all values.

Thanks Everyone, This is a bug in the iOS version will be fixed in 0.2.9. Internal Commit: d78d2f0 Fixed hard coded column names in Node Dashboard Query

Hi @stevesreed, The status can be whatever you would like it to be. Currently there is no way to edit the current favorite but you could delete it and add a new one. During selection of the new favorite select whichever status value you would like to see on the Favorites page.

Please do let us know if this resolves the issue. I'm adding additional information below in the event another user has the same issue. We recommend firmware updates are only done when on the same network as the ISY and connected locally. Firmware updates from a remote connection may lead to packet drop during firmware installation, which may cause this issue.

Hi @PAstrachan, The Insteon files are missing, so the ISY firmware will need to be reinstalled.

Hi @PAstrachan, My best guess at this point is the firmware installation did not complete. If you are comfortable with making a browser request to verify please do the following, if not please open a ticket. We need to verify the firmware upgrade installed all files. To do this make the following request in a web browser with <ipAddress> replaced by the IP Address of your ISY. http://<ipAddress>/rest/profiles/family/1/files This should result in something like the following. If file names are missing firmware installation was incomplete, please try the installation again. <profiles> <profile family="1" id="1"> <files dir="EDITOR"> <file name="I_EDIT.XML"/> </files> <files dir="EMAP"> <file name="I_EMAP.XML"/> </files> <files dir="LINKDEF"> <file name="I_LDEFS.XML"/> </files> <files dir="NLS"> <file name="EN_US.TXT"/> </files> <files dir="NODEDEF"> <file name="I_NDEFS.XML"/> </files> </profile> </profiles>

Hi @PAstrachan, Polyglot is not required. Did you get errors when synchronizing the app? What is your firmware version?

Hi @oatflake, Please try to find the ISY with the search icon (magnifying glass) next to local IP Address as there may be an invalid character in the typed address. Note there is a bug in the current version which may require you to hit the search button a second time after you accept the iOS permission for the app to search for your ISY on the local network, this will be fixed in the next release.