Javi

A little hard to follow, but I don't think "Access Control" is an open closed property. If I remember correctly this is something like how it was controlled manual/keypad/etc.. My guess is there are multiple nodes for this device and the Favorite is using the wrong node.

Great, for reference in case anyone else finds this topic. On Android the Notification Channels must be set to App Provided Sound. -

I think it's a generic warning, but it is valid. As long as you crate a UD Mobile backup it can be restored but you may need to re enter credentials depending on if iOS keychain associates the new install to the old install. There is a caveat, If there is a database upgrade in the app you cannot install a backup created on a newer UDM version on an older UDM version.. but that is usually the reverse situation going from Beta back to production. Also Database upgrades are not that common.

I'm not sure, the sounds are included in the app's package so should work unless the user has changed setting on Android OS. Did you happen to customize the sounds on Android? Maybe the file no longer exists? https://wiki.universal-devices.com/index.php?title=UD_Mobile#Android_2

For Matter over Thread a Thread Border router is required. The device can be added to the border router first, i.e. a Nest Hub Max, then share the device with eisy using the sharing QR Code or Pairing Code from the Border Router's app. Eisy will communicate with the Thread Border Router to control the device. Note that Pairing Code entry still in UD Mobile beta for iOS.

I'm not familiar with ratgdo, so you may want to ask in that sub forum.

Bug discovered in version 1.2.9 - 1.2.10. Causes failure on back navigation from folders on home tab and automations tab. Fixed in 1.2.11

Great, thanks for the update. I'm in the process of implementing BLE commissioning through iOS Matter APIs instead of handling BLE ourselves, maybe in the next release.

Most customizations should remain intact if the UUID is cleared in UDM (see link below) and the new Credentials (IP address, remote URL, and auth) replace the existing credentials. The node-address + SQL-Controller-Table-Base-Column-ID (as UDM supports multiple controllers) are the unique identifiers. The controller SQL-Controller-Table-Base-Column-ID is tied to the UUID however the UUID is not part of the Unique identifier. UD Mobile allows users to "clear" the UUID so the SQL-Controller-Table-Base-Column-ID remains intact when the UUID is cleared. UD Mobile will add the new UUID to the existing SQL-Controller-Table-Base-Column on Synchronization if the UUID is cleared. At a higher level if the node-address does not change then customizations will remain intact. If synchronization prompts to "remove cached values" after replacing the UUID then create a backup before removing cached values. If customizations/favorites are removed restore the backup then adjust any customizations which were removed to point to the new node-address before synchronization again. Insteon should be safe in most situations, other protocols/node-servers have enumerated node-addresses so they are susceptible to Address change. So keep node servers in the same slot and add all required parameters prior to synchronizing UDM. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Migration

Does the Node have a Status-Value on the Home Tab? I can replicate a similar error for Nodes which do not have Status Properties. If there is no value (defined values) then Advanced Configurations will not work.

Hi Everyone, See the following for an update:

Version 1.2.9 on iOS will allow Matter Setup Code entry. This version is awaiting approval from Apple for Beta Testers so should be live in the next 24-48 hours. A matter permission was also added which may fix iOS blocking BLE matter commissioning in production but will not know for sure until it is live. Currently the Setup Code only supports devices which were commissioned (connected to Wifi) with another service, still working on Setup Code for initial commissioning. Please report any app crashes on the forum. Version 1.2.9 contains major changes which will allow a future version to remove synchronization.

It may be better in some situations and worse in others, not to mention the introduction of race conditions. Requesting all is a comprises that revoves the possibility of a race and too many requests at startup. While this may be slower in some situations, it may be faster in others. Making multiple requests for a single status values may take longer than requesting all status in a single request.

Updated Wiki Is "Request Status of all Programs" values enabled in the Controller's Settings?

IoX

Probably just need to reboot, this is a requirement (which should be removed within the next couple of firmware updates) to get formatted values after node server install.

Thanks, I can't replicate the name error so please verify UDM is on 1.2.32 in a few days (currently awaiting Google's approval). If the issue is not resolved by then try synchronization, if still not resolved send me a copy of the app backup and I'll take a look. With regards to "off" add another customization for the value = "off" with an empty string for the formatted value.

Set the Formatted Value in the Advanced Configuration to a space (i.e. " ") this will remove the words off or on. Or set it to "off" and remove "off" from the favorite name. Please show a screenshot so I know the location. I'm in the process of many lower level changes to update the app and may have missed something.

Portal Licenses are tied to the Controller not the account, so you just need to remove the controller from your account (or revoke locally) if you sell. The new owner just needs to add the controller to their account and approve locally. UD Mobile works with local only connections: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Local_Only_and_VPN

Yes, The Advanced config is linked to a node property not a favorite. If only a boolean is required then the program route will work without the need for more variables, but you will have more programs. If this was a real device, not a variable, I would suggest the Favorite Type Picker which would show the command dropdown. Another option may be the Virtual Node Server.

The Advanced Status (list) is linked to the Node (variable) property (value). So the Home Tabs and any favorite with this node (variable) as the Display-Node will use the same Advanced Status (list) as the list is linked to the Node Property not the Favorite. I don't quite follow what you are trying to achieve, so the following is based on the assumption that you want to show the status on each button along with a different color. If you don't need status then remove the Display Node and use Color in the favorite's editor, not the Advanced Status. To show 3 different colors for the same node property you will need a work around as this is not a common situation. UDM is very flexible so there are a few ways to do this. Using 3 variables which are all set to match the tracking variable. This can be done in a program, something like if state_var_1 changes set var_2 to equal state_var_1 && set var_3 to equal state_var_1. Now you have a separate node which has its own Advance Status list. Using programs with only an IF statement to match the desired status. Then in the Program's Advanced Status list change the color based on Idle-True and Idle-False (i.e. is desired status true or false).

What is the app version? Version 1.2.8 was released this morning with bug fixes.

Issue should be fixed in iOS app version 1.2.7. Usually takes apple a couple of days for review before going live. Thanks

Thank Guys, I had a few reports of this issue but could not find a Firebase crash log. @Geddy 's Apple report actually came through with the crash log. I don't even check there often as the reports usually fail to include the crash log.

It's still on our list, but can be done from the Admin Console. Scenes in version 5.x are much more complex than Scenes in 4.x (see the 5.x fan example). Also for insteon the Scene information is written to the Controllers/Responders so may take some time depending on the number of changes. Each Scene-Controller-Settings has an on-level setting for each responder in the Scene. The Scene-Settings also has an on-level setting for each responder in the Scene. So changing the on-level for each Responder manually may not be intuitive or may not work as desired without changing many properties. So, if you set the Scene-Settings on-levels' for each responder, it will only work if you trigger from eisy. Setting on-levels from a Scene-Controller-Settings will only work when triggered from that Controller. What are you trying to do? There may be another way to accomplish the same without getting too deep into the settings every time a change is needed.