Help required with apps.yaml having errors - Fox inverter

[kosymodo]

Hey folks, I need some help please in configuring Predbat with my new Fox system.

I have Predbat installed, and mostly seems to be configured OK. However, I have a message saying that apps.yaml has 4 errors.

I have added Tony Hoyle's additions to my configuration.yaml and have uploaded his predbatt.yaml file into the same folder as that configuration.yaml file (I think this is the correct place to save it?)

What am I missing? No doubt something obvious, knowing me! ;)

[WyndStryke]

As of a recent predbat version which introduced auto-detection of kW versus kWh, most of Tony's automations don't need to be used anymore.

Also I don't think Tony's sensor for soc_kw is needed, since we're already supplying Soc as a percentage. So I also commented this out.

# If soc_kw is not supplied, then predbat will calculate it from soc_percent    
#  soc_kw:
#    - sensor.tonyhoyle_bms_actual_kwh_remaining

This is mine which just uses the sensors from the integration directly. However note that it relies on recent(ish) firmware. Older firmware might not include the bms_ sensors.

In particular, watch out for sensor.bms_kwh_remaining which means something different in old firmware compared to new firmware. In the new firmware it means the total nominal capacity of the battery, after adjusting for state-of-health (i.e., soc_max). In the old firmware, it meant the state of charge expressed in kWh.

  # NOTE: RECENT FIRMWARE NEEDED for bms_kwh_remaining (total battery capacity after considering 
  #       state-of-health.  Old firmware used this for soc_kwh.  If not available then just put 
  #       in the nominal battery size in kWh (not the usable size) as a constant rather than as 
  #       a sensor.
  soc_max:
    - sensor.bms_kwh_remaining

If you have 'manager' (AKA ARM) firmware of 1.33 or higher, then it'll include all the updated sensors on the KH.

apps_yaml.txt

[kosymodo]

@WyndStryke just revisiting this, as, although I no longer have any errors in my Predbat, I’m thinking my apps.yaml contains code it doesn’t need to as a result of it being cobbled together from different sources!

I know the fox.yaml template is based on @letsstartbeinganon upload, where in fact it shouldn’t be any longer, because of there no longer being a need to use Tony’s automations etc

@springfall2008 might it be a good idea to offer a template without reference to and/or code for this historical requirement?

My goal this week is to re-do my apps.yaml to make it less cluttered by code which is no longer required, especially since my export is going live in 3 days and I want Predbat to be correctly configured for that occasion 😀

[WyndStryke]

The same is probably true for many of the other inverter types too. Having to convert was a frequent requirement. I tried to simplify mine a bit (the one attached to that post).

It's really up to us Fox users to make changes to the template since Trefor can't test on his system (which isn't a Fox), and the same goes for all the other inverter types too.

[kosymodo]

Yeah I get that we’ll have to do the hard work to get an apps.yaml looking good, and then Trefor can upload that in place of the old fox.yaml template. Just seems a bit complicated to have an outdated template file with unnecessary code

[kosymodo]

@WyndStryke I've reviewed my apps.yaml against yours, and have copied a lot of yours across to mine. I now have a couple of errors though. Where do you get your number.force_charge_power_w and number.force_discharge_power_w from? I reckon I need to set up a couple of helpers, right?

EDIT - ignore me, I mistyped, both should be without the '_w' which now works :)