Comments (17)
from pv_opt.
from pv_opt.
I can't see these logs for some reason. Could you please re-upload? Thanks
from pv_opt.
Odd, just downloaded and re-uploaded them.
Since updated to 3.14.9 and indeed that seems have addressed it to some extent
from pv_opt.
Seeing similar too, but also a closed issue resurfaced in 3.14.9 (I've added logs).
Thanks.
from pv_opt.
My battery is predicted to be flat at 23:00 and OE tariff showing cheaper slots before 05:00 when the price then ramps up. Notice it isn't showing the optimised blue trace line.
from pv_opt.
from pv_opt.
Try changing the “pass threshold” to zero
On 26 May 2024 at 17:22 +0100, solarjones @.***>, wrote:
error.log
main.log
pv_opt.log
My battery is predicted to be flat at 23:00 and OE tariff showing cheaper slots before 05:00 when the price then ramps up. Notice it isn't showing the optimised blue trace line.
image.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
Unsure which parameter that is as I don't have that?
from pv_opt.
@solarjones it's the "charge threshold" in the bottom of the dashboard. By default it's 4
from pv_opt.
Its called "Charge Threshold" on the dashboard
from pv_opt.
@solarjones it's the "charge threshold" in the bottom of the dashboard. By default it's 4
Thanks! Obvious now you said it 😀
from pv_opt.
Still something off. Not sure why the 15:30 slot doesn't trigger a charge and why only discharge is scheduled :/
from pv_opt.
error.log
main.log
pv_opt.log
pv_opt.log.patch
from pv_opt.
Yep I'm having the same problem with my setup as well.
Recently there seems to be very few charging slots allocated, despite there being a large difference in unit price between now (for example) and my peak period of 16:00 - 19:00.
I adjusted the "Charge Threshold" to 0 as noted above, and it seemed to have started working again. However, it's had another recalculation and again has totally ignored my cheapest slot.
I've ended up putting it in read only and manually setting my charging slots so I can at least get through the peak times later, but there seems to be something fundamentally wring with the calculations as it's missing key (relatively) cheap slots to charge.
My screenshot FYI:
from pv_opt.
from pv_opt.
But at a basic level, it should be charging the battery at 14.51p, 15.54p etc, ready for discharging at the expensive times, which are approx twice the price? It didn't do this, which was why I had to put it in read only and manually charge, ready for peak slots.
It’s ignoring the cheap slots because they aren’t cheap enough to save you any money. The SOC shows your solar getting you to after the peak slots.
But after the peak slots it's still more expensive than before, so why wouldn't it charge up as cheap as possible to last as far as possible overnight?
So roughly what does the difference in price between charging and discharging need to be before it considers it enough to set a charge? From the above I have a 14 / 15p rate before peak, with approx. 30p peak - I would have thought that would have been plenty of difference?
from pv_opt.
Related Issues (20)
- PV sun up pre-charging HOT 3
- Optimiser frequency setting not working as expected HOT 2
- No charging schedule set in pv_opt HOT 8
- Static Solcast data HOT 8
- Incorrect release label? HOT 1
- Timezone error stopping pv_opt from starting HOT 7
- Unexpected error running initialize() for pv_opt HOT 3
- Consumption Shape HOT 2
- Unexpected error in worker for App pv_opt: + ValueError: cannot convert float NaN to integer HOT 1
- solcast integration gone HOT 5
- Set up help HOT 3
- Multiple Inverters HOT 5
- Unexpected error in worker for App pv_opt:: AttributeError: 'numpy.float64' object has no attribute 'interpolate' HOT 2
- AppDaemon HASS plugin incompatible with `numpy 2.0.0` HOT 21
- PV-OPT stopped working after update to 3.15.2 HOT 5
- Decreasing SOC despite battery charge HOT 2
- Integration with solis-sensor and solis-control HOT 6
- Discharge Power Greater Than `battery_current_limit_amps` HOT 2
- "Divide by zero" warning messages in PV_Opt HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pv_opt.