Javi

Hi @fmk2, Currently we have a manual backup and restore option. I've just added instructions to our Wiki (linked below). Please let us know if additional instructions are needed. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Backup_and_Restore

iOS Beta 0.5.7 Added Edit, Admin, and Settings Locks. Bug fixes. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Edit_Locks_.28Currently_Android_Only.29

Hi @ewind, This was a design change for the Favorites screen. Currently there is no way to change this, however allowing users to choose the number of items per row for each Favorites Screen is on our list.

Most developers will report issues when found. My position involves front end and app development. Issues I encounter are with ISY Portal and local subscriptions, and not with third party portal providers. We run stress tests to balance app speed with request success rates, to avoid similar issues. Our alpha testers did see brief connectivity issues, usually lasting a few minutes, with early versions of our app. This was related to subscription loops or too many large file requests simultaneously exhausting available resources. With that said, most developers including myself, prefer to isolate issues before assuming the problem belongs to someone else. If the problem disappears when a third party portal is removed, reappears when portal is re-established, and does not appear with another Portal, I assume the correlation would warrant a report as the issue can be replicated.

iOS Beta 0.5.6 Note: Sync will be required to change mapped Icons/values for folders and Scenes. Added Customizations. Colors can be changed based on Status values at the Global, Individual and Favorites level. Status mappings available at the individual level. Customization Wiki Instructions will remain as Android Only until pushed to production. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Customizations.28Currently_Android_Only.29

Hi @bjs, Thank you. We have have been able to replicate network issues after bombarding the ISY with network request (i.e. denial of service), most of the time ISY recovers within a few minutes after bombardment has ended. In rare situations some issues continued until a reboot. For context, a few years ago Google Chromecast was flooding local networks with much less traffic causing issues with routers. There is a large amount of data transferred during the initial subscription request and ISY can handle many sockets. However, if many subscriptions or portal sockets are started simultaneously, sockets are abandon or not closed gracefully while data is in queue, ISY is waiting for timeout from these clients, then the result could be similar to the stress tests above.

Hi @dennisric and @bjs, Can both of you try to using our Mobile App with only local connection (Second option here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Local_Connections_and_Local_VPN) by selecting Advanced -> Only Use Local Connection ? During initial synchronization the App will check the ISY for missing files or a few other common issues such as network connections. If all is well during initial synchronization please open our app when the issue is presented and it may show us a more detailed error. Connections errors should pop or show as a notification, depending on user setting you may need to pull down your notification panel to see current error status.

See:

Is the fixture wired to the switch? Based on your description of the LED On Level it sounds like the switch is controlling a scene.

It is on our list but a slightly different implementation. The current plan is to have any Favorite available as a widget, so a Favorite of type Command would achieve something very similar. When Command is a Program it can toggle a device without the app needing to knowing status because status is referenced in the ISY program. See the custom toggle example here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle The difference lies in the status updates as there is no good way to implement this without things getting out of sync. Our options are Interval-Status-Checks, Background-Push, and leaving the subscription connected. Background Push will be throttled and/or delayed after too may updates. Throttling and delay is determined Operating System and Platform Push Service (Apple/Google), we as developers do not have control/warnings about throttling or delays of Background Push. This will also require server side setup so Portal would be required. This may work for a couple of devices, if any device is updated too frequently or if there are too many devices updating status will be out of sync. This will also inherently be out of sync as there is no persistent connection and only triggered on status update. So unknown value, such as no/poor internet will not trigger status. We may have this option at some point but it is currently low priority. Interval Status Checks are inherently out of sync as they are request/response driven. This is not currently on our list. Leaving the subscription connected is the most accurate option and is currently a user preference on Android. This will use more data/power, so may not be a great option if your device is connected to mobile data more often than Wi-Fi. This solves the status issue by only showing status when we are subscribed to ISY. If used in with Favorites Command type toggles can still be functional even when the app does not have status. I have been running a persistent connection and Android for about a month and on average it uses 5% of battery daliy, I'm mostly on WiFi so I do not have good data on mobile data usage with this option. This is on our list for iOS and can be changed (-1) on Android in Advanced System Settings.

Thanks. The can be disregarded on Android as well and the message has been changed to a detailed warning, in case a user has Z-Wave devices but they are not found by the app. This should be reflected in the most recent Android production release.

Hi @philgood, If this is on iOS and you don't have Z-Wave devices this error can be ignored. This should be fixed in the next update.

Fix for issue #26 made it into today's build, should be live sometime in the next 48 hours.

HI @apostolakisl, Thanks. I have replicated on the Home Tab, looks like a bug was introduced when saved position was implemented for back navigation. I'll try to get a fix pushed to beta early next week. https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/26

Our UD Mobile App has folders (Rooms) which can show a display node (such as a scene containing all lights). A folder (Room) can have 2 click options(top/bottom) if there is a display node. Clicking the top you can toggle a device/scene clicking the bottom opens the (Room) folder. Weather can be added from a node server and will display in the same way. See screenshot below where all rooms are folders and show the status of lights/weather in that area/room Depends on if your devices are supported by Node Servers.

I'll preface this with acknowledgement that I may be biased ? . I prefer using home automation controls on my phone, both voice recognition and from App. Our wall mounted tablet works great for showing Google photos and thing that neighbors/friends need access to when we are gone. Young children are too loud when they are awake and I prefer not to speak at a Smart Speaker or have a Smart Speaker respond (usually in the wrong room) when they are asleep, not to mention letting a toddler have control of the house (Google's babble translating is amazing). We have GH in every room and its mostly used for timers, podcasts, and music (did I mention children are loud). I can use voice commands on a phone with 99% accuracy event when music/movie is playing which is not even close to Smart Speaker accuracy in a noisy environment. Although most of the time I just use the app for things in the house that are not in line of sight so I can be sure the change was made (i.e. locking the door). Also keeping ISY subscription alive until killed by the system makes the things I use most even faster than voice commands in most cases.

This is on our list for UD Mobile, but after items of higher priority. Android is further along than iOS. Most programs conditions and executions can be viewed in app, no edits at this time. The Favorites Command Type option is similar program execution setup and Individual Status Mappings is similar Program Conditions. This was done to help us work out any bugs before moving code to Program edits.

Amazon devices are showing a few crashes due to database upgrades. This will be fixed in 0.112 and only affects existing installs for version with versions less than 0.110. Will not affect new installations of 0.110 from today/yesterday.

Android Alpha 0.112 (Closed Testing) Fixed subscription remaining connected in Backup Activity. Fixed database upgrade crash for database versions less than 6 (April 2021). Fixed default mapping comparison for NLS mapped icons.

Thanks for checking. Please send me a copy of the backup.

Hi Dave, I can not replicate this behavior. Can you check if the node has an Individual Status Mapping overriding the favorite Icon (Favorites Tab -> Click Edit -> Click Favorite -> Select Configure Colors/Values/Icons) ? I have updated our wiki to reflect that Favorite Icons have lower priority to Individual mapped values when there is a Display Node. Also note that Individual Status Mappings are linked at the Node Status level so it affects both Home Tab And Favorites Tab. So, if the Favorite Display Status is the same Status used on the Home Tab setting an Individual Status Mapping will override both when the comparison is matched. I also just noticed that both the Favorites Icon and Individual Status Mapping Icon have no delete option. So, if an Icon was set the only way return to Use Default Icon is delete the entire Individual Status Mapping then recreated. I also just noticed that the color edit dialog populating with the default value instead of the user input. I'll try to get these fixed in the next update.

It's been a while for Amazon App Store updates. Updated version 0.110. https://www.amazon.com/Universal-Devices-UD-Mobile/dp/B08SKT5NM8/ref=sr_1_8?keywords=Universal+Devices&qid=1637251777&s=mobile-apps&sr=1-8

Android Alpha 0.110 (Closed Testing) Added not null Status Mappings. Fixed existing Status Mappings not showing mapped values. Node Dashboard now honors Status Mappings. Updated wiki with Not Null mapping values.

Hi @FuegoMCS, I recommend upgrading firmware first. Please backup before starting the process and take notes of password reset and program adjustments.

Standard Hex Codes. I would like to offer a predefined set for the globals, but it is lower on the priority list. I noticed I forgot to remove Global test color values for Null and Zero for existing database upgrades, but this will be removed in the next update, only alpha testers affected. The same color code appearance varies too much on Android depending on screen type for light and dark modes so, as before, I ultimately decided to not set default values. I'll try to add "Not null and not equal to" comparison in the next update, probably as the lowest comparison priority so greater/less than values can be caught first. I was hesitant to add this in the beginning as I anticipated too many support issues as not equal could catch multiple unrelated states. I'll have to think about this one, currently there is no value in the NLS for color. This would require additional work during synchronization to insert new and preserve existing user defined values. I'll try to add mappings for existing values in the next update. A few other issues which should be fixed soon: Lock error on back top bar back button press shows lock. Node Dashboard does not reflect color.