Entity not avaliable: pvopt_opt_cost, pvopt_base_cost

[pbcjh10]

Running pv_opt on a HA Green. Set up eventually!

Solis inverter, Pyton tech batteries. Using Solax modbus where I have 169 entities.

However, I have a dashboard error and my dashboard never displays a PV Opt Result. pv_opt.log main.log error.log

This is the dashboard:

[stevebuk1]

Hmmmm, Pv_opt is occasionally failing to load consumption data from sensor.solis_house_load. It strictly doesn't need it, it loads both power and energy and will use power in preference of energy.

It might be a generic problem with Beta-9 you are running as I only download the energy sensors, however I think your energy sensor is not correct in config.yaml (so it has nothing to fall back on if power isn't working right) can you attach that file please?

[stevebuk1]

Note: from tomorrow I'm on hols for the week, will pick this up again on my return.

[pbcjh10]

@stevebuk1 voila! config.yaml.txt

[stevebuk1]

Try commenting out all of these lines in config.yaml:

id_consumption_today: sensor.{device_name}_consumption_today id_consumption:

• sensor.{device_name}_house_load
• sensor.{device_name}_bypass_load

The first entry is incorrect for the Solax modbus integration - it should be sensor.solis_house_load_today. I don't think that is the cause of the problems tho as Pv_opt seems to recognise that its not found and instead revert to the system default.

I think the cause of the problem is the 2nd and 3rd entries when a call is made through Appdeamon to load the consumption history in W . Its clear from #270 that some systems struggle to get it done with 10seconds and I suspect loading consumption as W is a significant size. Here, the system defaults appear deliberately set to entities that don't exist, and if this happens the system reverts to using kWh, which it then converts to W. I suspect loading kWh history is significantly smaller but perhaps slightly less accurate. Try it and post a log please.

[pbcjh10]

@stevebuk1 voila! pv_opt(1).log main(1).log error(1).log

It looks like its working, although my read only 'off' keeps flicking back over to on, similarly choosing Zappi from the dropdown box, but not sure how much of a difference they make. Are you able to explain why its dumping my battery to grid at 16:30 ? Solar will be negligable but I'll still have the evenings electricity use?

Also not sure I understand the "current setting forced discharge" is that right?

[stevebuk1]

re the readonly setting, if you want Pv_opt to start up in readonly mode, find this line in config.yaml:

read_only: false # If true the inverter will not be controlled

and change false to true.

The EV charger control is the beginnings of support for EVs. If you have a Zappi and its seen as part of the house load, then you'll need to set this to Zappi otherwise the consumption history that Pv_opt uses to predict your use will include the EV charging data. If your Zappi is outside of the house load (i.e on its own Henley block) you can leave it set to None.

If you do have a Zappi that is seen as part of the house load and/or are on IOG let me know as I have a mature Beta that supports IOG i.e will pick up any extra cheap slots and prevent the house battery discharging when the EV is charging. It also includes all the code for setting the default for the EV selector correctly.

[stevebuk1]

Apologies I've got myself confused. You were running the Beta release of Pv_opt before (v3.16.0-Beta-9) but your latest logs show its changed back to the main production release (v3.15.5). Was this deliberate?

[pbcjh10]

Yep we have a zappi and are on IOG !

From: stevebuk1 @.> Sent: 02 October 2024 13:35 To: fboundy/pv_opt @.> Cc: pbcjh10 @.>; Author @.> Subject: Re: [fboundy/pv_opt] Entity not avaliable: pvopt_opt_cost, pvopt_base_cost (Issue #269)

re the readonly setting, if you want Pv_opt to start up in readonly mode, find this line in config.yaml:

read_only: false # If true the inverter will not be controlled

and change false to true.

The EV charger control is the beginnings of support for EVs. If you have a Zappi and its seen as part of the house load, then you'll need to set this to Zappi otherwise the consumption history that Pv_opt uses to predict your use will include the EV charging data. If your Zappi is outside of the house load (i.e on its own Henley block) you can leave it set to None.

If you do have a Zappi that is seen as part of the house load and/or are on IOG let me know as I have a mature Beta that supports IOG i.e will pick up any extra cheap slots and prevent the house battery discharging when the EV is charging.

— Reply to this email directly, view it on GitHub https://github.com/fboundy/pv_opt/issues/269#issuecomment-2388531510 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3A5ETLAGUGQGCM7XMXJALZZPR55AVCNFSM6AAAAABPB3MNY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGUZTCNJRGA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AE3A5EW7YYAWP2I2XHZFPKLZZPR55A5CNFSM6AAAAABPB3MNY2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUOLYMTM.gif Message ID: @. @.> >

[pbcjh10]

No!

From: stevebuk1 @.> Sent: 02 October 2024 13:59 To: fboundy/pv_opt @.> Cc: pbcjh10 @.>; Author @.> Subject: Re: [fboundy/pv_opt] Entity not avaliable: pvopt_opt_cost, pvopt_base_cost (Issue #269)

Apologies I've got myself confused. You were running the Beta release of Pv_opt before (v3.16.0-Beta-9) but your latest logs show its changed back to the main production release (v3.15.5). Was this deliberate?

— Reply to this email directly, view it on GitHub https://github.com/fboundy/pv_opt/issues/269#issuecomment-2388584224 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3A5EXK4RQ5RAE2N2CNOY3ZZPUZXAVCNFSM6AAAAABPB3MNY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGU4DIMRSGQ . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AE3A5EULVIFGMXXXVEGXPA3ZZPUZXA5CNFSM6AAAAABPB3MNY2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUOL3TSA.gif Message ID: @. @.> >

[stevebuk1]

Apologies I got myself confused. You are already running v3.16.0-Beta-9 and are on IOG.

In which case, take a look at the config.yaml here: https://github.com/stevebuk1/pv_opt/blob/dev/apps/pv_opt/config/config.yaml

Add the section called "EV parameters" to your own config.yaml - this will ensure Zappi is selected on each startup.

I'll post later on with some additional lines to add to config.yaml which will enable addtional logging, then I can have a look at your forced discharge question.

[stevebuk1]

I'll post later on with some additional lines to add to config.yaml which will enable additional logging, then I can have a look at your forced discharge question.

Near the top of your config.yaml file there is the following line:

debug: false

Change false to true.

In the user area, add the following line:

debug_categories: W

Once you see a charge/discharge plan that doesnt make sense, attach Pv_opt.log.