Javi

It should respond.

It does, but it is actually a scene used so eisy can observe status of all devices. Icon is a monitor, see @Geddy 's image.

Please update to 6.0.4. Sync should not be slower, but there is less info is shown in progress, so current process remains longer. Manual delete of eisy Node Properties databases may be required. However a firmware upgrade usually fixes this also. If not fixed by 6.0.4 please open a ticket.

It may be a different name like "ISY" or "IoX" depending on when the original file was created or if renamed. Icon should look like a monitor.

@Techman , I misunderstood the request. You are trying to send all off to the ISY scene. We do not show this scene in UDM as it would likely cause confusion. The work around used by @IndyMike sends the same command to the ISY Scene.

iOS version is in review now, so likely live in the next 1-12hours. If this does not correct the issue, please open a ticket, include UUID

Not normal, but cannot test on 6.0.3 as the current patch is 6.0.4 which has bug fixes. Also UDM 1.4.15 is awaiting apple's review so should be released soon, so also worth a try after upgrading to 6.0.4. If issue persists after upgrade try to disable each of the controllers to check if it is isolated to one (Home Tab Menu > Controller's Settings > System Settings), cancel requests to synchronize. The reason is one controller may be publishing too many status updates causing UDM to appear slow for both controllers.

I can not replicate this behavior, both Conditions and Actions show the path in Admin Console on my eisy. Are you sure the device is in a user-created folder, not the main folder? The default name for the main folder is iOX, but may have been renamed by user, the icon is a monitor. If in this "folder" it is at root.

Adding comment in case others users are trying to isolate issues with some z-wave devices, specifically this happens frequently with some brands of z-wave locks. See https://wiki.universal-devices.com/UD_Mobile#Schlage_Locks

I must agree with @Guy Lavoie .

Update: if this is z-matter use: /rest/zmatter/zwave/node/<nodeAddress>/security/user/<userNumber>/set/code/<pin> /rest/zmatter/zwave/node/<nodeAddress>/security/user/<userNumber>/delete Note that there is no validation from the device, so if it does not work the device may need to be awake. This is also true in Admin and UD Mobile.

Should be fixed in UDM for iOS v1.4.15

We do hope to have for UD Mobile soon. It can be done remote. Get the url to ISY from my.isy.io then append the paths mentioned above then enter in a browser. Note that 3511 is the code and <userNum> is the user number.

I believe issue was resolved. Please let me know if it persists

Should have been fixed in iOS a few weeks ago, todays Android release should resolve the issue after sync.

Not intentional, but many things broke in recent updates. Let me know if there are high priority lockouts and I'll try to get them implemented.

Hi @dbwarner5 , apologies for the delay. We are still trying to find the cause, this our only open ticket where the issue was not corrected with 6.0.4 update.

I think this was fixed in 6.0.4. If not the profiles database files need to be deleted + reboot which will recreate. If you don't already have an open ticket and issue persists please open one.

Was issue corrected?

It is a UD Mobile limitation for remote, works locally in pre 6.x firmware. Local PG3 connections are currently broken in UD Mobile as we are migrating away from separate local and remote credentials, like eisyUI. If you are local use eisyUi on web until fixed.

The account selection is only shown if you are logged into more than one my.isy.io Account. Issue replicated fixed in 1.5.6, will try to release soon

Hi, this is very high on our list, with a new firmware implementation in 6.x. Until that time it can still be done with the following urls. // Deletes a door lock user code e.g. /zwave/node/<nodeAddress>/security/user/<userNum>/delete // Sets a door lock user code e.g. /zwave/node/<nodeAddress>/security/user/<userNum>/set/code/<pin> Update: if this is z-matter use: /rest/zmatter/zwave/node/<nodeAddress>/security/user/<userNumber>/set/code/<pin> /rest/zmatter/zwave/node/<nodeAddress>/security/user/<userNumber>/delete Although these locks do not validate the user id was saved or changed, so still requires manual check.

I believe you have already opened a ticket, if not please open one for diagnostic.

@Techman , I think it is fixed in UDM for Android 1.5.3. Not yet released, likely next week. please let me know if issue persists in that version.

Unless you intended to have 2 instances, the one not linked to any of your programs should be removed.