Skip to content

getSunCalc log-message incorrectly placed in INFO-scope #558

@hans-fischer

Description

@hans-fischer

Hello together!

Describe the bug
I'm using more than one sun-position node. And they seem to share a inner state.
So with more than one sun-position, I'm getting a lot of those logs:

29 Oct 09:49:06 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation
29 Oct 09:49:06 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation
29 Oct 09:49:16 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation
29 Oct 09:49:16 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation
29 Oct 09:49:26 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation
29 Oct 09:49:26 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation
29 Oct 09:49:36 - [info] [position-config:wds18] getSunCalc, time difference since last output to low, do no calculation

The problem is not that the plugin saves cpu-cycles, the problem is the logging.
I mean, its INFO and to have my container logs full of those has no informational value for me.

Could you please put that log into DEBUG?

Expected behavior
I expect my container logs to only contain relevant runtime information. To have the same log over and over again without any impact to my runtime is not helpful and distract from important issues.

System information (please complete the following information):

  • Node-Red Version: 4.1.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions