Javi

@dbwarner5, The remote integration is Beta as it does not have all features, but the error should not happen. It may be related to the Allow ISY Access Parameter as this has not been added to UDM. What is your eisy and PG3 firmware versions?

The first thing to check is if this is a connection or read timeout. I've seen long connection times when multiple family members are streaming which is network related, not eisy related. Assuming read timeout: Not single threaded, but to maintain thread safe operations most software queues some request to a single thread. For example a program triggering notifications with variable substitution, we don't want the variable to change during substitutions. Busy can happen for many reason, such as large data queue when starting a new local subscription. Portal (remote subscription) has a single socket so it will request all values (rest) when a new client connects as it shares a subscription amongst clients. IMO a 30 second timeout local, 120 remote should be sufficient for both connection and read.

Both items are on our list in one way or another, although not sure on timeframe.

Beta 1.1.52 Updated Device Dashboard (aka Node Dashboard) cells and added new menu to select cell type. Added alpha Device Property History (aka Status History). During initial testing you must enable capture of status history, this will likely be enabled by default in a future firmware version. During alpha testing we are only trying to verify this does not overwhelm eisy, especially users with large systems. Chart options, improvements, and favorites tiles coming soon. See: https://wiki.universal-devices.com/UD_Mobile#Status_History

In short this is an insteon limitation with non-load bearing KPL Buttons. See Known issues: https://wiki.universal-devices.com/UD_Mobile#Scene_Estimated_Status . I updated Known Issues, but this issue has been discussed at length in the forum, so a search may shed light on some more detail. Not Possible, the only way this would happen is if you turn the Scene off/on not the Dimming Device...the scene cannot be dimmed to a percentage from the admin console. Even if using the "DIM" button a non-load bearing KPL Button will not turn off. It has always been possible to control a physical device outside of a scene. For example KPL buttons and fanlink commands (low,med.high,off), would be close to impossible.

Sending a command to a Device (not scene) from UD Mobile or Admin Console only affects the device. If a scene is being triggered then something else is causing this to happen. Scenes in UD Mobile have the added percentage capability which may not work with all devices, specifically keypad links and battery operated devices. The ON and OFF button should work the same as Admin Console. See wiki for adjusting Scenes for percentage commands.

We have seen this a few times with upgrades, it is usually related to UD Mobile being linked to the ISY994 not eisy. Since ISY994 can no longer install/purchase new modules UD Mobile cannot automatically add the ISY994 to Portal.

Tapping the indicator (triangle) next to the command parameter name (i.e. Group, Sound, Content) changes the selection from predefined values to variables. This is how all programs behave and allows for saving a status to a variable then sending that status as a command parameter. This works with integer variables as all Status and Command values are static and enumerated at a lower level.

These are email groups, not Push Notification Groups. Create groups in UDM from Notification Tab > Settings (gear icon). I believe the node server will need to be restarted after a group is added.

Long press the App Icon on the Home Screen which will show shortcuts. Then long press "Favorites" and drag to home screen. This should not be necessary, but could be caused by multiple issues. If this also happens in Admin Console then likely interference from power line noise.

On our list, but we don't have a time frame. Also see the following for limitations:

Currently Android has a Favorites Shortcut which can be placed on the Home Screen. iOS has a preference to open to Favorites Screen. As for widgets, they only allow limited updates, the amount of updates is determined by OS, but If I remember correctly it was about 50 per day (2 per hour). So while widgets may work well for some things that don't change frequently, like weather forecasts, it will likely lead to support issues for most other devices as Status will be out of sync for some users. This will lead to widgets with incorrect status values. With that said, direct commands shortcuts are on our list but not yet implemented. This would allow trigger of a program which checks status for toggle, which does not require that UD Mobile knows status.

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.