-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
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
Lowest price always sends on/true until first period #184
Comments
Exported the nodes in question, just in case:
|
I noticed when using "Deploy" i often get errors from the Lowest price-node: |
I notice this in your config: If you have it configured, you could try to set contextStorage to About the Edit: I wrote |
But this whole thing is triggered by the event state node for my nordpool sensor. Why would it not have price data? |
The errors come when the node starts up. That is before any input. Initial output is also set then. |
(Thank you for spending time on helping me out here, I really appreciate it!) Then why is the schedule still wrong when the next hour and price change comes? |
Now I see your point. I think that is a bug. Thanks to your input I have been able to create a test, currently failing. I will try to find time to fix it soon. Thank you for reporting. |
I have found a bug and I will publish a fix soon (in v 4.1.5). (I have edited my comment above about this value. I wrote The bug was that the schedule continued to be on after 05, but since that is outside the planning period, your |
Updated to 4.1.5 and Also: If i try to update the schedule after 13 (that's when nordpool releases prices for the next day) I do have price data for my whole period (20-05), shouldn't that work? |
I must see the output to be able to evaluate the case. If you have data for today and tomorrow, you can see the schedule for tonight, but not for tomorrow night. |
Lowest Price node
The schedule generated after a reboot sets output to on/true even though I have set "Outside Period, Send: Off". After the first period has started everything works as expected until i restart Node Red.
I don't think this is because of missing data right after restart since schedule is updated on the hourly price changes and it still looks the same until first period started.
Adding output below. Note this is generated at 16.08PM. The first schedule row I would expect to have value:false. The schedule for tomorrow looks as expected (off between 05.00 - 20.00).
The text was updated successfully, but these errors were encountered: