Jump to content

Javi

Employees
  • Posts

    2082
  • Joined

  • Last visited

About Javi

Profile Information

  • Location
    Denver, CO

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Javi's Achievements

Advanced

Advanced (5/6)

1.1k

Reputation

169

Community Answers

  1. 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".
  2. We have a couple of reports of the same issue. We are still investigating.
  3. Saving to the controller is on our list. UDM was built starting with ISY994 which could not handle saving the UDM configuration.
  4. Some of the synch changed so possible app error. However more likely the NOde Server in slot 5 is not configured correctly.
  5. Should be fixed in the latest release.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. Sorry, I think I misunderstood. Reboot should correct the issue. I believe reboot requirement for mapped status is removed firmware version 6.0.0
  12. 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.
  13. Not currently, but the Advanced Configurations will likely require an update soon due to some other changes, so I'll keep this in mind.
  14. 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.
  15. Was the Admin Console Restarted? Is it shown in UD Mobile?
×
×
  • Create New...