Skip to content

Releases: rdmtc/node-red-contrib-sun-position

2.0.5: bug fixes

13 Nov 13:40
23285eb
Compare
Choose a tag to compare

2.0.5: bug fixes

  • clock-time

    • fix of check if payload and topic has changed to prevent send output on not changed payload/topic to output 1 #360
    • fix of not changeable context store #358
  • blind-control

    • fix of not changeable context store #358
    • fix of not working '0' value for setBlindSettingsTop, setBlindSettingsBottom, setBlindSettingsIncrement and setBlindSettingsLevel config overwrite possibility #359

2.0.3: small fix + enhancement

07 Nov 23:52
1b38b0b
Compare
Choose a tag to compare

2.0.3: small fix + 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 versions below 2.0.0 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!

See https://github.com/rdmtc/node-red-contrib-sun-position/releases/tag/2.0.0 for all changes made in 2.0.0.

  • general

    • allow to set context store in configuration node #351
    • fixed randomNumber cached again #302 + #353
    • selectable range for random number #352
  • blind-control + clock-time

    • allow to set context store, if not defined using settings from configuration node, otherwise default #351
    • readjusted rules UI, edit buttons only visible on mouse over
    • allows to enable/disable rules #349

2.0.0 / 2.0.1 major changes

13 Sep 20:25
Compare
Choose a tag to compare

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

1.2.4: maintenance + critical bugfix

20 Feb 14:33
a8b7716
Compare
Choose a tag to compare
  • time-span

    • fixed bug that second operand displayed wrong in config!
    • fixed critical output bug #240
  • blind-control + clock-time

    • added additional information in the output
      • last data which contain data from the last evaluation (when the rules was last time evaluated) - #223
        • for blind-control msg.blindCtrl.lastEvaluated.sunLevel, msg.blindCtrl.lastEvaluated.ruleLevel, msg.blindCtrl.lastEvaluated.ruleTopic, msg.blindCtrl.lastEvaluated.level, msg.blindCtrl.lastEvaluated.ruleId
        • for clock-time msg.timeCtrl.lastEvaluated.payload, msg.timeCtrl.lastEvaluated.topic, msg.timeCtrl.lastEvaluated.ruleId msg.timeCtrl.lastEvaluated.ruleTopic
      • msg.blindCtrl.name / msg.timeCtrl.name which is the name of the node (or the id if no name is given in the config) - #238
        • this information will be send as msg.payload.name to the second output if two outputs are configured
      • msg.blindCtrl.id / msg.timeCtrl.id which is the id of the node
        • this information will be send as msg.payload.id to the second output if two outputs are configured
  • blind-control only

    • renamed msg.resetOnSameValue to msg.resetOnSameAsLastValue parameter to reset existing overwrite if msg.payload equals to position (node.previousData.level) (#223)
    • reordered evaluation of resetOnSameValue and ignoreSameValue

1.2.3: BugFix

15 Feb 19:52
25b592e
Compare
Choose a tag to compare
  • within-time-switch
    • fix bug that time limitations does not work #236 upstream of #192)

1.2.2: BugFix

14 Feb 20:00
bc14a54
Compare
Choose a tag to compare
  • general

    • internal object property sunset renamed to sunsetEnd and sunrise to sunriseStart (#213). This leads into problems with backward compatibilities. In any select box where sunset or sunrise is selected, it needs to reselect the right time.
  • blind-control + clock-time

    • fix that note settings overwrite by message and payload does not working #233
    • fix bug with missing function #223

1.2.1 rework

14 Feb 10:14
0842bf0
Compare
Choose a tag to compare
  • general

    • changed several links to documentation #151
    • replaced all remaining png type graphics with svg
    • added examples
    • minor bug fixes (#196, )
  • blind-control + clock-time

    • Standardization and consolidation of the same and similar functions #186
  • blind-control only

    • for Blind control the current used mode as operator (#197)
    • add a msg.resetOnSameValue parameter to reset existing overwrite if msg.payload equals to position (node.previousData.level) (#223)
  • time inject

    • fixed bug, that interval between times does not start when load node and time in in the interval #189
    • smaller changes which leads into more options for outgoing data
  • time-comp

    • redesign of the output, allows similar to the inject node set multiple properties
      • so the node becomes like a kind of a change node
  • time-span

    • redesign of the output similar as time-comp
  • within-time-switch

    • allows to have setup the time limitation also by msg, flow, global or env variable. #192

1.2.0-beta2 rework

15 Nov 16:42
1570a2b
Compare
Choose a tag to compare
1.2.0-beta2 rework Pre-release
Pre-release

Unfortunately this release is not finished yet and only released as beta. Unfortunately, due to external influences, I am currently unable to continue working here.

  • general

    • changed several links to documentation #151
    • replaced all remaining png type graphics with svg
    • added examples
    • minor bug fixes (#196, )
  • blind-control + clock-time

    • Standardization and consolidation of the same and similar functions #186
  • blind-control only

    • for Blind control the current used mode as operator (#197)
    • add a msg.resetOnSameValue parameter to reset existing overwrite if msg.payload equals to position (node.previousData.level) (#223)
  • time inject

    • fixed bug, that interval between times does not start when load node and time in in the interval #189
    • smaller changes which leads into more options for outgoing data
  • time-comp

    • redesign of the output, allows similar to the inject node set multiple properties
      • so the node becomes like a kind of a change node
  • time-span

    • redesign of the output similar as time-comp
  • within-time-switch

    • allows to have setup the time limitation also by msg, flow, global or env variable. #192

to test this version:

Installation over the Node-Red GUI will not work, because tagged as a beta release

Install of this version in Node-Red:

  • change to the installation directory of Node-Red
  • enter the command npm install node-red-contrib-sun-position@1.2.0

Install of this version in a Homematic:

  • logon with ssh
  • enter the commands:
    • source /usr/local/addons/redmatic/home/.profile
    • cd /usr/local/addons/redmatic/var
    • npm install --save --no-package-lock --global-style --save-prefix="~" --production node-red-contrib-sun-position@1.2.0

To go back to the previous version you must do the same as above with the difference instead of node-red-contrib-sun-position@1.2.0 enter node-red-contrib-sun-position@1.1.7.

1.1.7 BugFix

13 Sep 15:24
eac653a
Compare
Choose a tag to compare
  • general

    • replaced some png type graphics with svg
  • time inject

    • fix missing data property name. #185
    • fix not working offset #181 #182
  • blind-control + clock-time

    • prevent irrelevant error when no rule with time constraint exists. #180
    • fix that autotrigger time from configuration is not used #186
  • clock-time

    • fix that overrides with value false or 0 does not work #186

1.1.6: BugFix

28 Aug 18:40
1eb7ac0
Compare
Choose a tag to compare
  • general
    • reworked JSONATA (preparation is now done on node creation)