Javi

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?

Creating a Node Server which populates an ISY Status with the Network Response code could be built quickly. Most of the other ISY Modules have Node Servers equivalents which are far superior such as Wake on Lan, Elk, Weather, and Notifications. Even if we were to rebuild Network Resources it would be as a Node Server as Modules are depreciated. Although why build a generic network module when you can target the exact device your are trying to control, this is likely the reason Network Resources have not been recreated as a Node Server.

I've never used this integration, so it is possible it was different at one point. Maybe @bmercier knows if anything changed. As far as I can tell V2.0 is almost the same as V1.0. You can click the expand button to get the enter and Exit urls and use the same way with locative.

Node Server is still the answer. We are working on better documentation and have a few examples which can be installed then modified to fit your needs. See https://docs.isy.io/

@TexMike, I don't believe the Portal Occupancy Node Server has changed in quite a while. There are 2 versions, looks like Version 2 has On and Off commands in AC. You may need to synchronize UD Mobile after the Nodes are installed for the commands to become available in UDM's Geofence command selection.

https://wiki.universal-devices.com/index.php?title=UD_Mobile#Migration if you want to preserve favorites then follow instructions above. This basically clears the UUID so the new system replaces the old system and changes access URLs to the new system's local/portal URLs. If you don't want to preserve favorites then add the new system, then delete the old system after migration.

Thanks Jim, Looking into this.

Hi @Jimbo.Automates, I think I may have found the issue. There are two US-English NLS files being created, one upper and one lower case. <profile family="10" id="1"> <files dir="nodedef"> <file name="PORTNDEF.XML"/> <file name="nodedefs.xml"/> </files> <files dir="editor"> <file name="custom.xml"/> <file name="PORTEDIT.XML"/> <file name="editors.xml"/> </files> <files dir="nls"> <file name="EN_US.TXT"/> <file name="en_us.txt"/> </files> </profile> I believe the EN_US.TXT is being created in error as it only contains a small number of definitions ND-occupancy-NAME=Occupancy ND-occupancy-ICON=MotionSensor ST-ST-NAME=Occupied ND-occ2_device-NAME=Occupancy v2.0 (Mobile Device) ND-occ2_device-ICON=MotionSensor ND-occ2_geofence-NAME=Occupancy v2.0 (Geofence) ND-occ2_geofence-ICON=MotionSensor ST-occ2d-ST-NAME=Occupied ST-occ2g-ST-NAME=Occupied Was this somehow created by ELK? Does not look related.