Version 1.0.2.22

  1. Fixed bugs in thermostat triggers.

Version 1.0.2.21

  1. Fixed bug where the thermostat state device was not getting updates.
  2. Fixed a bug where the the event/command threshold setting was not parsed correctly from the .ini file.
  3. Added a wait for response to query commands.
  4. Enhanced the "STATUS" class of messages so that all changes in device status should result in a log message.
  5. Enhanced the handling of device status web page buttons. These should now wait for a response from the ISY and update the status on the page after the button press.
  6. If you see a "*Warning*" message about multi-capability devices, please let me know. I have these printing to help me track down possible race conditions.

Version 1.0.2.20

  1. Fixed bug that would cause thermostat names to get corrupted if the device configuration page was used on a secondary thermostat device.
  2. Fixed device enable/disable bug when a device name matched a different device address/id.
  3. Added additional information for 501 errors returned from the ISY when trying to send a command. It now should list what was sent to the ISY to help with resolving these problems.
  4. Added events to track the event and command queue backlogs. If the backlog exceeds 10, an event will fire and output a log message.
  5. Improved the iMeterSolo output, it might be more correct now. Good news is that SmartHome shipped my iMeterSolo order today.
  6. Improved the status page reporting of device info.

Version 1.0.2.19

  1. Fixed bug that would cause thermostat names to get corrupted if the device configuration page was used on a secondary thermostat device.
  2. Fixed device enable/disable bug when a device name matched a different device address/id.
  3. Added additional information for 501 errors returned from the ISY when trying to send a command. It now should list what was sent to the ISY to help with resolving these problems.
  4. Added events to track the event and command queue backlogs. If the backlog exceeds 10, an event will fire and output a log message.
  5. Improved the iMeterSolo output, it might be more correct now. Good news is that SmartHome shipped my iMeterSolo order today.
  6. Improved the status page reporting of device info.

Version 1.0.2.18

  1. Fixed bug where programs were not respecting the auto-add setting and would always create HomeSeer devices.
  2. Fixed bug where the plug-in could use standard X10 house codes A-P for non-X10 devices if the A10/X10 module was in-use.
  3. Improved handling of device code allocation to better reused device codes.
  4. Improvements in iMeterSolo support (still incomplete)
  5. Removed support for non-specified thermostat set points. Early thermostat adapters supported a set point command/event that would flip between heat and cool depending on the thermostat mode. Current adapters support only individual heat and cool set points. This version will try to automatically remove the "- SP" thermostat device node.

Version 1.0.2.17

  1. Fixed bug in ISY Device Triggers. The trigger string getting passed to HomeSeer was incorrectly built so it would never match and thus never fire any ISY Device Triggers.

Version 1.0.2.16

  1. Fixed bug in device parsing. ISY device folders and parent folders were not getting set.

Version 1.0.2.15

  1. Internal code changes to ISY network communication layer.
  2. Cleaned up the trigger support and trigger strings. This version should automatically update existing triggers. Please verify that triggers are functioning as expected after upgrading to this version.
  3. Fixed bug that could cause a program crash when invalid data is used to send a command to the ISY.
  4. Fixed a bug in the thermostat Heat/Cool call secondary devices were not displaying the proper status.
  5. Fixed a bug in the SetIOEX API handler where it would crash the plug-in if the device passed in wasn't mapped to an ISY device.
  6. Added a drop down menu to the primary thermostat device to allow control over thermostat mode.
  7. Added a new web page specifically for thermostat status and control.
  8. Additional improvements to the iMeterSolo support. If you previously had iMeterSolo devices configured, you will need to go to the plug-in configuration page and use the "Update Device Types" button.

Version 1.0.2.14

  1. Updated to work with ISY firmware 2.8.10.
  2. Added additional support for iMeter-Solo devices. This is still a work in progress.

Version 1.0.2.13

  1. Fixed a bug in the command queue, if communication with the ISY was disrupted and a program command was sent, the plug-in would crash.
  2. Changed device drop downs in conditional triggers to include the device location along with the device name.
  3. Added a new log level called "Status". This is slotted in between Warnings and Notices. It logs device status changes along with Errors and Warnings. Note: if you were using log levels Notice or above, you'll have manually reset your log level.

Version 1.0.2.12

  1. Added conditional trigger support for scenes.
  2. Added basic support for iMeterSolo energy monitoring devices from SmartHome.
  3. Changed all device types generated by the ISYInsteon plug-in to be prefixed with "ISY" so that they don't conflict with generic device types or device types created by other plug-ins.

Version 1.0.2.11

  1. Fixed a bug that would cause the plug-in to go into an infinite loop if communication with the ISY is lost.

Version 1.0.2.10

  1. Fixed a bug where scenes created by the latest ISY firmware cannot be controlled.

Version 1.0.2.9

  1. Fixed bug where newly created scenes are not imported into the plug-in. This likely effects any scenes created using ISY firmware 2.8.0 or later.

Version 1.0.2.8

  1. Changed the custom device types, defined by the plug-in, to all be prefixed with "ISY " so they won't conflict with other standard or custom device types. To update your current ISYInsteon defined device types, use the "Update Device Types" button on the configuration screen.
  2. Added some debugging messages around group (scene) import from ISY.

Version 1.0.2.7

  1. Command queuing mechanism described above
  2. Enhanced the device trigger drop down selection boxes to display the full device name (name + path/folder info).
  3. Added a configuration option to set the HomeSeer device location and/or location 2 fields to a user defined text string. This string is applied to all device records owned by the ISYInsteon plug-in.

Version 1.0.2.6

  1. Changes to the network communication layer to provide better error reporting.
  2. Fixed a bug in the program conditions. They would only detect if a program was in the state true or false and ignore programs in the states "running true" or "running false". Now "running true" and "true" are considered true. "running false" and "false" are considered false.
  3. The Thermostat API now only reports the main thermostat device. The secondary (heat/cool/fan) thermostat devices are ignored by the API functions.
  4. When creating the HomeSeer records for a thermostat, the secondary devices are now treated as generic on/off sensors instead of thermostats. This doesn't effect existing installed thermostat devices.
  5. A log message that reported execution of program command was changed to output the full program name instead of the program ID.

Version 1.0.2.5 September 26th, 2010

  1. Fixed bug that would prevent the plug-in from sending program commands to the ISY.

Version 1.0.2.4

  1. Changes to the network communication layer to provide better error reporting.
  2. Changes to the network communication layer to provide better synchronization between device and program commands.
  3. Updated the device lists so that the latest Smarthome devices should now be recognized.

Version 1.0.2.3 September 11th 2010

  1. Updated to support the new data format for the ISY Brultech Energy Monitor module. This should not impact any existing triggers or conditions.
  2. Updated the device lists so that the latest Smarthome devices should now be recognized.

Version 1.0.2.1 July 5th 2010

  1. Fixed bug where newly added scenes could not be controlled until the plug-in was restarted.