npm node-red-contrib-sun-position 1.2.4
1.2.4: maintenance + critical bugfix

latest releases: 3.0.0-alpha1, 2.2.0-beta3, 2.2.0-beta2...
3 years ago
  • 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

Don't miss a new node-red-contrib-sun-position release

NewReleases is sending notifications on new releases.