Skip to content

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

1.0.12: BugFix + enhancement

07 Mar 13:24
30edcb9
Compare
Choose a tag to compare
  • general
    • BugFix: Allow 0 as value for any time input, mainly for time-compare or time-span node, but affects potentially all nodes.
    • BugFix: random offset #90 now working as expected
    • BugFix: node error output for time input if time can not be evaluated has missing original message.
    • prepared new Node interval-inject (not finished, not available) - is the same as standard node-red inject node for intervals with start and end of interval able to use sun-times.

enhancements

  • Blind-control allows now granular settings of topic
  • documentation enhanced for clock-timer and general

1.0.11: enhancement

27 Feb 21:35
01fa934
Compare
Choose a tag to compare

1.0.11: BugFix + enhancement

  • general

    • hopefully fixed #102 - massive changes in the library with cleanup lot of functions
      • maybe fixes also #98
    • fixed and reworked caching of calculated sunTimes, MoonTimes
  • blind-control + clock-time

    • documentation + i18n
    • add start delay setting where a time can be defined where no output
      • if in startup delay, the reason code is set to NaN and node state, reason description stated that node is in startup
    • after startup delay ended default output will be send (due to reason code change)
    • implement #92 additional date restriction
  • time-inject

    • fixes that time inject will do a recalculation every 1 ms (Problem can only occurs if the time constraints are used.) #106
    • implement #92 additional date restriction
  • within-time

    • implement #92 additional date restriction
  • sun-position + moon-position

    • implements #81 - now it is possible to have msg.latitude and msg.longitude (or msg.lat and msg.lon) to override settings in configuration node. The configuration Node still needs to be configured properly.

bug fix (only an test release)

22 Feb 22:26
a457ac2
Compare
Choose a tag to compare
Pre-release

1.0.10: bug fix

  • general

  • sun-position + moon-position

    • implements #81 - now it is possible to have msg.latitude and msg.longitude (or msg.lat and msg.lon) to override settings in configuration node. The configuration Node still needs to be configured properly.

1.0.9: bug fix

  • general

    • fixed #102 again - massive changes in the library with cleanup lot of functions
    • fixed and reworked caching of calculated sunTimes, MoonTimes
  • blind-control + clock-time

    • documentation
    • if in startup delay, the reason code is set to NaN and node state, reason description stated that node is in startup
    • after startup delay ended default output will be send (due to reason code change)
  • clock-time

    • additional to reason or rule change, the payload will also output on these changes
      • if type of payload has changed
      • if payload is of type string, number or boolean and value of the payload has changed
        • changes on arrays, objects will not detected

1.0.8: bug fix

  • time-inject

    • fixes that time inject will do a recalculation every 1 ms (Problem can only occurs if the time constraints are used.) #106
  • blind-control + clock-time

    • documentation
    • i18n

1.0.7: bug fix

  • general

    • added additional caching of sun times calculation to reduce calculation load
  • blind-control + clock-time

    • fixed start delay setting causing no output at all
    • i18n, spelling, documentation

1.0.6: bug fix

  • general

    • fixed #102 - nodes calculate wrong sun times
      • this happend between midnight - TimezoneOffset to midnight
      • maybe fixes also #98
    • fixed broken rule check for time-span #103
  • blind-control + clock-time

    • first implementation of #92 (needs more test)

1.0.5: bug fix

  • blind-control + clock-time
    • add start delay setting where a time can be defined where no output

1.0.4: bug fix

28 Jan 13:23
7acf1d2
Compare
Choose a tag to compare
  • within-time-switch
    • fixed error day selection #100
    • fixed wrong working month selection
  • sun-position
    • added lastUpdateStr to payload to get the original calculation base time
  • moon-position
    • added lastUpdateStr to payload to get the original calculation base time

1.0.3: bug fix

19 Jan 16:04
c0ff608
Compare
Choose a tag to compare
  • blind-control
    • fixed maximum rules #96

1.0.2: bug fix

09 Jan 19:57
ae936b5
Compare
Choose a tag to compare
  • time-comp

  • general

    • added random offset (not fully tested) #90
    • Improve display of days of the week and months (first try) #91

1.0.1: bug fix

03 Jan 22:53
73a8c9c
Compare
Choose a tag to compare
  • time-inject
    • fix downward compatibility for older node settings

1.0.0: mayor release

02 Dec 22:03
70e5d58
Compare
Choose a tag to compare
  • new Node: clock-time

    • This is a simplified blind-control node, with only time rules and any payload.
    • it is ideal for dimmers, Christmas lights, ...
  • time-inject

    • added month selection
    • added even/odd day selection
  • within-time

    • added day selection
    • added month selection
    • added even/odd day selection
  • blind control

    • added day selection to rules
    • added month selection to rules
    • added even/odd day selection for rules
  • general

    • added on several settings the possibility to use payload if the topic of an incoming message contains special value.
    • fixed smaller problems
  • The big jump in the version number is not due to the amount change, but rather other reasons.

    • The Version starting with 1... will show that this node is tested and working with Node-Red above 1...
    • After this release, no major changes are planned in the next time and the node is for the time being feature complete. This fits a version number 1... better than 0...

0.5.4 BugFix

20 Nov 15:42
ca227f8
Compare
Choose a tag to compare

additional fix for #68

0.5.3: BugFix

14 Nov 12:32
c9cd9c9
Compare
Choose a tag to compare