node-red-contrib-sun-position 2.0.0

2.0.0 / 2.0.1 major changes

on Node.js NPM

2.0.0: enhancement

⚠ Warning: This Version could break existing flows. Please check your configuration!

🛑 Nodes (especially blind, time-control nodes) that were created or saved with this version do not work in older versions of the package. This affects the export / import of flows and when switching to an older version. It is therefore essential to create a backup before upgrading to this version!

• general

  • added only even and only odd weeks
  • added css property to moonPhases object an using css from here
  • for offset values of a random number a cached value will be used which will be only generated once per day. #302
  • selection of random number is available in more places
  • allow negative altitudePercent #259

• time-inject

  • fixed error if only flow/global context is set #252
  • fixed missing interval multiplier
  • added possibility for inject special values from config menu like default inject node
  • reworked simple interval (only simple interval)
    • added start timestamp
    • added selection for interval of days and weeks #313
    • added possibility to setup interval greater than 24.9 days (2147483647 - 32bit integer limit of NodeJs)

• within-time-switch

  • configurable msg.payload of the outgoing message #292

• moon-position

  • moon times will now be has additional property timesNext with the values for the times of the next day #307
  • added next moon phase date time #296

• blind-control + clock-time

  • added possibility to copy rules to clipboard and paste rules from clipboard
  • nodes have now always 2 outputs - may breaks existing flows!
    • First output is configurable.
  • redesigned rule conditions, now unlimited conditions could be defined
  • additional nodeID which will be also in the output (if set will override nodeId)
    • added as rule condition operator - usable in subFlows
  • No more messages are sent at the first output if the rule has changed but the payload (level/slat) has remained the same.
    • A message will be sent if the topic has changed.
  • overwrite will be written to node context and restored on recreation - allows overwrite be stable on deploy #300
  • No longer configuration of number of outputs. Node will always have two outputs
    • The message send to the first output will no longer be send on rule change, only on level/payload changes.
    • The message on the first output is fully configurable.
    • A property can be setup to be a string with placeholders. (The same placeholders can be used for the topic.):
      • blind-control
        • %name% - name of the node
        • %id% - ID of the node
        • %level% - level
        • %levelInverse% - level, but inverse
        • %slat% slat position
        • %code% - node.reason.code,
        • %state% - node.reason.state,
        • %description% - node.reason.description,
        • %rule% - ID of the active rule (if rule was active)
        • %mode% - current mode
        • %topic% - msg.topic of the incoming (trigger) message (if available)
        • %payload% - msg.payload of the incoming (trigger) message (if available)
      • clock-timer
        • %name% - name of the node
        • %id% - ID of the node
        • %code% - node.reason.code
        • %state% - node.reason.state
        • %description% - node.reason.description
        • %rule% - ID of the active rule (if rule was active)
        • %topic% - msg.topic of the incoming (trigger) message (if available)
        • %payload% - msg.payload of the incoming (trigger) message (if available)
  • The name of the node (or the id if no name is given in the config) can be configured in the output message - #238
    • this information will be send as msg.payload.name to the second output
  • ID of the node can be send
    • this information will be send as msg.payload.id to the second output if two outputs are configured
  • blind-control only changes
    • redesigned oversteer, now unlimited oversteer can defined
    • oversteer can be defined only valid for special mode
    • removed minimum altitude settings
      • for functionality the downward compatibility is given by automatic adoption of the setting as new first oversteer, which has the same effect.
      • no longer specific output of the reason (instead of "below the minimum elevation angle" will output "oversteer 1")
    • window settings as typedInput, which allow to use from flow, global context or environment - node can better used in a subFlow
    • per message set mode will be written to node context and to thus this will be stable on deploy
      • needs to delete values of context on change
    • current mode will no longer part of the node label/name, it will be displayed in the node state #321
    • added option to setup a rule which prevents the node to send anything out #280

• time compare and change + time span

  • fixed parsing of ECMA-262 (simplified ISO8601) Format times (e.g. 2021-05-17T08:45:00.000Z) #250
  • added parsing of full ISO8601 Format (e.g 2019-01-18T00:00:00.000Z, 2019-01-17T17:00:00.000-07:00, 2019-01-18T07:00:00.000+07:00)

2.0.1: BugFix + enhancement

• general

  • implemented partly #338 + #308
  • fixed randomNumber cached #302
  • implemented randomNumber cached weekly

• blind-control

  • allow to setup a rule which will only overwrite slat #345 or topic
  • enhanced overwrite possibilities for slat. Additional msg.blindSlat as message property allowed or if the topic contains __slatOverwrite __ the payload as slat position will be used - partly #346
  • for slat value make a deep clone as this could be any object and an object comparison

• clock-time

  • implement resetOnSameAsLastValue and ignoreSameValue #341
  • for payload value make a deep clone as this could be any object and perform an an object comparison

• time-comp

  • added next occurrence #339