Comments (17)
fboundy
commented on June 20, 2024
Been busy with other things but will look at this as soon as I can
from pv_opt.
punkymuzzle
commented on June 20, 2024
Awesome, thank you
from pv_opt.
punkymuzzle
commented on June 20, 2024
Hi, any update on this please?
Thank you very much
from pv_opt.
silverhouse3
commented on June 20, 2024
@punkymuzzle do you have example of your files as I've got an X1 and its just a bunch of errors on the dashboard 😁
from pv_opt.
punkymuzzle
commented on June 20, 2024
@silverhouse3 there are a couple of (long) threads which should contain most of what you need:
#149
#188
I have been working with @fboundy to get the X1AC working with pv_opt.
It's mostly working now (thanks to @fboundy 's awesome programming skills), the only outstanding issues I have are:
- When the inverter discharges to 10% SoC it goes idle so pv_opt can't write to it (enhancement #216 raised)
- No way of ringfencing my 16:00 - 19:00 peak slot so the batteries are guaranteed full just before the peak time is reached (no official request yet, will need to raise this)
Hope this helps - let me know if you need anything further after reading the above links.
from pv_opt.
punkymuzzle
commented on June 20, 2024
Hi, any update on this please?
Thank you very much
from pv_opt.
fboundy
commented on June 20, 2024
Finally found time tio have a look at this. Would it help to have a "Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC above this level?
from pv_opt.
punkymuzzle
commented on June 20, 2024
Sure, what do you need from me?
…On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
Finally found time tio have a look at this. Would it help to have a
"Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC above
this level?
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from pv_opt.
punkymuzzle
commented on June 20, 2024
Yes that sounds great. We could either have it automatically be a couple of
% above the minimum SOC level that you set, or just a manual figure that
can be set.
My minimum SOC is 10% so I always try to keep it 2% higher using an
automation, but PV-opt always changes the Inverter state back to self use
so it eventually discharges to 10% (and then goes idle)
Thank you
…On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
Finally found time tio have a look at this. Would it help to have a
"Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC above
this level?
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from pv_opt.
fboundy
commented on June 20, 2024
So what happens if you just set the maximum depth of discharge to 12% in the config.yaml?
…On 21 May 2024 at 06:27 +0100, punkymuzzle ***@***.***>, wrote:
Yes that sounds great. We could either have it automatically be a couple of
% above the minimum SOC level that you set, or just a manual figure that
can be set.
My minimum SOC is 10% so I always try to keep it 2% higher using an
automation, but PV-opt always changes the Inverter state back to self use
so it eventually discharges to 10% (and then goes idle)
Thank you
On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
> Finally found time tio have a look at this. Would it help to have a
> "Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC above
> this level?
>
> —
> Reply to this email directly, view it on GitHub
> <#216 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
from pv_opt.
punkymuzzle
commented on June 20, 2024
Ooooh I wasn't aware of that setting 🙂.
I've now changed it and the next charging cycle (which was originally
starting from 10%) has now recalcated to start from 12%.
So hopefully this will fix my issue.
Will let you know tomorrow once the charge cycle has completed.
Thanks for your help.
…On Thu, 23 May 2024, 08:21 fboundy, ***@***.***> wrote:
So what happens if you just set the maximum depth of discharge to 12% in
the config.yaml?
On 21 May 2024 at 06:27 +0100, punkymuzzle ***@***.***>, wrote:
> Yes that sounds great. We could either have it automatically be a couple
of
> % above the minimum SOC level that you set, or just a manual figure that
> can be set.
> My minimum SOC is 10% so I always try to keep it 2% higher using an
> automation, but PV-opt always changes the Inverter state back to self
use
> so it eventually discharges to 10% (and then goes idle)
> Thank you
>
> On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
>
> > Finally found time tio have a look at this. Would it help to have a
> > "Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC
above
> > this level?
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <#216 (comment)>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
> > .
> > You are receiving this because you were mentioned.Message ID:
> > ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR353EDCJ6KRALCL2M3M3ZDWKHVAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGQYDIMJWGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from pv_opt.
punkymuzzle
commented on June 20, 2024
OK it did t work unfortunately.
The charging schedule calculated from 12 percent but there wasn't anything
to stop the battery discharging down to 10, so it went idle again.
Is there any way that PV opt can send a setting to the Inverter to stop
discharging at 12pc? Backup mode?
Or better still, send the next charging times to the Inverter before it
goes idle, that would be preferable, as the Inverter then remembers it even
if it goes idle.
Thanks very much for your help
…On Thu, 23 May 2024, 09:16 Steve Bond, ***@***.***> wrote:
Ooooh I wasn't aware of that setting 🙂.
I've now changed it and the next charging cycle (which was originally
starting from 10%) has now recalcated to start from 12%.
So hopefully this will fix my issue.
Will let you know tomorrow once the charge cycle has completed.
Thanks for your help.
On Thu, 23 May 2024, 08:21 fboundy, ***@***.***> wrote:
> So what happens if you just set the maximum depth of discharge to 12% in
> the config.yaml?
> On 21 May 2024 at 06:27 +0100, punkymuzzle ***@***.***>, wrote:
> > Yes that sounds great. We could either have it automatically be a
> couple of
> > % above the minimum SOC level that you set, or just a manual figure
> that
> > can be set.
> > My minimum SOC is 10% so I always try to keep it 2% higher using an
> > automation, but PV-opt always changes the Inverter state back to self
> use
> > so it eventually discharges to 10% (and then goes idle)
> > Thank you
> >
> > On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
> >
> > > Finally found time tio have a look at this. Would it help to have a
> > > "Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC
> above
> > > this level?
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <#216 (comment)>,
>
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
>
> > > .
> > > You are receiving this because you were mentioned.Message ID:
> > > ***@***.***>
> > >
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
> —
> Reply to this email directly, view it on GitHub
> <#216 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACNR353EDCJ6KRALCL2M3M3ZDWKHVAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGQYDIMJWGE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
from pv_opt.
fboundy
commented on June 20, 2024
Ok - the latter might me easier. Will try to find some time over the weekend to implement it.
…On 24 May 2024 at 11:45 +0100, punkymuzzle ***@***.***>, wrote:
OK it did t work unfortunately.
The charging schedule calculated from 12 percent but there wasn't anything
to stop the battery discharging down to 10, so it went idle again.
Is there any way that PV opt can send a setting to the Inverter to stop
discharging at 12pc? Backup mode?
Or better still, send the next charging times to the Inverter before it
goes idle, that would be preferable, as the Inverter then remembers it even
if it goes idle.
Thanks very much for your help
On Thu, 23 May 2024, 09:16 Steve Bond, ***@***.***> wrote:
> Ooooh I wasn't aware of that setting 🙂.
> I've now changed it and the next charging cycle (which was originally
> starting from 10%) has now recalcated to start from 12%.
> So hopefully this will fix my issue.
> Will let you know tomorrow once the charge cycle has completed.
> Thanks for your help.
>
> On Thu, 23 May 2024, 08:21 fboundy, ***@***.***> wrote:
>
>> So what happens if you just set the maximum depth of discharge to 12% in
>> the config.yaml?
>> On 21 May 2024 at 06:27 +0100, punkymuzzle ***@***.***>, wrote:
>> > Yes that sounds great. We could either have it automatically be a
>> couple of
>> > % above the minimum SOC level that you set, or just a manual figure
>> that
>> > can be set.
>> > My minimum SOC is 10% so I always try to keep it 2% higher using an
>> > automation, but PV-opt always changes the Inverter state back to self
>> use
>> > so it eventually discharges to 10% (and then goes idle)
>> > Thank you
>> >
>> > On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
>> >
>> > > Finally found time tio have a look at this. Would it help to have a
>> > > "Wake-Up SOC" parameter so that PV-Opt always tries to keep the SOC
>> above
>> > > this level?
>> > >
>> > > —
>> > > Reply to this email directly, view it on GitHub
>> > > <#216 (comment)>,
>>
>> > > or unsubscribe
>> > > <
>> https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
>>
>> > > .
>> > > You are receiving this because you were mentioned.Message ID:
>> > > ***@***.***>
>> > >
>> > —
>> > Reply to this email directly, view it on GitHub, or unsubscribe.
>> > You are receiving this because you were mentioned.Message ID:
>> ***@***.***>
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#216 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ACNR353EDCJ6KRALCL2M3M3ZDWKHVAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGQYDIMJWGE>
>> .
>> You are receiving this because you were mentioned.Message ID:
>> ***@***.***>
>>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
from pv_opt.
punkymuzzle
commented on June 20, 2024
Awesome, thank you very much
…On Fri, 24 May 2024, 12:06 fboundy, ***@***.***> wrote:
Ok - the latter might me easier. Will try to find some time over the
weekend to implement it.
On 24 May 2024 at 11:45 +0100, punkymuzzle ***@***.***>, wrote:
> OK it did t work unfortunately.
> The charging schedule calculated from 12 percent but there wasn't
anything
> to stop the battery discharging down to 10, so it went idle again.
> Is there any way that PV opt can send a setting to the Inverter to stop
> discharging at 12pc? Backup mode?
> Or better still, send the next charging times to the Inverter before it
> goes idle, that would be preferable, as the Inverter then remembers it
even
> if it goes idle.
>
> Thanks very much for your help
>
> On Thu, 23 May 2024, 09:16 Steve Bond, ***@***.***> wrote:
>
> > Ooooh I wasn't aware of that setting 🙂.
> > I've now changed it and the next charging cycle (which was originally
> > starting from 10%) has now recalcated to start from 12%.
> > So hopefully this will fix my issue.
> > Will let you know tomorrow once the charge cycle has completed.
> > Thanks for your help.
> >
> > On Thu, 23 May 2024, 08:21 fboundy, ***@***.***> wrote:
> >
> >> So what happens if you just set the maximum depth of discharge to 12%
in
> >> the config.yaml?
> >> On 21 May 2024 at 06:27 +0100, punkymuzzle ***@***.***>, wrote:
> >> > Yes that sounds great. We could either have it automatically be a
> >> couple of
> >> > % above the minimum SOC level that you set, or just a manual figure
> >> that
> >> > can be set.
> >> > My minimum SOC is 10% so I always try to keep it 2% higher using an
> >> > automation, but PV-opt always changes the Inverter state back to
self
> >> use
> >> > so it eventually discharges to 10% (and then goes idle)
> >> > Thank you
> >> >
> >> > On Mon, 20 May 2024, 16:24 fboundy, ***@***.***> wrote:
> >> >
> >> > > Finally found time tio have a look at this. Would it help to have
a
> >> > > "Wake-Up SOC" parameter so that PV-Opt always tries to keep the
SOC
> >> above
> >> > > this level?
> >> > >
> >> > > —
> >> > > Reply to this email directly, view it on GitHub
> >> > > <
#216 (comment)>,
> >>
> >> > > or unsubscribe
> >> > > <
> >>
https://github.com/notifications/unsubscribe-auth/ACNR352XHKCZKWMMXTNVA7LZDIITJAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGY4DGMBTGY>
> >>
> >> > > .
> >> > > You are receiving this because you were mentioned.Message ID:
> >> > > ***@***.***>
> >> > >
> >> > —
> >> > Reply to this email directly, view it on GitHub, or unsubscribe.
> >> > You are receiving this because you were mentioned.Message ID:
> >> ***@***.***>
> >>
> >> —
> >> Reply to this email directly, view it on GitHub
> >> <#216 (comment)>,
> >> or unsubscribe
> >> <
https://github.com/notifications/unsubscribe-auth/ACNR353EDCJ6KRALCL2M3M3ZDWKHVAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGQYDIMJWGE>
> >> .
> >> You are receiving this because you were mentioned.Message ID:
> >> ***@***.***>
> >>
> >
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR355MPKGSHNQFTUYEVGDZD4NL7AVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGI3DGMBYGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from pv_opt.
punkymuzzle
commented on June 20, 2024
Hi
Is there any update on this please?
Thanks very much
from pv_opt.
fboundy
commented on June 20, 2024
Should be fixed in 3.14.10. You’ll need to add `sleep_soc: 15` (for example) to your `config.yaml`
…On 29 May 2024 at 10:39 +0100, punkymuzzle ***@***.***>, wrote:
Hi
Is there any update on this please?
Thanks very much
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
from pv_opt.
punkymuzzle
commented on June 20, 2024
You are a star, thank you very much.for your help
I'll set it up and monitor tonight.
Thanks again
…On Sun, 2 Jun 2024, 13:50 fboundy, ***@***.***> wrote:
Should be fixed in 3.14.10. You’ll need to add ‘sleep_soc: 15’ (for
example) to your config.yaml
On 29 May 2024 at 10:39 +0100, punkymuzzle ***@***.***>, wrote:
> Hi
> Is there any update on this please?
> Thanks very much
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNR35ZMSW6W6XVWYXGDJKDZFMIKVAVCNFSM6AAAAABGW2JO5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTHA2DANZTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from pv_opt.
Related Issues (20)
- Manual tariff setting HOT 3
- Hold lower than 100% battery charge HOT 6
- Question about charging optimisation algorithm HOT 8
- 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
- Battery doesn't get charged in cheap periods HOT 16
- 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 2
- Multiple Inverters HOT 4
- Unexpected error in worker for App pv_opt:: AttributeError: 'numpy.float64' object has no attribute 'interpolate' HOT 1
- AppDaemon HASS plugin incompatible with `numpy 2.0.0` HOT 20
- PV-OPT stopped working after update to 3.15.2 HOT 5
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.