Skip to content

Releases: billchurch/indigo-elk-m1-plugin

2.0.3

14 May 11:53
9fca2a8
Compare
Choose a tag to compare

Added

  • New device for temperature sensors (type 33), and sending the st / receiving the ST messages to update them.

2.0.2

26 Dec 17:48
Compare
Choose a tag to compare

Added

  • ELKRP Connected (RP) and Installer Program Mode Exited (IE) messages

Changed

  • self.runstartup was mentioned throughout the plugin previously, which did not exist, corrected to self.startup.
  • Added start of communications error recovery. Plugin will now attempt to restart itself in the event of timeouts or loss of communication to the M1-EXP.

2.0.1

16 Dec 00:09
Compare
Choose a tag to compare

Breaking changes

Upgrading from versions older than 2.0.0

  • This uses a new CFBundleIdentifier, as a result devices discovered or created in versions prior to this release (2.0.0) are incompatible.
  • Disable previous Elk Plugin
  • Delete previous Elk Plugin -- remove from: /Library/Application Support/Perceptive Automation/Indigo 7/Plugins (Disabled)
  • Document and then delete any triggers, scripts, or devices that were made in version prior to v2.0.0
  • Install new plugin
  • Re-create triggers, scripts, or devices with new v2.0.0.
  • In theory, going from pre-2.0.0 to 2.0.0 will be the only time this should occur, and future upgrades will not have this issue.

Changes

  • Reformatting of XML
  • Reformatting of Python to conform to PEP 8 Style Guide
  • No functionality changes

Initial Release

15 Dec 21:51
Compare
Choose a tag to compare

Breaking changes

Upgrading from previous versions

  • This uses a new CFBundleIdentifier, as a result devices discovered or created in versions prior to this release (2.0.0) are incompatible.
  • Disable previous Elk Plugin
  • Delete previous Elk Plugin -- remove from: /Library/Application Support/Perceptive Automation/Indigo 7/Plugins (Disabled)
  • Document and then delete any triggers, scripts, or devices that were made in version prior to v2.0.0
  • Install new plugin
  • Re-create triggers, scripts, or devices with new v2.0.0.
  • In theory, going from pre-2.0.0 to 2.0.0 will be the only time this should occur, and future upgrades will not have this issue.

Changes

  • Initial Release
  • Reformatting of XML
  • CFBundleIdentifier
  • Addition of CFBundleName
  • Increment Version
  • Change CFBundleURLName