Javi

Go to your UD Mobile Geofence, and set the enter/exit commands to turn on/off the "Kent" Node on your device and the "Nancy" node on the other device. We do not create Geofences on other devices automatically for various reasons including stocking, privacy, ect. As an alternative you can create a seperate Geofence for all users on a single device (i.e. one named Kent Home and one named Nancy Home) with the same radius, but change the enter/exit command match the node for that user. Then disable Geofences for the other users. Export your backup to the other users device, then enable Geofences for that user and disable or delete those for other users. Edit: Also not that the OS (iOS/Android) may periodically ask the user if they would like to keep location permissions. So the other user must be aware, and accept always allow location access if prompted.

This is only in relation to the v4.x setup for the KPL which references grouping. The Grouping is depreciated, not toggle mode. Using the 5.x scene to turn on/off a device which is not a toggle could get confusing quickly.

I've updated instructions https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server

If I remember correctly changing the toggle to non-toggle[on/off] required the depreciated button grouping. When using 5.x scenes the buttons should be left as toggle. IMO the best way to link KPL buttons with a fanlink is with a single scene similar to the 5.x example on our Wiki. If you want to keep an OFF button then the setup is slightly modified. If you want to use AC/UDM/Alexa control the Fan directly, not from a scene, then write the programs/scenes to keep KPL in sync. https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

The Upload node definitions will install the Node Server. I may have missed this when I wrote the instructions. Please let me know where this should be inserted and I'll update the wiki. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server

Add a seperate Geofence for each person as the commands should be to a different node/variable/program. Then disable all except for the Geofence related to the same device (person). You can do this on the device which will export the backup file. Then on import to another device verify the correct Geofences are enabled/disabled for that person.

Yes, with a combination of programs/variables. Each device updates a unique State variable as a boolean where entered=1 and exit=0. A program evaluates whenever one of state variables change if all state variables are in the IF Condition. IMO the node server is better when trying to use a group, no need to use urls simply adding a geofence (location) then adding devices (people, then add devices (people) to the geofence (location). Then you trigger Enter/Exit (On/Off) for that device (person) in the UDM Geofence Commands. Now in programs you can trigger automations whenever the Geofence (location) is on/off. With the variable/program method you would need logic to check if all people (devices) have exited or if someone entered when all other devices (people) were already gone. We should probably make this a local node server at some point.

If you import the UD Mobile backup your fences will be in the backup but will need to be re-enabled if they did not exist on the same phone already. Programs can be used to check if you are both at a location, but it may be eiser to use a node server which tracks groups of users such as Portal Occupancy. See https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server

https://www.universal-devices.com/my-tickets login with your portal account. We changed synchronization functions in last few versions of UDM for iOS, so very possible it is an issue with UD Mobile.

If reboot/upgrade does not correct the issue and you have an ISY Portal account then please open a ticket. Include your UUID and platform (iOS/Android) with text stating Javi asked you to open a ticket. I will provide instructions for remote diagnostic approval if we need to connect to your system to replicate the issue.

It is still on my list, not sure on timeline.

UD Mobile currently creates basic scenes. Editing of Scene Links, for things like ramp rate and on level, must be done from the Admin Console. This is still on our list for UD Mobile. There are limited Scene edits in UD Mobile by either Home Tab edit mode or Node's Dashboard settings. From Home Tab enter edit mode by clicking edit button (pencil icon) then click the scene then click Edit Scene. From the Node's Dashboard (screen with all status and commands) click settings (gear icon) then click Edit Scene.

You can access from http://ipAddress:3000 (or eisy.local:3000)on your local network. The Occupancy Node Servers on Portal is a Geofencing Node Server for third party apps. No need access Occupancy unless you have a use case. Installing and configuring the first Node server has a learning curve. I recommend a weather Node Server to start, something like WeatherBit. WeatherBit is $5 and allows you to add weather data to eisy.

I stopped using CAO Tags for the same reason, do the YoLink Devices work inside a fridge?

Hi @Merlin, Thanks for starting this topic! I'm having my main water line replaced in the next few weeks which requires opening a wall so I will be adding a motorized main valve at the same time. I had WaterCop in my Amazon cart for years, but it appears it is no longer being produced. I was not impressed with the other Z-Wave options as they blocked or had no manual controls and/or used the pipe for leverage. Many of the other non-Z-Wave options may contain lead, so they are a no go and the reason the line is being replaced. I just purchased the YoLink Meter and Valve combo and hub at a 20% discount on their site. While I was only looking for a valve the meter will allow me to eliminate Flume and their expensive proprietary batteries....not to mention the meter being moved outside and I'm not sure if the new meter is supported by flume. The YoLink Hub is still required but it is very inexpensive ~$20. If you are using UD Mobile Notifications then you are already using a Node Server.

Yes, use a disabled program. Then have UD Mobile trigger "Run IF" on enter. The program is disabled so it is not triggered automatically when the sensor status changes. Something like: If sensor is closed Then open garage door. Note that you may need a larger geofence to prevent false entries exists.

This sounds like it is an issue with Favorites, however I cannot replicate. Please send me a PM or open a Ticket and attach a copy of the UD Mobile backup file, this must be zipped first for tickets. I may also need to do a brief remote diagnostic so will provide instructions for you to approve our access if needed.

I don't think this is related to the original issue. We recently rebuilt favorites and there were are few status errors in programs. Do you have the latest version of UD Mobile for iOS (1.1.40)? Does the same error happen from the Home Tab?

While UDM contains most features of the Admin Console is not depreciated and does contain features not yet available on UD Mobile. Did you try "admin" for both username and password after reset? Are you on a local or remote connection (i.e. remote if url is https://my.isy.io/.......)?

I can not replicate this behavior, also cannot find this exact error message. Is this still happening? Can you post a screenshot of the error message? iOS or Android? What is the hardware (eisy, Policy, or isy)?

Server issue corrected.

Replicated, we are looking into this again.

Server issue corrected.

Replicated 404. We are looking into this now.

Hi @n_sievers, What ihardware (994/Polisy/eisy) are you using? Do you get any error messages from Settings Tab > Systems > Your System, Remote Connection Section > Test Remote Connection? Note that you will need to disable WiFi on your Mobile device if you have Local Connection Settings configured. May be today's weather in Denver 😁