-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
outcome not in line with expectations (1 hour off) #12
Comments
It does not seem you are doing anything wrong, but the plug-in is doing something wrong. |
The only way I know of to debug is to run it in the HASS development environment. Once you find the guide it's quite easy to follow and setup, and integrates well with VS Code. |
Hi. Found your custom HACS integration and found it very cool. Thanks for your job! :) |
After fixing #13 in #14 I also found a spot in prices to try to reproduce this issue but seem to function as expected, could be that #14 fixed this one as well. Please update to v.0.2.3 and see if you agree.
Ignore noise in binary sensor history graph before 13:30 as that was during my testing of other prameters |
Hi. Nordpool Data:
My binary sensor:
My expectation is, the binary sensor activate at 3am and ends at 5am. Maybe you have an idea how to solve it? Kind regards. |
Good morning. I would be pleased to receive a reply. Best regards
|
Good morning. Do you have any ideas to solve this? Thanks in advance,
|
Hi, have not really thought of negative prices until now. Spontaneously I would say it should work just fine, but apparently there is something strange happening.
One could try to allow negative range but specially the ACCEPT_RATE I'm not so sure how large negative value must be allowed. In the example from 2023-12-29 it should not activate until the two [-0.093, -0.095] 03:00 and 04:00 (which has the lowest average in the up to 24h span ahead). On the other hand it should likely not switch off when that time has passed as the "moving 24h" only looks at prices in the future. So at 07:00 when the price is -0.001 it's still the cheapest looking in the future. |
Hello, |
With release of version 2 #45 I'm closing this as the code is completely rewritten. But feel free to reopen or create new issue if similar problem is still seen. |
Hi, I have been playing around with the tool for a few days and found that the outcome is not optimal, eg. in this case one hour off; what's the best way to debug?
I want the start time for the cheapest 4 hour period in a max 24 hour time horizon (rolling) - based on the nordpool sensor my binary planning sensor generates 19:00 with an average cost of 41cents [calculation is correct adding up 19 - 23pm / 4]; however, starting one hour later (20:00) would generate a lower average of 35cents. Any thoughts what I am doing wrong?
YAML code:
Used nordpool data:
The text was updated successfully, but these errors were encountered: