Javi

Currently there are no "tabs", but is on our list. There are "Folder" Favorite Types, which also support a display node. See: https://wiki.universal-devices.com/UD_Mobile#Type

I don't think they are errors which will cause issues. It is likely an invalid format in a human readable name for a node server. The next version will list the Family (i.e. Node-Server, Insteon, etc) and instance (i.e. node server slot). Please post the same screenshot when they Family and instance are displayed and we can investigate further. Same as:

I don't think they are errors which will cause issues. It is likely an invalid format in a human readable name for a node server. The next version will list the Family (i.e. Node-Server, Insteon, etc) and instance (i.e. node server slot). Please post the same screenshot when they Family and instance are displayed and we can investigate further.

See the custom toggle example. https://wiki.universal-devices.com/UD_Mobile#Favorite_Examples Basically you want the "Display node to show the sensor and the "Command" to be a program you create which triggers the door. Or if the door only supports toggle, you can trigger the door directly in "Command".

We have a couple of reports of the same issue. We are still investigating.

Saving to the controller is on our list. UDM was built starting with ISY994 which could not handle saving the UDM configuration.

Some of the synch changed so possible app error. However more likely the NOde Server in slot 5 is not configured correctly.

Should be fixed in the latest release.

I think it may just be unintuitive, #71A6FA is not the default (ios version tint color) it is an example. Try pressing the delete button at the top of the color edit dialog.

Ok thanks for trying. Please open a ticket. Title it "Formatted values not in subscription, exists in Admin Console" Include your UUID, firmware version, and link to this topic.

Nothing to report, time constraints on my side. I don't work with Python or Node Server Development frequently so would likely need a few days to figure it out. With that said, it is open source so it can be modified/copied by anyone willing.

eisy. Formatted Status values are published by eisy, so it's not app related. Anytime a node server is installed a reboot is required before eisy will publish formatted values (this is written in the alert prior to synchronization). This was required in 994 due to lower processing/memory. Sometimes a node server reinstall/update will trigger this requirement. This requirement should finally be removed in firmware 6.0.0 If reboot does not correct the issue then there is another problem. The app will do a formatted status values lookup in dropdowns, so if dropdowns have formatted values and status does not (after reboot), then you may to open a ticket.

Not yet, we are in the process of migrating to new iOS APIs, but have not yet refreshed home/favorites screen. Should be fixed on some other screens.

Sorry, I think I misunderstood. Reboot should correct the issue. I believe reboot requirement for mapped status is removed firmware version 6.0.0

Ok, if it happens again please send me a copy of the backup file with the issue. There is no way for the nodes to be deleted in UDM aside from the scenarios I mentioned. UDM uses the same database tables for all controllers so corruption would have affected everything not a single controller. So aside from accidental delete there could have been a bug which prevented loading.

Not currently, but the Advanced Configurations will likely require an update soon due to some other changes, so I'll keep this in mind.

Not sure, configurations can only be deleted in 2 scenarios. The first is user deletes, the second is during cleanup after synchronization, in which case the app prompts for backup prior to delete. Since the app will not delete on it's own then, It's possible there was a bug which prevented display of some nodes, however this would be the first report. Maybe a pocket delete? UDM > Settings > Insteon > Cancel Discovery.

Was the Admin Console Restarted? Is it shown in UD Mobile?

Does synchronization correct the issue?

Please open a ticket and include your UUID. It is likely a calculation error somewhere, but I can't replicate on my side.

Please open a ticket and include your UUID and firmware version. Also test when enabling only using the Local Connection in Controller Settings > Local Connection Settings. Be sure to press the test button to be sure the credentials/ip/etc are correct. Does this have the same issue? This test will help us determine if the issue is isolated to remote connection.

Not currently as there is no position parameter in firmware. The Admin Console is also ordered alphabetically.

Not directly, but if you have an application with can call a url you can use the Portal Geofencing Node Server. The following link is how UDM can work with the Portal Geofencing Node Server. The NS can also be triggered with a portal URL, which is how 3rd party Geofencing works with eisy. https://wiki.universal-devices.com/UD_Mobile#Occupancy_v2.0_Node_Server I have played with iBeacons in the past as presence detection but it was too unreliable to triangulate using signal strength, but it may work if only requiring detection instead of triangulation.

Hi Bob, I don't follow exactly, but I think there is a simple solution. KPL buttons can not be controlled programmatically (unless it is the button with the load), they must be controlled from a scene. So, if I understand you want to issue a command to the scene, If this is true use type "Command" then for the command set the Scene to "ON". https://wiki.universal-devices.com/UD_Mobile#Favorite_Custom_Toggle With that said check out the 5.x fan example which simplifies KPL Buttons, so you only need 3 (high, med, low) and only one can be lit at a given time, pressing the lit button will turn the fan off. Then UD Mobile can control the fan module directly and the KPL Buttons will remain in sync. https://wiki.universal-devices.com/ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

Great, for reference the numbers 1:1,1 correspond to the module and port (blaster). Depending on your iTach version and number of ports and modules.