Releases: rdmtc/node-red-contrib-sun-position
Releases · rdmtc/node-red-contrib-sun-position
0.5.2: BugFix
- general
- fix for error on getting tooltip #69
0.5.1 BugFix and Maintenance Release
0.5.1-beta: BugFix and Maintenance Release
- general
- fix for week number calculation when in daylight saving #65
- if time output as object the week is now an extra object with properties
- iso Array
[year, week]
- week Number week number
- year Number full year
- even Boolean is true if week is even
- iso Array
- blind control
- fix for #66 if the blind not uses values between 0 and 1
- fix for #67 mixed earliest and latest settings
- enhanced output of the rules
- change logic of rule execution: From rules within Until rules will now considered.
- change should have no affect if rule setup is equal to the examples, that time restricted rules separated in first only until and afterwards only from rules
0.5.0 mayor release for blind control
-
configuration
- switched latitude and longitude and added openstreetmap link/map for the position to prevent issues caused by latitude and longitude (maybe cause of #55)
- added german translation for latitude and longitude
-
time inject
- added output of week number to enhanced date output
- enhanced name output for enhanced date output
-
sun-position
- fixed #52 bug with implementation
- added
positionAtSolarNoon
as additional payload property with the position data of the sun at solar noon
- added
- fixed problem with
msg.ts
not considered as used timestamp
- fixed #52 bug with implementation
-
moon-position
- fixed problem with
msg.ts
not considered as used timestamp
- fixed problem with
-
blind control
- fixed #61 by removing misleading angle
- fixed #62
setMode
can now deactivate sun control - added
resetOverwrite
additional property #54 - add possibility to have a exact priority comparisons (e.g. only reset a specific priority)
- redesigned rule input by dialog
- removed previous reset option for level operator, will now be done by new special level type
- added new type of Level:
NotDefined
, where for absolute rules default or sunControl will be used and for min/max the rule will be reset.- This will allow to have only one type of time rules (until/from) which could cover whole day.
- Hopefully this makes rules easier.
- added per rule two different times and two different conditions
- allows to define more scenarios
- allows to reduce amount of needed rules.
0.4.10: critical bug fix
- fixed bug #57 with the code prepared for Node-Red 1.0. The recommend way for be backward compatible doesn't work. This is also confirmed by @knolleary.
0.4.9: small enhancement
- implemented #52 as height of the sun in the sky in percent (0~100 with 100% being at solarnoon and 0% being completely down) - altithudePercent
- fixed bug for #53, no longer send blind position in override mode
- updated dependencies
- more changes for node-red 1.0 (https://nodered.org/blog/2019/09/20/node-done)
- added node-red 0.19.0 as required version
0.4.8 - Maintenance
- added 'triggerOnly' posibility - fixes #48
- updated dependencies
0.4.7 - BugFix Release
- fix problems
- if time tooltip has wrong format
- if not initialized
- on exception get backend data
0.4.6 Maintenance
- time-comp
- fixed css for multiselect in node-red Beta
- added tooltip for time select fields
- time-span
- added tooltip for time select fields
- enhanced readme and added links to changelog #43
0.4.5
0.4.4
- fixed critical problem in sun - calculating Julian cycle which leads into wrong sun times if it is calculated at certain times
- fixed problems on RedMatic call of getBackendData
- tooltip with resolved time on typeInput now also available in RedMatic
- i18N reworked
- for compares using mathematical signs for equal, unequal, greater than, less than
- added more Unicode symbols
- added direct moon phase output
- added compare to current moon phase for conditions
- blind control
- fixed error on empty ruleset
- add clear button for rules
- add sort button in UI editor
- reworked minimum/maximum blind position settings by rule, enhanced in documentation
- addresses #36
- enhanced documentation
- added possibility for inverted open / close settings #40
- changed lot of internal
- cleanup procedures
- fixed problems with test function #32
- optimized code to ES6 possibilities
- changed esLint rules to be more restrictive
- fixed a lot of wrong usages of arrow function for data validation
- optimized access to backend services
- changed lot of UTC time compare problems #34