Javi

Hi @chris.com, Thank you. The app is not able to get a list of files from the ISY. This is usually caused by a communication issue or incomplete firmware upgrade. Did you updated firmware sometime after the app was working correctly? To check if this is a communication issue, please reboot ISY and Mobile device then after a few minutes try synchronization again.

Hi @chris.com, Have you tried synchronizing the app with the ISY after seeing the error? Additional status mapping and validations were recently added which may have caused a new error check. Please also be sure you have the most recent version of the app.

Hi All, We have multiple reports of issues with iOS 15.2 + causing user data to be deleted. Please be sure to backup UD Mobile in case your device encounters the issue. It appears that users which experience the issue one time will experience the issue again on the same device every few days. This appears to be a bug in iOS and we are currently testing work arounds. None of our development devices are experiencing this issue. If you encounter the issue please help us by opening a ticket or commenting in our issue tracker on GitHub. https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/49 Regards, Javier Refuerzo Edit: Link to this post has been sent in push notification to all iOS users.

Hi @CLipman, Glad you are liking UD Mobile. I think you just need to turn on variable requests at startup. See Settings Tab > Systems > Your System > Advanced.

Thanks

Hi @Jimbo, I'll take a look. @inovermyhead, This appears to be unrelated to this thread. UD Mobile lost login creds somehow, it should have prompted for login, but a few of these classes were updated recently so there may be an issue. Logout of all portal accounts in the app, then login. After login then go to Systems and for each ISY reestablish the portal connection as it was removed when logged out.

Hi @Jimbo, Can you check the ISY error log to see if a new subscription ID is created during each "PyISY reconnected to the event stream." log event? Also looking for unsubscribe events.

Hi @shbatm, Thank you. Reconnect looks correct, although I do not use reconnect as mobile disconnects are mostly due to poor network conditions. I find it easier to unsubscribe when encountering network issues in case the device loses network soon after, this way no subscriptions are left hanging. @Jimbo , I have found that a good test for subscription closing is to set your heartbeat value to a low number, such as 10-15 sec. This will force a reconnect loop. Being that ISY is less powerful than Polisy, ISY may eventually throw an error but should recover quickly and allow subscriptions again in the next loop iteration. The reconnect loop should have a short delay. I have found that 3 second works well as a stress test and only throws the occasional error, shorter delay throws many errors, longer delay rarely throws an error. If ISY does not recover quickly after an error is thrown, it is very possible the program needs to unsubscribe and is creating too many new subscriptions without closing existing subscriptions.

Thanks @MrBill, A reboot would not close the subscription gracefully. If there are plenty of other subscription slots available then nobody would notice and eventually the ISY will terminate the subscription if it does not get an ACK. The problem would arise if the library loses connection or misses a heartbeat, at this point it should send unsubscribe with the subscription ID on another thread. If it does not unsubscribe and somehow gets in a loop of subscriptions without unsubscribing the subscription queue may fill causing already subscribed error. Our app was guilty of this in the early days, and days of debugging this single issue is memorable. I don't use anything with this library so I'm unsure if it is unsubscribing correctly when it loses a connection/heartbeat. The unsubscribe function is incorrect so even if the library is calling unsubscribe it is not happening.

Are any of you using software which has the PyISY library? I believe the Home Assistant Plugin and Hue emulator use this library. I have seen reports that this library was causing issues with subscriptions. I took a look last week and the unsubscribe call was incorrect, so it is possible that this library has never closed a subscription correctly. I put in a pull request, but this may not be the root cause of the issue. If anybody encounters this issue please first try disconnecting any services which use PyISY to isolate the issue. Reboot may be required if there was a subscription loop without closing gracefully for a long duration of time. Note that we are still waiting for a pull so the user which isolated PyISY as the cause can see if fixing the unsubscribe function fixed the errors.

Unfortunately the FanLink can not act as a controller as it only sends status values, not command values. If you regularly set the fan to a specific speed, consider using the single scene for on/off voice commands. This would keep all KPLs in sync. If your speed preference changes by time of day/year a program can alter the Scene links to set the fan to another level for the ON command. I think programs would be the only other route. Adding 4 scenes (High/Med/Low/Off) with only the KPLs as a responders and without the FanLink, will allow programs to monitor the FanLink and send the Scene On Command to adjust the kpl buttons. Just set the Scene links for each scene to turn on/off each KPL depending on FL value.

All, Please ignore users if you do not agree with them and refrain from posting this type of content as it is no help to anyone.

Hi @mbking, It looks like the search button still points to the old BASIC auth functions, so this is a bug as all portal connections are now oAuth. As for getting the Remote URL, a list of your ISY Linked to ISY Portal should popup after selecting your ISY Portal account., so there must have been an error, dialog canceled, or portal creation canceled. Please click the delete icon next to the Portal window above the URL search, this will not delete the portal just remove the link for the system in app. Now click "Add" in the ISY Portal window and select your Portal account. Note that the app supports multiple Portal accounts so if a Portal account was already entered into the app it should populate as a list item. If this is on a different Portal account select "Add New Portal". Then the list of available ISYs should be shown. After clicking you ISY the remote url should be automatically populated.

Hi @Gunn, Thank you, fixed punctuation. If you would like an off button to show OFF STATUS there are a few ways to accomplish this, although I think it would cause too much confusion if added to our wiki. Below is one example, I'm sure others here will have different/better methods which vary in difficulty. Add the off keypad button to another scene as a responder. Due to insteon limitations non-load keypad buttons can only be controlled by the ISY when they are in a scene. Now setup a program IF to monitor the STATUS of the FAN MOTOR when OFF. In the THEN part of the program turn ON the scene with only the off button. Note that a second or two delay may be needed ahead of the ON command, this will account for brief STATUS off values. The ISY will stop running the program if the status changes in this brief delay.

Hi @Gunn, You are correct that the instructions should be updated, these instructions are for firmware versions less than 5.X. Although the issues your having may be related to your other post were old Insteon links remain from manual or Insteon Hub Scenes. For 5.X firmware only one Scene needs to be created and links should be adjusted. See the highlighted scene member from the folder structure for link adjustments The Scene Links (all buttons off, except High button. Fan High), This setup will allow UD Mobile to control the fan scene with toggle (high/off) and keep buttons synchronized. Note that Scene Member calculation for UD Mobile should be disabled for all keypad buttons: High Links (all buttons off, except High button. Fan High): Med Links (all buttons off, except Med button. Fan Med): Low Links (all buttons off, except Low button. Fan Low): Edit: I've updated our wiki with 5.x instructions https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

Hi @mbking, Thank you! We have no plans to remove manual HEX input, color picker would be in addition to manual input.

Hi @stimpy2k, Please first try upgrading to the latest version of UDMobile (version 0.117 as of 12-19-2021) and running synchronization. The original poster has a failed firmware installation with missing node definition which required reinstallation of firmware. This issue may be caused by remote firmware installations so we encourage all users to install firmware from a local connection and not from ISY Portal or any other remote connection. Firmware reinstallation is done in the same way as a firmware upgrade, and as always please backup your system before attempting upgrade. If UD Mobile upgrade and synchronization does not fix the issue we can run a remote diagnostic or you can run self diagnostic with instructions below. Please open a ticket for remote diagnostic. Remote diagnostic requires ISY Portal. To run self diagnostic request the Z-Wave Editor file from the ISY with the following url in a browser. Replace ipAddress with the IP Address of your ISY. http://ipAddress/rest/profiles/family/4/profile/1/download/EDITOR/EDITORS.XML Now search the page for "ZW_UNLOCK_NT". The page may contain something similar like "ZW_UNLOCK" but it is not the same editor. If "ZW_UNLOCK_NT" is not present firmware will need to be reinstalled. Tags (for future form searches): Could not get Editor Object , Cursor is empty

iOS Beta 0.6.0 Added Global User Preference for Favorites-Tab/Home-Tab/Default launch types due to Apple's limited widget sizes. Synchronization required to obtain missing Editors listed below. Added encoded editor parsing and insertion for Node Def Status Editors. Fixed Deadbolt UOM Action human readable values. Fixed NLS for encoded editors with underscore in NLS definition. Other bug fixes. Android Production 0.117 Synchronization required to obtain missing Editors listed below. Added encoded editor parsing and insertion for Node Def Status Editors. Fixed Deadbolt UOM Action human readable values. Fixed NLS for encoded editors with underscore in NLS definition. Other bug fixes.

On most Android devices, including Google's Pixel, notifications only show as a dot, so the number must be an addition by the device manufacturer. UD Mobile presents a silent notification until the user specified subscription duration has ended or for 1 minute if not specified. Recently the Android app was changed to allow users the specify the duration of the subscription after closing the app. Android requires developers to notify users with a notification when an app is using resources in the background, most android devices will allow users to ignore notifications based on type. So if this is ignored, and we implement push with a different type ID, push will still be presented. If you do not see the notification, It may have been hidden so check the device settings for the App. On iOS this badge should be removed within a few seconds after closing the app when the app is finished saving state, at some point we hope to have a similar user preference as Android. I've updated our wiki with information on how to change this setting. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Global_Settings

Hi @apostolakisl, Replicated on Android. It appears the app is trying to send commands to each device instead of the scene, does not appear to affect iOS. I'll try to get this fixed in the next update. https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/28 Edit: Commit # 04bfc18. Fixed Favorite Type Commands for Commands with no optional values. Fixed in version 0.116

Thanks @bpwwer, Calculating on the app side is somewhat expensive at app start especially with more than one system. UD Mobile has app defined Node Server files for Scenes, Programs, Variables, ect, so they appear the same as any Node. At some point we may be able to add a second status definition to scenes.. Keeping the current Estimated Status with percentage so it appears as a "Group" and a second Scene Status calculated with Link Type. I think link type would have to be static after synchronization as querying this at startup would cause a few seconds of delay, but may satisfy most situations. UD Mobile currently queries the scene relations table when values are updated for all "ST" values with UOM 100 (0-255) and UOMs 51, 78, 79 (0-100). Then takes the matched relations rows and runs 2 queries one for UOM 100 / 2.55 and and one for UOMs 51, 78, 79 with precision calculations. I never could get SQLite to do all calculations in the same query with division for 255 and percentage precision values.

iOS Beta 0.5.8 Adjusted top Navigation Bar buttons. Fixed missing Custom Mappings for node folders. Added Folder creation in Devices and Scenes. Added Scene creation in Devices and Scenes. Added ability to Add/Remove Scene members. Created Scene Edits view. Added Scene Links View. Bug Fixes. Edit Scenes view can be accessed from Home Screen Edit or Node Dashboard.

@bpwwer are you making this calculation somewhere? I can foresee making a similar calculation for the ISY Scene Member (Controller) based on link type Command , but even this could be difficult if the scene link type or command values is adjusted from a program.

I'm not sure this is true, ISY does not have a value for scene status. We do have estimated status in App. As our app developer I have a few questions and observations, which may help future app development. What happens when a member of a Group is out of sync or does not support the sync value (i.e. binary on/off vs dimmable)? Would this not lead to the same issue? Is the goal to show a status? There may be too many variables to make this "better" than the current implementation. The Group definition sounds similar to having (1) all Controllable devices in a Scene as controllers of the Scene, (2) all devices must not be responders to any other Scene, and (3) all devices support the same values (binary or dimmable). How would your description of Scene handle a non momentary device event (i.e. kpl on/off)? What is the difference between your Scene description and a program which executes THEN on device command? A program can control a Scene with no hardware controllers so the command ON value is always executed and command OFF is never executed. The Program case can also handle the non momentary events.

Hi @mbking, Thank you. We have no ETA for push at this time. I'll ask the team to see if there are any updates.