Javi

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.

If on the latest versions please open a ticket. Not sure, aside from missing status values does a screenshot show the issue? If you have multiple controllers have all been synchronized?

The message is due to NO node definitions found for the Plugin Slot Number (instance). Synchronization changed in the last few versions, So possible there is a bug somewhere. new Synchronization should be much faster. Requires at least 6.0.3 if on Firmware 6.0.x. If there is a functioning plug-in that slot, and synchronized on 6.0.3 or greater please open a ticket so we can investigate.

Do you get synchronization errors? Any other errors? Have you synchronized? There should have been a message about synchronization being required in one of the last few versions.

There is an issue with The node server in slot number one. Is it being used? Is it running?

I have these locks also These locks do not conform to the Z-Wave Standard. Any lockup of the physical device would not be caused by eisy, so the device may be starting to malfunction in addition to compatibility issues. See the following to "fix" the compatibility issue: https://wiki.universal-devices.com/UD_Mobile#Schlage_Locks

Ok, thanks. Responded to your ticket.

If is -1 then it can be reused, if not then it cannot. if none are -1 then no others can subscribe which will cause issues. They should clear themselves but could take some time. See page 10. https://docs.universal-devices.com/developers/docs/3.1.1/ISY-WS-SDK-Manual.pdf Edit: Forgot to answer the question; if you have an SID and for any disconnect reason (self or forced) try to unsubscribe. Obtain a new SID on subscribe.

Thanks, That helps. Will review.

0.8.8 is still in staging. 0.8.5 is latest release. @dbwarner5 , I want test something, to narrow the issue to initial value and/or value change. If the value changes (i.e. from ON to OFF, not query by opening dashboard) 1) Does the app show the value change without a query (i.e. without changing the screen)? 2) If #1 is true, is the value shown the next time the app is opened, or is the value null again?

The process has changed as the automatic change to Favorites causes issues in some processes if the user leaves or the app directs user to a webpage. New process is listed here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Show_Favorites_at_launch

Just tested and Groups work, are you sure the program was saved prior to testing? You can also test from the UD Mobile Node directly. Setup: https://youtu.be/KSmx-XIquAw Sending to a specific Group or Device: https://youtu.be/z4pquLcI2Es Creating your own notification content: https://youtu.be/KSmx-XIquAw?t=165