Javi

This 401 error is invalid username or password for the direct local connection. Try the default of "admin" for both. If the default does not work then it was changed by the user and will need to be reset. Alternatively the URL to ISY from ISY Portal will work with the Admin Console using your Portal Credentials.

Does the system have > 1024 programs/program-folders? If they system does have > 1024 programs it is a bug in UD Mobile. ISY994 had a limit of 1024 programs which I do not think was updated for eisy.

My guess is that another device has the spoken, or Alternate Spoken as "Kitchen Lights". Currently UD Mobile does not have a search function for Alexa, but the Portal Website does. From my.isy.io for the system UUID under the tools column press Select Tool > Connectivity > Amazon Echo, the try a search in the search box.

The issue is the ISY (not Admin Console) could not get or parse the NLS file. For historical reasons the Admin Console has its own NLS parser. It appears the Admin Console was able to get and parse the NLS file. While UD Mobile also parses the NLS file it relies on ISY for formatted values when a status value changes which is the reason we know the ISY could not get or parse the NLS file. As far as we know this is not an issue with current firmware or UD Mobile. The same issue may be caused by an earlier ISY994 firmware which could have migrated. It may also be caused by Node Servers not updating profile files properly. To check if this is caused by a migrated file please post or send me the response to /rest/profiles/family/10/files (i.e. http://192.168.X.X:8080/rest/profiles/family/10/files) ? . Also let me know the slot number for the node with the issue. If the issue is not due to a migrated file other debugging steps are needed.

Hi @sjpbailey, As the author of the very misleading error message, I can say the error originates from code which was catching a bug in early 5.x 994 systems. This bug showed itself when 994 would return empty XML after multiple successful (200) response for data. With that said UD Mobile may catch other errors here also, such as files with empty XML. So, it is very possible this error is triggered by a Node Server. Please open a ticket and we can try remote diagnostic.

The default behavior for scenes functions similar to a switch. However if you have devices which do not change status such as Key Pad Link Buttons, and Battery Powered Devices may need to be removed from Scene calculations from the Node Dashboard see: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Scene_Estimated_Status It depends. The reason the program is disabled is to prevent a vicious loop. In the light example posted above the program would continually run as soon as the light changes status. The status change triggers the program to runThen or runElse, which causes the a status change which causes the program to run, repeating forever. If the IF Condition does not trigger a change, such as an integer variable, then you can use as is. If the IF Condition triggers a change then the program will run on its own. So issuing the runIf command from UDM may not have any effect as the Then/Else action may have already been executed.

I'll add that there is a global option for colors Settings Tab > Global User Preferences which will remove the need to set each device individually.

The Node Dashboard is the screen shown which has all Status (sorry typo) and Commands for a node. i.e. clicking the node on the home screen takes you to the node dashboard This is automatic for most devices which have On and Off commands, such as lights/switches, no need to modify. The default Program behavior on click is runIf. So place your IF condition (i.e. if light is off) in the ISY Program which will trigger runThen (turn light on) or runElse (turn light off), then disable the program to prevent it from running automatically. If you want to customize the display, i.e show something other than the program on the tile, see the following example. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

Settings-Tab > backup. iOS allows backup to iCloud but requires the backup to be moved/copied to the iPhone local storage before restore. Both backup and restore via Google drive work for Android. Credentials may need to be rentered after restore. Geofences may need to be reenabled after restore. With regards to Favorites, there are a one button add options. On home tab, click edit (pencil) click node, add to Favorites. Or From node dashboard (screen with all statues and command) click settings (gear) add to Favorites. You can add a device to Alexa from the Node Dashboard also by clicking the speak (person speaking) icon.

If it is the same UUID with a .local url then it is just another way to connect to the same system locally. Either URL can be used. UD Mobile will also show both when using the local finder next to Local Connection Settings > Local IP Address. Some network (router) settings and/or operating system may prevent one of the URLs from being shown or responding to a network request.

UD Mobile will ask users if they would like to install the Notification Plugin in the following situations "My Notifications" was clicked on the Home Screen "Notifications (Create, view and edit push notifications and programs for this device)" is clicked from the Node Dashboard Settings. Node Dashboard is the screen which shows all Status and Controls for a Node, the settings is the gear icon. If the user agrees UD Mobile will automatically install and configure the free version of the Notification Node Server.

Do you receive an error message,? If so please post the message or screenshot. The Local Connection Settings require the local credentials, not portal credentials. After these are entered use the test button at the bottom of the Local Connection Settings to test the connection. Please post error message if not successful. Note that Local Connection Settings override default settings, so the IP Address should be reserved in your router or it may change. To use the apps default settings Only Use Local Connection must be unchecked and all System Network Relations must be removed.

The app is trying to use Local Connection Settings. This is a manual override setting as Local Connections are not setup by default. Was this error automatically shown on the on the Home Screen or trying to issue a specific command? If automatically shown on Home Screen Continue. Go to Settings Tab > Systems Do you have more than one System listed? Select the system named home "Home" Expand Local Connection Settings. Is there a Local IP Address? Is "Only use Local Connection" enabled?

Settings Tab> Systems> System > Program and Variable Settings

OK, thanks. Will try to replicate

Ok Thanks for the clarification. Was the QR Code used to add the device? I own this Zooz device also. However it is connected to an older UD System which I will be migrating soon. May try to replicate at that time.

If you enabled ZMatter then the UD Mobile will communicate with the ZMatter Hardware not Zooz Hardware. Do you have both connected?

Did you enable or have the ZMatter Hardware? Unless something changed the Zooz, 500/300 series modules all had ZW prefixes, ZMatter Zwave support has ZY prefixes.

Hi @TRI0N, Sorry for the frustration. Usually reboot solves communications issues after firmware upgrade, upgrades from some versions may required a hard power cycle. If that does not work please open a ticket.

Fixed in next release. Android 1.1.30 iOS 1.1.15. Until fixed a new group can be created without "/". After update the old group can be deleted.

Thanks, looks like a similar bug. If you want this tracked please open a ticket. Attach images for <nodeInfo>, <nodeDef>, AC image, and a zipped Backup File for your system (Not a UD Mobile backup). Include this as the issue: "Encoded Editor missing formatted values in rest/nodes, and Subscription Event." This causes missing formatted values in Notifications, Emails, and on UD Mobile." If you open a ticket send me a Private Message with the ticket number.

This was a bug in ISY994i. I thought it was fixed in Polisy/eisy firmware.

Please post response to /rest/zmatter/zwave/node/ZY0nn_306/def/get

Based on the the <nodeInfo> it appears IoX does not have the formatted value (formatted="2"). Can you please let me know if UD Mobile shows the formatted value or a numerical value for the same ALARM Status? The reason the formatted value is shown in Admin Console is because Admin Console parses values itself it does not use the IoX parser. However when a notification is sent the IoX parser is used.

Hi @mbking, I'm trying to replicate this issue. Are you using a beta build of the Node Server?