We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug node-red-contrib-sun-position for NodeRED
Inject enhanced gives out the wrong date. Take a look at the screenshot.
Screenshots
If i take the "timestamp"-option from this node is gives out the right date.
System information (please complete the following information):
Additional context Found out something interesting: check this out. Configs:
When i use that extra option it give out the right date sometimes :D I injected serveral times in row.
If you add 1 sec it gives out the right one every time. Any idea why that happens :D? The conifg is on my timezone.
The text was updated successfully, but these errors were encountered:
time-inject fix for next property #364
53a4206
fixed with 2.0.6
Sorry, something went wrong.
Hypnos3
No branches or pull requests
Describe the bug
node-red-contrib-sun-position for NodeRED
Inject enhanced gives out the wrong date. Take a look at the screenshot.
Screenshots

If i take the "timestamp"-option from this node is gives out the right date.
System information (please complete the following information):
Additional context

Found out something interesting: check this out.
Configs:
When i use that extra option it give out the right date sometimes :D
I injected serveral times in row.
If you add 1 sec it gives out the right one every time.
Any idea why that happens :D? The conifg is on my timezone.
The text was updated successfully, but these errors were encountered: