Release v2.2.0

Changes

• Updated @clarify/api to 0.3.0

v2.1.0

New features

• Support for including enumValues is restored.
• Added new payload formats: You're now allowed to send in just a number as the payload, an object containing a time and a value, or the existing format, an object with two arrays with times and values.
• Allow setting valueType on the signal. type is being renamed to valueType on the API. We will be trating type as an alias for valueType.

v2.0.0

Breaking changes

• Remove override fields from clarify-api node. You can only configure it using a credentials file.
• All input errors are now catchable, and won’t be send through the wire if the request fails.
• The clarify_insert node no longer has an output, all errors are catchable using an catch block.
• Remove support for Node 12
• Moved packaged from @searis/node-red-contrib-clarify to @searis/node-red-contrib-clarify.
  • We’ll continue to publish the old package for the lifetime of the v2, but we’ll deprecate it.

Release v2.0.0-beta.1

First beta of v2

Breaking changes

• clarify_api node only supports client credentials file for authentication. All override fields has been removed.
• Errors are no longer being sent as an output, they are only sent as an error, and can be handled using a catch node.
• Drop support for Node 12 and older
• Drop support for Node Red v1
• Output matches API responses for Integration.insert and Integration.saveSignals

Other change

• clarify_insert node has a new appearance

v1.0.2

What's Changed

• Validate input id using new less strict requirements by @mogstad in #53