Javi

Thanks

I have a similar "Access Control" node and have verified (1) the status mappings are incorrect and (2) formatted values are not being displayed in UDM (subscription formatted). I'll submit a bug report, however it is at firmware level so may be some time before a fix makes it to production. I also think the Node may not have installed correctly or may require a compatibility mode. The Binary Door/Window Sensor has a status on my end and is the Node I use to verify status. If unsure how to do this please open a ticket as it's not my specialty. If you open a ticket, let me know the number and I'll attach notes.

Polisy is likely the cause.

Also Polisy, may not be supported. There were networking changes required. Please open a ticket if using Polisy and wanting matter support.

Yes QR Code was the only way prior to the latest Android and iOS (iOS still in beta) versions of UD Mobile. It's possible we don't yet recognize the device type, but basic on/off should work. I've only tested with this https://www.amazon.com/dp/B0BZBGD87V?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_1. Was/Is there an error message?

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.