• Help
  • Esphome testing and Battery Capacity Issues

I'm testing the board with Esphome, I had the same problem before, when i choose the battery capacity, I have this situation

21:53:07

[W]

[component:237]

Component powerfeather_mainboard took a long time for an operation (56 ms).

21:53:07

[W]

[component:238]
Also I have this warning on webpage

Components should block for at most 30 ms.

    niky8907 Hi, thanks for creating the post here. I just have a question, when you say " i choose the battery capacity" what do you mean? Do you mean the config parameter in the yaml:

    powerfeather_mainboard:
      id: "my_powerfeather"
      battery_capacity: 1000           # <---------------- this one?
      battery_type: "Generic_3V7" 
      update_interval: 5s

    I ask because the picture you posted is not of this - instead, the picture is of the dashboard controls. Do you mean perhaps one of these dashboard controls?

    I posted the behavior of the dashboard control when I tried to modify the YAML.
    I observed the same behavior while testing the board with the PowerFeather-Demo code.
    I have four Sanyo UR18650ZM2 batteries in parallel, so I tried changing the configuration as follows:

    battery_capacity: 9880

    Is this incorrect?

      niky8907 The max is actually 6000. In case of parallel, the capacity of a single cell must be used. This limitation is inherited from the LC709204F fuel guage:

      parallel-capacity

      I realized I didn't mention this in the ESPHome config documentation, will fix.

      By the way @niky8907, please do mark this as solved if the previous answer works for you.

      Yes, but I’m not sure if this behavior is normal.
      In the Debug Log[W]

      [component:237]

      Component powerfeather_mainboard took a long time for an operation (56 ms).

      21:53:07

      [W]

      [component:238]
      Also I have this warning on webpage

      Components should block for at most 30 ms.

      I didn't encounter this when I was testing the component, can you share your entire config yaml (minus the "secrets" of course, like wifi password etc.)?