Javi

Another option is IR codes with iTach. I have a single iTach and xantach IR distribution to all A/V Electronics in every room. This makes it easy to add/replace AV devices as the iTach Node Server controls all A/V equipment in the entire home. iTach has 3 outputs so if 2 devices have the same codes the output can be changed. We have 2 Samsung TVs with the same or similar code sets so both rooms use a different output. Most devices have code sets in the Global cache Control Tower Database, but if they do not exist you can learn or find codes online. We also have an old smart TV in the bedroom which I did control via IP for a while as it had no discrete (on, off, input) ir codes. This is the only AV device I have owned without these discrete codes. The TV would fall off the Wifi network sometimes and it was a pain to troubleshoot, so I added an energy monitor to determine if the TV was on or off to simulate discrete codes with power toggle from iTach. This also makes debugging an automation easy as you will see the ir blaster blink when an ir command is sent.

Changed 100 to 200 on Wiki. Too many false exits with 100 meters, although it may need to be much greater depending on location to avoid false exits.

Ok thanks for trying. Being as this is outside of UD Mobile can you please open ticket? Please reference this thread and that Javi asked you to open a ticket.

This instance of PG3 was connected to that ISY at one point, as it retrieved the UUID. I'm not sure at what point the UUID is obtained and/or validated, so we will have to look into this. Maybe try changing the IP Address to 0.0.0.0. then Save?

Please unplug, Then try synchronization.

My guess is you have either Local Connection Settings or Remote Connection Settings Pointing to the old ISY as sync will fail if it encounters a UUID which does not match. This needs to be corrected, then UUID need to be cleared.

I don't believe so, eisy only has interfaces re0 and wlan0. While I'm not a network architect, I think you need a VLAN switch, or device that can act like a switch, before connection to eisy.

While there is currently no app which has all features of the Admin Console, UD Mobile allows basic program edits, Variables, Network Resources, and a few other items are not yet editable from UDM. UDM requires firmware 5.0.16 or greater.

Try swiping app from recents, it is likely still looking for the other instance. I'm not sure we tested delete as UDM was only intended to show a single instance.

Should be live now. Issued caused caused a race condition when returning from backup dialog (System file selector) which briefly restarted subscription (value population). This caused removal the newly populated values along with removal of unused values.

I don't think the one with port 3000 is currently connected to anything, although it may have connected to something at some point. You must have manually changed the port at some point as we only default to port 8080.

Wifi is not available while ethernet is connected. Set Wifi credentials from UD Mobile > Settings Tab > WiFi Configuration.

While both instances are available in UD Mobile it may not be intuitive as UD Mobile was really only intended for a single instance. So it may be easier to use the PG3 web interface. As far as I know a second instance must be created by the user, so I'm not sure how this was created without user intervention. This screenshot shows a Polisy with 2 PG3 instances "Test Polisy" and "Home" with "Home" having a checkmark as the web interface is currently interacting with "Home". From there you can "Edit Current IoX" which will show the connection settings for that instance. In this screenshot "Home" is a 994 and "Test Polisy" is a Polisy. The Polisy box is hosting both PG3 instances. Pressing "Edit Current IoX" for "Home" shows the connection settings for the 994, with the local IP Address. If I switch to "Test Polisy" the select "Edit Current IoX, the IP Address should be 0.0.0.0 as IoX (ISY) is running on the same box. If there is an unmanaged node it could be from an old instance of PG2 or "Portal" (Occupancy Node Server). If you cannot access the Polyglot instance which created the Node Server then you will need to delete the Node from the AC.

Both of these PG3 instances are running on the same box. Each PG3 instance can serve nodes to any box running ISY as long as they can communicate (on the same network). So it appears you have 2 instances of PG3 running on your Polisy one is linked to your ISY994 and one is linked to your Polisy (ISY on Polisy)

Probably best to delete the unused PG3 instance if it is not used to avoid confusion. The first remote connection to PG3 may require a reboot, I'll try to add a confirmation at that point so there are no surprise reboots. There can be multiple instances of PG3 running on the same box (Polisy/eisy) and connecting to different systems (isy/Polisy/eisy). When an instance of PG3 is linked to an ISY/Polisy/eisy it gets the available slots. If a slot is unavailable and is not managed by the linked instance of PG3 then the Node Server is "Managed by another instance". The Multiple instance feature was intended to link Polisy to ISY994 before IoP (Isy on Polisy), so it is not really needed anymore.

Managed by another instance shows that the connected instance does not manage the Node Server in that slot. Logs only work on local connection (still on the todo list for remote) so it is very likely the Local Credentials are incorrect in Settings-Tab > Systems > Your System > Local Connection Settings. Do you have multiple eisy/Polisy boxes running? Is PG3 connected to multiple systems? From UDM Admin-Tab > Plugins > Settings (gear icon at the top), is there multiple ISYs listed under ISY Configuration?

The 25 items may be your variables. If it happens every time then they are not being retrieved during synchronization so the app wants to remove them. Should be easy to replicate with remote access. If interested I can do sometime this week, send me a PM or open a ticket, and include UUID.

Both Apple and Google say fences can be delayed by ~2 minutes, so this must be considered with setting the Geofence radius. Geofencing is broken at the Operating System Level for most Android Devices which is the reason UD Mobile on Android implements a location service. The Location Service is not as good as OS level Geofencing so either the polling needs to be triggered or your mobile device must connect/disconnect from WiFi before the Location Service will trigger a crossing. If using the Location Service you can increase/decrease polling intervals on fence crossings, so using multiple fences may make this more timely.

Because all status values in ISY are represented as numbers. While it is possible there are negative values this is not very common so negative was omitted for globals, but can be set in custom mappings. Most dimmable lights/switches have values 0 (off)-100 (full on). Most non-dimmable lights/switches have values 0 (off) and 100 (on). Globals may not work well with devices which do not conform to 0 (off) and greater than zero (on). I don't think the Node Dashboard screen Scene Members section incorporates colors of any type, but the same device should have a color in the Node List or in Favorites. This screen has not changed much since release, so it is due for a upgrade, I'll try to get colors in at that time. Programs will always have the positive color as they do not conform to 0 for off and greater than zero for on. They have 4 common values Idle-true, Idle-false, running-then, running-else. Adding globals for programs is on my list, although it has lower priority to other features.

The disappearing undo message (snackbar undo) is fairly common in app and web development.

@LFMc, I apologize I misread interpreted the error message. This is a UD Mobile database cleaning message, it is similar to the error message I mentioned above as that error also causes nodes to be removed from the App's Database. If the message does not include an error then it should be safe to delete these values without removing favorites, although you should always backup just in case. Can you try a backup then remove values? Does this correct the issue?

This usually happens when ISY994 is under heavy load, resulting in invalid responses, which causes UDM to believe the resource (variable/node/etc) no longer exists so it is removed from the app. A reboot usually corrects the issue. Does this happen every time? Does a reboot correct the issue?

The link works for me. Is there another issue?

Try setting the Global Defaults first, Then if you have a device that does not conform set it's mapped values individually.

Is this a Scene? Scene's have estimated status as they don't have a native status. There are some scene members that can cause this estimate to be incorrect. Devices such as Key Pad Buttons or battery powered devices need to be manually excluded from estimated status. See: https://wiki.universal-devices.com/UD_Mobile#Scene_Estimated_Status