Releases: rdmtc/node-red-contrib-sun-position
2.0.5: bug fixes
2.0.5: bug fixes
-
clock-time
-
blind-control
2.0.3: small fix + enhancement
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
-
blind-control + clock-time
2.0.0 / 2.0.1 major changes
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
- configurable
-
moon-position
-
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)
- blind-control
- 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
- this information will be send as
- 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
- this information will be send as
- 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
-
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
andignoreSameValue
#341 - for payload value make a deep clone as this could be any object and perform an an object comparison
- implement
-
time-comp
- added next occurrence #339
1.2.4: maintenance + critical bugfix
-
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
- for blind-control
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
- this information will be send as
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
- this information will be send as
- last data which contain data from the last evaluation (when the rules was last time evaluated) - #223
- added additional information in the output
-
blind-control only
- renamed
msg.resetOnSameValue
tomsg.resetOnSameAsLastValue
parameter to reset existing overwrite ifmsg.payload
equals to position (node.previousData.level
) (#223) - reordered evaluation of
resetOnSameValue
andignoreSameValue
- renamed
1.2.3: BugFix
1.2.2: BugFix
-
general
- internal object property
sunset
renamed tosunsetEnd
andsunrise
tosunriseStart
(#213). This leads into problems with backward compatibilities. In any select box wheresunset
orsunrise
is selected, it needs to reselect the right time.
- internal object property
-
blind-control + clock-time
1.2.1 rework
-
general
-
blind-control + clock-time
-
blind-control only
-
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
- redesign of the output, allows similar to the inject node set multiple properties
-
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
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
-
blind-control + clock-time
-
blind-control only
-
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
- redesign of the output, allows similar to the inject node set multiple properties
-
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
-
general
- replaced some png type graphics with svg
-
time inject
-
blind-control + clock-time
-
clock-time
- fix that overrides with value false or 0 does not work #186
1.1.6: BugFix
- general
- reworked JSONATA (preparation is now done on node creation)