Javi

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

This should not happen, but can be caused by incorrect configuration (local / remote settings) Failing PLM (Admin Console also shows an incorrect value when both AC and UDM are open and status is changed).

Yes see https://wiki.universal-devices.com/index.php?title=UD_Mobile#Migration Jump down to about 8 lines to Finally migrate your favorites and settings in UD Mobile. First backup UD Mobile from Settings-Tab > Backup in case of errors this way Favorites and User Preferences will not be lost.

Fixed span size refresh in next version

Was the issue resolved? If so please let us know how for future reference. If not resolved: Is the Notifications API Key (Notification Tab > Settings > API Key) the same on both Mobile Devices? Do are both devices listed under the Devices Section (Notification Tab > Settings > Devices)? If they are are there any special characters in the name?

This is only from UDM, Scenes do not support % commands

It is an insteon limitation with KPL Buttons, which can only be controlled by a scene. UDM attempts to do this automatically with all devices in the Scene when using the Dim function. However UDM cannot control the KPL Buttons directly without switching the entire Scene. If UDM were to turn on the entire scene it would go to on level not the level set by the UDM dimmer. So without using programs and/or variables KPL buttons can not be controlled using UDM's Scene Dim function. Another option would be to use a Switch which will turn the Scene ON or OFF with respect to OnLevel.

Did you exclude the KPLs from Calculation? The KPL Buttons (not load) only have 0% and 100% nothing in between. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Scene_Estimated_Status If that does not work, you likely have interference from something else such as a program.

This is not the behavior I see, maybe there is something else triggering OFF. The off Command is only sent to the Scene for 0%.

Scenes really have no status, they are static setpoints. So adding to firmware may work in some situations but not all. Also, upon rethinking this, I don't think UDM's Scene Dim function works for KPL buttons when not set to 0% or 100%. There is an Insteon Limitation with KPL Buttons. Only a Scene can turn on a KPL Button, not a Direct Command. In order for UDM to convert this static scene into a dimmer UDM sends commands to each device independently, which will not work for the KPL buttons. However if the UDM Scene Percentage is 0% or 100% then the scene "OFF" or "ON" command is sent. So to show status with KPL Buttons a State Variable can be used, this way programs are not looking at dimmer/button status values. Create a variable, then in UDM add the variable to Favorites, then change Favorite Type to Slider. Create a new Scene for each KPL button where you want status where the Button is the only member as a Responder. Finally create a program which observes the variable, If value > 0. In then set all dimmers to the variable value and turn on the Scenes which contain the the single KPL buttons. In Eles turn off the scene containing all devices. Note that this may require UDM gets variable status on Startup. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Program_And_Variable_Settings