ISY-26 Insteon:Release Notes 2.5

From Universal Devices, Inc. Wiki

For Release 2.5 (RC1)

Fixes

  • Fix: Schedule 'Time is' entries run intermittently
  • Fix: Cannot enable programs
  • 'Replace Device' now updates all remoteLincs first
  • 'Replace Device' does not require exact device type/subtype match
  • 'Restore Device' now removes links to unknown devices
  • 'Restore Device' now removes duplicate links
  • 'Restore Device' now moves keypad led links to front of link database
  • 'Restore Device' now ensures link to PLM for responder only devices
  • Less aggressive network crawl (now ignores inactive links)
  • Missing PLM links added when device added to ISY
  • For Linux, Log can be saved to filesystem
  • Updated User Guide


Features

  • Detailed progress in Java console for long running commands (Restore Devices, etc.)


Known Bugs

  • None


For 2.4.15

Fixes

  • Or (...)/And (...) logic in programs
  • 'New Insteon Device' now removes old links immediately (as currently done if linked instead)
  • Sunset/Sunrise now recalculated at DST changeover
  • Device now working correctly after 'Replace Device'
  • Move 'True/False' to own column in Program Summary
  • Widen h/m/s input dropboxes (showed '...' in some browsers)
  • Proper file cleanup when removing a device from ISY and device communication fails.
  • Device firmware levels in GUI
  • Regression: ELK/Notification setting are not saved
  • Progress bar when saving programs
  • Sunrise/set "Same Day" now working correctly when the From is a fixed time or lastrun time, and the To is a sunrise/set.


Known Bugs

  • Documentation is still at 2.4 level


For 2.4.13

Fixes

  • Overwrite existing links now immediately overwrites links when the device is added
  • 00 in the middle of Insteon address
  • Removed notification settings from Configuration tab
  • 'Repeat 0 times' entry fixed
  • Program Summary shows True/False state of programs
  • Various minor bug fixes


For 2.4.12

Fixes


New Triggers/Schedules

  • 'On Never' schedule entry fixed (no longer hangs the box)
  • AM/PM in Summary table displays and sorts correctly
  • Changes to 'Run at Reboot' automatically updated in summary screen


For 2.4.11

Fixes

  • Last run times would show 00:00:00


Enhancements

  • Show [Applied Locally], in Red for local scene controllers
  • Maintain the state of program GUI
  • Added "Run at Bootup" to address the power failure issues
  • Retain combobox values between Status/Control


For 2.4.10

Fixes


New Triggers/Schedules

  • Newlines preserved in Program Comment field
  • 'Finally' replaced by 'Else'; semantic difference is 'Else' runs independent of whether 'Then' ran
  • Fixed program true/false status, and various logic bugs in programs.
  • Added 'is not received' to X10 conditions
  • Keypad buttons available in Status conditions and actions
  • Log key presses/X10 messages received to the java console (turned on/off in the shell)


For 2.4.9

Fixes


Main Application

  • INSTEON address is now shown on the Device View next to Device Type
  • Now, the same on level and ramp rate can be applied to all the devices within a scene


New Triggers/Schedules

  • Clicking on 'New Folder', now uses 'New Folder' as default name instead of 'New Program'.
  • 'My Lighting' now included in drop down lists
  • Fix for non-toggle buttons. An event occurs whenever a button is pressed (i.e. not just when the current value of the button changes)
  • Configuration fix for Relay devices; now allows Fast On/Off etc.
  • Node combo boxes widened to accomodate long names
  • Schedule migration no longer turns lights Off instead of On
  • Copy readable contents of program to clipboard
  • Copy program
  • Program tree has popup menu
  • Fix for box hanging when deleting all contents of a folder and the folder itself
  • Fix for intermittent save/delete program errors
  • Fix for null references to programs and nodes within a program


Regression

  • Fixed not being able to change the userid/password
  • Removing devices from a scene, left residue and in some cases the device would still respond to commands from the scene it previously belonged to