odya / esphome-powmr-hybrid-inverter Goto Github PK

View Code? Open in Web Editor NEW

84.0 9.0 13.0 50.55 MB

ESPHome config for various PowMr Hybrid Inverter models.

License: MIT License

C++ 100.00%

esp32 esp8266 esphome esphome-config esphome-devices powmr

esphome-powmr-hybrid-inverter's Introduction

Hi 👋, I'm Andrii Ganzevych

Backend developer from Kyiv, Ukraine

🤖 Smart home enthusiast (Home Assistant, IOT, microcontrollers etc.)
🎸 Musician (playing mandolin & whistles in O'Hamsters celtic-punk band🍀)
📸 Photographer (aerochrome, infrared, micro/macro, nature, aero)
👾 Geek-boy (comics, mass-culture, computer games as art)
🚀 Space tech fan
🏔 Traveler
🚴‍♀️ Cycler
🍺 Craft beer drinker

Connect with me:

Languages and Tools:

esphome-powmr-hybrid-inverter's People

Contributors

Stargazers

Watchers

Forkers

davidebeatrici hippieua aver-ua pkirk roving-ronin gauix4 ogry gutekhkey gh-user-source th3m1k3y brucedidier hvdb

esphome-powmr-hybrid-inverter's Issues

PV_Current Duplicate template Sensor

Just wanted to inform you the template sensor for PV_Current is duplicated in both the main Yaml Aswell as the Inverter Yaml, this throws up errors within the Esphome API

"Received nan" almost for all commands

Can you help me to figure out the issue, please?

Invertor: POW-HVM6.2M

Microcontroller: M5 Atom lite + RS232->ttl
GPIO22+GPIO19
Config as in the example

this is the part of the log

[15:03:24][C][modbus_controller:349]: ranges
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x1399 count=1 skip_updates=2
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x1196 count=37 skip_updates=0
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x11BC count=16 skip_updates=0
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x138A count=1 skip_updates=2
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x138F count=1 skip_updates=2
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x1391 count=1 skip_updates=2
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x139A count=1 skip_updates=2
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x139E count=1 skip_updates=2
[15:03:24][C][modbus_controller:352]:   Range type=3 start=0x13A0 count=1 skip_updates=2
[15:03:24][C][modbus_controller:354]: server registers
[15:03:24][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1399 count 1
[15:03:24][V][modbus:210]: Modbus write: 05.03.13.99.00.01.51.25 (8)
[15:03:24][V][modbus_controller:556]: Command sent 3 0x1399 1
[15:03:24][D][uart_debug:114]: >>> 05:03:13:99:00:01:51:25
[15:03:24][V][sensor:043]: 'Load Power': Received new state nan
[15:03:24][D][sensor:094]: 'Load Power': Sending state nan W with 0 decimals of accuracy
[15:03:25][D][sensor:094]: 'Battery Current': Sending state nan A with 1 decimals of accuracy
[15:03:25][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1399 count 1
[15:03:25][V][modbus:210]: Modbus write: 05.03.13.99.00.01.51.25 (8)
[15:03:25][V][modbus_controller:556]: Command sent 3 0x1399 1
[15:03:25][D][uart_debug:114]: >>> 05:03:13:99:00:01:51:25
[15:03:26][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1399 count 1
[15:03:26][V][modbus:210]: Modbus write: 05.03.13.99.00.01.51.25 (8)
[15:03:26][V][modbus_controller:556]: Command sent 3 0x1399 1
[15:03:26][D][uart_debug:114]: >>> 05:03:13:99:00:01:51:25
[15:03:26][V][internal_temperature:034]: Raw temperature value: 118
[15:03:26][V][sensor:043]: 'Controller Temperature': Received new state 47.777779
[15:03:26][D][sensor:094]: 'Controller Temperature': Sending state 47.77778 °C with 1 decimals of accuracy
[15:03:27][W][modbus_controller:027]: Modbus device=5 set offline
[15:03:27][D][modbus_controller:040]: Modbus command to device=5 register=0x1399 countdown=0 no response received - removed from send queue
[15:03:27][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1196 count 37
[15:03:27][V][modbus:210]: Modbus write: 05.03.11.96.00.25.60.85 (8)
[15:03:27][V][modbus_controller:556]: Command sent 3 0x1196 37
[15:03:27][D][uart_debug:114]: >>> 05:03:11:96:00:25:60:85
[15:03:28][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1196 count 37
[15:03:28][V][modbus:210]: Modbus write: 05.03.11.96.00.25.60.85 (8)
[15:03:28][V][modbus_controller:556]: Command sent 3 0x1196 37
[15:03:28][D][uart_debug:114]: >>> 05:03:11:96:00:25:60:85
[15:03:29][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1196 count 37
[15:03:29][V][modbus:210]: Modbus write: 05.03.11.96.00.25.60.85 (8)
[15:03:29][V][modbus_controller:556]: Command sent 3 0x1196 37
[15:03:29][D][uart_debug:114]: >>> 05:03:11:96:00:25:60:85
[15:03:30][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1196 count 37
[15:03:30][V][modbus:210]: Modbus write: 05.03.11.96.00.25.60.85 (8)
[15:03:30][V][modbus_controller:556]: Command sent 3 0x1196 37
[15:03:30][D][uart_debug:114]: >>> 05:03:11:96:00:25:60:85
[15:03:31][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x1196 count 37
[15:03:31][V][modbus:210]: Modbus write: 05.03.11.96.00.25.60.85 (8)
[15:03:31][V][modbus_controller:556]: Command sent 3 0x1196 37
[15:03:31][D][uart_debug:114]: >>> 05:03:11:96:00:25:60:85
[15:03:32][D][modbus_controller:040]: Modbus command to device=5 register=0x1196 countdown=0 no response received - removed from send queue
[15:03:32][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x11BC count 16
[15:03:32][V][modbus:210]: Modbus write: 05.03.11.BC.00.10.81.5A (8)
[15:03:32][V][modbus_controller:556]: Command sent 3 0x11BC 16
[15:03:32][D][uart_debug:114]: >>> 05:03:11:BC:00:10:81:5A
[15:03:33][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x11BC count 16
[15:03:33][V][modbus:210]: Modbus write: 05.03.11.BC.00.10.81.5A (8)
[15:03:33][V][modbus_controller:556]: Command sent 3 0x11BC 16
[15:03:33][D][uart_debug:114]: >>> 05:03:11:BC:00:10:81:5A
[15:03:34][V][sensor:043]: 'Load Power': Received new state nan
[15:03:34][D][sensor:094]: 'Load Power': Sending state nan W with 0 decimals of accuracy
[15:03:34][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x11BC count 16
[15:03:34][V][modbus:210]: Modbus write: 05.03.11.BC.00.10.81.5A (8)
[15:03:34][V][modbus_controller:556]: Command sent 3 0x11BC 16
[15:03:35][D][uart_debug:114]: >>> 05:03:11:BC:00:10:81:5A
[15:03:35][D][sensor:094]: 'Battery Current': Sending state nan A with 1 decimals of accuracy
[15:03:35][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x11BC count 16
[15:03:35][V][modbus:210]: Modbus write: 05.03.11.BC.00.10.81.5A (8)
[15:03:35][V][modbus_controller:556]: Command sent 3 0x11BC 16
[15:03:36][D][uart_debug:114]: >>> 05:03:11:BC:00:10:81:5A
[15:03:36][V][internal_temperature:034]: Raw temperature value: 118
[15:03:36][V][sensor:043]: 'Controller Temperature': Received new state 47.777779
[15:03:36][D][sensor:094]: 'Controller Temperature': Sending state 47.77778 °C with 1 decimals of accuracy
[15:03:36][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x11BC count 16
[15:03:37][V][modbus:210]: Modbus write: 05.03.11.BC.00.10.81.5A (8)
[15:03:37][V][modbus_controller:556]: Command sent 3 0x11BC 16
[15:03:37][D][uart_debug:114]: >>> 05:03:11:BC:00:10:81:5A
[15:03:38][D][modbus_controller:040]: Modbus command to device=5 register=0x11BC countdown=0 no response received - removed from send queue
[15:03:38][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138A count 1
[15:03:38][V][modbus:210]: Modbus write: 05.03.13.8A.00.01.A0.E0 (8)
[15:03:38][V][modbus_controller:556]: Command sent 3 0x138A 1
[15:03:38][D][uart_debug:114]: >>> 05:03:13:8A:00:01:A0:E0
[15:03:39][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138A count 1
[15:03:39][V][modbus:210]: Modbus write: 05.03.13.8A.00.01.A0.E0 (8)
[15:03:39][V][modbus_controller:556]: Command sent 3 0x138A 1
[15:03:39][D][uart_debug:114]: >>> 05:03:13:8A:00:01:A0:E0
[15:03:39][V][sensor:043]: 'Battery Power': Received new state nan
[15:03:39][D][sensor:094]: 'Battery Power': Sending state nan W with 0 decimals of accuracy
[15:03:40][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138A count 1
[15:03:40][V][modbus:210]: Modbus write: 05.03.13.8A.00.01.A0.E0 (8)
[15:03:40][V][modbus_controller:556]: Command sent 3 0x138A 1
[15:03:40][V][sensor:043]: 'Load Current': Received new state nan
[15:03:40][D][sensor:094]: 'Load Current': Sending state nan A with 3 decimals of accuracy
[15:03:40][D][uart_debug:114]: >>> 05:03:13:8A:00:01:A0:E0
[15:03:40][V][modbus_controller:221]: 6 modbus commands already in queue
[15:03:40][V][modbus_controller:190]: Range : 1399 Size: 1 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 1196 Size: 25 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 11BC Size: 10 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 138A Size: 1 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 138F Size: 1 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 1391 Size: 1 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 139A Size: 1 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 139E Size: 1 (3) skip: 100
[15:03:40][V][modbus_controller:190]: Range : 13A0 Size: 1 (3) skip: 100
[15:03:41][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138A count 1
[15:03:41][V][modbus:210]: Modbus write: 05.03.13.8A.00.01.A0.E0 (8)
[15:03:41][V][modbus_controller:556]: Command sent 3 0x138A 1
[15:03:41][D][uart_debug:114]: >>> 05:03:13:8A:00:01:A0:E0
[15:03:41][V][sensor:043]: 'Load Power Factor': Received new state nan
[15:03:41][D][sensor:094]: 'Load Power Factor': Sending state nan  with 2 decimals of accuracy
[15:03:42][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138A count 1
[15:03:42][V][modbus:210]: Modbus write: 05.03.13.8A.00.01.A0.E0 (8)
[15:03:42][V][modbus_controller:556]: Command sent 3 0x138A 1
[15:03:42][D][uart_debug:114]: >>> 05:03:13:8A:00:01:A0:E0
[15:03:43][D][modbus_controller:040]: Modbus command to device=5 register=0x138A countdown=0 no response received - removed from send queue
[15:03:43][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138F count 1
[15:03:43][V][modbus:210]: Modbus write: 05.03.13.8F.00.01.B0.E1 (8)
[15:03:43][V][modbus_controller:556]: Command sent 3 0x138F 1
[15:03:43][D][uart_debug:114]: >>> 05:03:13:8F:00:01:B0:E1
[15:03:44][V][modbus_controller:044]: Sending next modbus command to device 5 register 0x138F count 1
[15:03:44][V][modbus:210]: Modbus write: 05.03.13.8F.00.01.B0.E1 (8)
[15:03:44][V][modbus_controller:556]: Command sent 3 0x138F 1
[15:03:44][D][uart_debug:114]: >>> 05:03:13:8F:00:01:B0:E1

POW-HVM3.2H-24V modbus write registers

Hi
I just want to share some extra write registers that I found in my POW-HVM3.2H-24V

I used an ESP32 and this https://github.com/zivillian/esp32-modbus-gateway/
By using the debug menu: "Debug" -> Slave ID 5 + "Read Holding Register" + Register # -> "Send" and comparing with the settings in the inverter screen

Here's the list: (just be careful, I haven't fully tested it)

5002 : Buzzer Alarm (range 0-1, settings menu 18)
5004 : Backlight control (range 0-1, settings menu 20)
5005 : Auto restart when overload occurs (range 0-1, settings menu 6)
5006 : Auto restart when over temperature occurs (range 0-1, settings menu 7)
5007 : Beep On Primary Source Fail (range 0-1, settings menu 22)
5008 : Auto return to default display screen (range 0-1, settings menu 19)
5009 : Overload Bypass (0-1, settings menu 23)
5010 : Record fault code (range 0-1, settings menu 25)
5017 : Charger Source Priority (range 0-3, settings menu 16)
5018 : Output Source Priority (range 0-2, settings menu 1)
5019 : AC input voltage range (range 0-1, settings menu 3) (0 - 90-280VAC, 1 - 170-280VAC)
5020 : Battery type (range 0-2, settings menu 5)
5021 : Output frequency (range 0-1, settings menu 9) (0 - 50hz, 1 - 60hz)
5022 : Max Total Charge Current (range 10-80, settings menu 2)
5023 : Output voltage (one of 220, 230, 240, settings menu 10)
5024 : Utility Charge Current (one of 2, 10, 20, 30, 40, 50, 60, settings menu 11)
5025 : Comeback Utility Mode Voltage (SBU) (0.5 volts step, settings menu 12)
5026 : Comeback Battery Mode Voltage (SBU) (0.5 volts step, settings menu 13)
5027 : Bulk charging voltage (settings menu 26)
5028 : Floating charging voltage (settings menu 27)
5029 : Low DC cut-off voltage (settings menu 29)
5030 : Battery equalization voltage (settings menu 31)
5031 : Battery equalized time (settings menu 33)
5032 : Battery equalized timeout (settings menu 34)
5033 : Equalization interval (settings menu 35)

Compiling for esp32c3

What parameters need to be changed to use it with the advanced pcb that @davidebeatrici designed. I can get it to compile but the esp just boot loops.

POW-HVM4.5K-24V/POW-HVM6.5K-48V support

Hello there.

Does anyone know if newer PowMr inverters like POW-HVM4.5K-24V/POW-HVM6.5K-48V are supported?

This feature is only available on ['esp8266'].

Verification for esp32 has errors.

INFO ESPHome 2023.5.5
INFO Reading configuration /config/esphome/node.yaml...
WARNING GPIO15 is a Strapping PIN and should be avoided.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
Failed config

logger: [source /config/esphome/node.yaml:46]
  level: WARN
  baud_rate: 0
  hardware_uart: UART1
  
  This feature is only available on ['esp8266'].
  esp8266_store_log_strings_in_flash: False

PV Power from POW-HVM10.2M seems to only show one of the two PV string

Gentleman,
I have two PV strings to my inverter(4 + 4kW) , but the register 4505 seems to show only one. The same thing is on the physical display of the Inverter, where only one string at a time is showed, but clicking make it cycle and show first one and then, after some other screen, the other one.

Any idea?

Inverter UART pins (TX2 & RX2) are swapped

Currently, the GPIO17 pin is being used as RX, although by default in WROOM32, it's assigned as TX. The current setup is functioning properly. However, swapping their roles would necessitate creating a new PCB hardware version, requiring separate pin configuration in the config file and complicating support. Therefore, I believe it's better to maintain the current configuration.

Thanks for the more complete registers list.

Hello from Lviv,
Linked your registers list from my readme.
Thanks for making it more complete!

Config temperature range warning

I've managed to install this project on my ESP 32 S2 Mini. I'm using POW-HVM3.2H-24V-N

In logs I'm getting one warning.

[W][esp-idf:000]: I (996404) tsens: Config temperature range [-10°C ~ 80°C], error < 1°C

Pintout and voltages from RJ45 port on POW-HVM3.2H-24V-N

I've got POW-HVM3.2H-24V-N, still waiting for the batteries, so testing it with benchtop power supply.

I'm checking the RJ45 pinout on my bench and I'm getting different outputs than from the diagram provided.

White green (1) is GND
Brown (8) is + VBat 24 V
Blue (4) is + 13.2 V

or at least that's what my multimeter says. Don't want to remove the top cover because of the tamper seal to check for the RJ45 board.

Unavailable daily energy sensors

Hi Andrii,
Thank you for your invertor integration.
Tried to use sunsynk-power-flow-card with PowMr invertor according to the example, but daily/total energy sensors are unavailable for PV and battery.

sensor.powmr_inverter_pv_yield_daily
sensor.battery_charge_daily

Sunsynk-power-flow-card developer @slipx06 says the problem is with the integration. I would appreciate any help in fixing this issue.

Sensors vanishing

So I'd been having issues as sensors had been vanishing from the modbus after some kind words and help from sseib over at the esphome discord we removed the lines

setup_priority: -10
offline_skip_updates: 100

From the modbus controller section of the inverter yaml
Now it all seems to work perfectly if the esphome device misses a modbus sensor it won't be deleted from the register.
Hope this helps anyone with the same issue and if odya or anyone thinks those lines shouldn't be removed please let me know.

Charger source priority and Output souce priority always returns to value "utility first" and "USB"

I don't understand why this happens, but even if I change the values to "only solar" and "SBU priority", they immediately change the values back to "Utility first" and "USB priority". Even if I change them on the inverter screen directly.
I'm using an Anern AN-SCI-MAX 10.2kw and the wifi dongle (esp8266).

Is it possible to use esp8266?

I repeat the title question: Is it possible to use esp8266?
In order to insert the firmware into the wifi antenna supplied to the inverter.

Duplicate modbus command found

[W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=4502 count=38
[W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=4538 count=1
[W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=4540 count=16

According to ESPHome's code the warning is logged when the exact command is already in the queue, which I guess may happen in our case because we are reading quite a lot.

However, I'm wondering why only those three addresses are affected and in a consistent manner.

Consider that I had to add command_throttle to the modbus_controller section (present in the old example), otherwise all retrieved values happened to be garbage.

Instaling problems

Hello Odya,

I Try to install de powmr-inverter file and get the following error. Can you explain what i do wrong?

Compiling .pioenvs/powmr-inverter/src/helpers/myhelpers.cpp.o
src/helpers/myhelpers.cpp:6:10: fatal error: myHelpers.h: No such file or directory

Looking for myHelpers.h dependency? Check our library registry!
CLI > platformio lib search "header:myHelpers.h"
Web > https://registry.platformio.org/search?q=header:myHelpers.h

#include "myHelpers.h"
^~~~~~~~~~~~~
compilation terminated.
*** [.pioenvs/powmr-inverter/src/helpers/myhelpers.cpp.o] Error 1
========================= [FAILED] Took 79.71 seconds =========================

POW-HVM4.2M-24V some issues

hi. thanks a lot for your work.
i have POW-HVM4.2M-24V inverter.
there are some issues that i found.

sensor "Charger Status" displays "0d00". what does it mean?
sensor "Controller Temperature" dispalys "70,6 °C". it's some kind of mistake. it can't be that high..
this invertor model has "Max Total Charging Current" = 140A (max) and "Max Utility Charging Current" = 100A (max). so the corresponding selects "Max Total Charge Current" and "Utility Charge Current" are not displayed normally and have an unknown value. how can i fix this?

Voltage control

I have POW-HVM1.5H-12V, will it be possible to control the voltages?

In the smartess application, it is not possible to control the voltages for 12v. There is only a choice of 24v or 48v.

Has anyone tested this integration with a 12v inverter?

does not read the values "Grid Active, Grid Active, Grid Power, Grid Voltage"

Hi, I can't read the "Grid Active, Grid Active, Grid Power, Grid Voltage" values. I have an esp32: M5Stack Atom Lite ESP32.

PowMr-Inverter as device name causes ESPHome compile to fail

Hi,

Just trying to get an ESP32-S3 to install your code and finding that it always fails.

Trying to trouble shoot it we've gone back to using the ESP32 flashed with a 'base' install from the ESPHome web installer, having it discovered in ESPHome on HA instance. When naming it powmr-inverter it then fails to compile.

If we repeat the steps but call it something else (power-inverter for example) then it compiles and flashes OK.
Note: At this point we are still using a default esphome configuration such as the example below, with zero reference to your powmr code:

esphome:
  name: power-inverter
  friendly_name: power-inverter

esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Power-Inverter Fallback Hotspot"
    password: "4pjRugTa49S4"

captive_portal:

If we then try to simply rename the device to 'powmr-inverter', or use this name from the start, we then find that compiling an install again fails. Note: This is again not even using your powmr-inverter code, its simply using powr-inverter as the device name.

To demonstrate this we've started with a default ESPHome install on the ESP32-S3, called it power-inverter and flashed it with that. We've then done a rename in ESPHome and gone to install it and it fails with:

INFO ESPHome 2024.3.1
INFO Reading configuration /config/esphome/power-inverter.yaml...
Updating /config/esphome/power-inverter.yaml to /config/esphome/powmr-inverter.yaml

INFO ESPHome 2024.3.1
INFO Reading configuration /config/esphome/powmr-inverter.yaml...
esphome:
  name: powmr-inverter
  friendly_name: Power-Inverter
  build_path: build/powmr-inverter
  area: ''
  platformio_options: {}
  includes: []
  libraries: []
  name_add_mac_suffix: false
  min_version: 2024.3.1
esp32:
  board: esp32-s3-devkitc-1
  framework:
    version: 2.0.5
    source: ~3.20005.0
    platform_version: platformio/[email protected]
    type: arduino
  flash_size: 4MB
  variant: ESP32S3
logger:
  baud_rate: 115200
  tx_buffer_size: 512
  deassert_rts_dtr: false
  hardware_uart: USB_CDC
  level: DEBUG
  logs: {}
api:
  port: 6053
  password: [redacted]
  reboot_timeout: 15min
ota:
  safe_mode: true
  version: 2
  port: 3232
  reboot_timeout: 5min
  num_attempts: 10
wifi:
  ap:
    ssid: [redacted]
    password: [redacted]
    ap_timeout: 1min
  domain: .local
  reboot_timeout: 15min
  power_save_mode: LIGHT
  fast_connect: false
  passive_scan: false
  enable_on_boot: true
  networks:
  - ssid: [redacted]
    password: [redacted]
    priority: 0.0
  use_address: powmr-inverter.local
captive_portal: {}

INFO Configuration is valid!
INFO ESPHome 2024.3.1
INFO Reading configuration /config/esphome/powmr-inverter.yaml...
INFO Generating C++ source...
INFO Core config or version changed, cleaning build files...
INFO Deleting /data/build/powmr-inverter/.pioenvs
INFO Deleting /data/build/powmr-inverter/.piolibdeps
INFO Compiling app...
Processing powmr-inverter (board: esp32-s3-devkitc-1; framework: arduino; platform: platformio/[email protected])
--------------------------------------------------------------------------------
Library Manager: Installing esphome/AsyncTCP-esphome @ 2.1.3
INFO Installing esphome/AsyncTCP-esphome @ 2.1.3
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Library Manager: Installing esphome/ESPAsyncWebServer-esphome @ 3.1.0
INFO Installing esphome/ESPAsyncWebServer-esphome @ 3.1.0
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash
 - toolchain-riscv32-esp @ 8.4.0+2021r2-patch5 
 - toolchain-xtensa-esp32s3 @ 8.4.0+2021r2-patch5
Dependency Graph
|-- AsyncTCP-esphome @ 2.1.3
|-- WiFi @ 2.0.0
|-- FS @ 2.0.0
|-- Update @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.1.0
|-- DNSServer @ 2.0.0
|-- ESPmDNS @ 2.0.0
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/api_connection.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/api_frame_helper.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/api_pb2.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/api_pb2_service.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/api_server.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/list_entities.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/proto.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/subscribe_state.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/api/user_services.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/captive_portal/captive_portal.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/esp32/core.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/esp32/gpio.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/esp32/preferences.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/logger/logger.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/logger/logger_esp32.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/logger/logger_esp8266.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/logger/logger_host.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/logger/logger_libretiny.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/logger/logger_rp2040.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/md5/md5.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/mdns/mdns_component.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/mdns/mdns_esp32.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/mdns/mdns_esp8266.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/mdns/mdns_host.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/mdns/mdns_libretiny.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/mdns/mdns_rp2040.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/network/util.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/ota/ota_backend_arduino_esp32.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/ota/ota_backend_arduino_esp8266.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/ota/ota_backend_arduino_libretiny.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/ota/ota_backend_arduino_rp2040.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/ota/ota_backend_esp_idf.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/ota/ota_component.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/socket/bsd_sockets_impl.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/socket/lwip_raw_tcp_impl.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/socket/lwip_sockets_impl.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/socket/socket.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/web_server_base/web_server_base.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/wifi/wifi_component.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/wifi/wifi_component_esp32_arduino.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/wifi/wifi_component_esp8266.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/wifi/wifi_component_esp_idf.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/wifi/wifi_component_libretiny.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/components/wifi/wifi_component_pico_w.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/application.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/color.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/component.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/component_iterator.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/controller.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/entity_base.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/helpers.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/log.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/ring_buffer.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/scheduler.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/string_ref.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/time.cpp.o
Compiling .pioenvs/powmr-inverter/src/esphome/core/util.cpp.o
Compiling .pioenvs/powmr-inverter/src/helpers/myHelpers.cpp.o
Compiling .pioenvs/powmr-inverter/src/main.cpp.o
Building .pioenvs/powmr-inverter/bootloader.bin
Creating esp32s3 image...
Successfully created esp32s3 image.
Generating partitions .pioenvs/powmr-inverter/partitions.bin
Compiling .pioenvs/powmr-inverter/lib703/AsyncTCP-esphome/AsyncTCP.cpp.o
Compiling .pioenvs/powmr-inverter/lib64d/WiFi/WiFi.cpp.o
In file included from src/helpers/myHelpers.cpp:6:
src/helpers/myHelpers.h:10:57: error: 'esphome::modbus_controller' has not been declared
 void updateUnknownSelect(uint16_t sensorIndex, esphome::modbus_controller::ModbusSelect* selectComp);
                                                         ^~~~~~~~~~~~~~~~~
src/helpers/myHelpers.h:10:88: error: expected ',' or '...' before '*' token
 void updateUnknownSelect(uint16_t sensorIndex, esphome::modbus_controller::ModbusSelect* selectComp);
                                                                                        ^
src/helpers/myHelpers.cpp:19:57: error: 'esphome::modbus_controller' has not been declared
 void updateUnknownSelect(uint16_t sensorIndex, esphome::modbus_controller::ModbusSelect* selectComp)
                                                         ^~~~~~~~~~~~~~~~~
src/helpers/myHelpers.cpp:19:88: error: expected ',' or '...' before '*' token
 void updateUnknownSelect(uint16_t sensorIndex, esphome::modbus_controller::ModbusSelect* selectComp)
                                                                                        ^
src/helpers/myHelpers.cpp: In function 'void updateUnknownSelect(uint16_t, int)':
src/helpers/myHelpers.cpp:22:8: error: 'selectComp' was not declared in this scope
   if (!selectComp->active_index().has_value() || sensorIndex != selectComp->active_index().value()) {
        ^~~~~~~~~~
src/helpers/myHelpers.cpp:22:8: note: suggested alternative: 'select'
   if (!selectComp->active_index().has_value() || sensorIndex != selectComp->active_index().value()) {
        ^~~~~~~~~~
        select
*** [.pioenvs/powmr-inverter/src/helpers/myHelpers.cpp.o] Error 1
========================= [FAILED] Took 33.24 seconds =========================

This is with a new HA install on an i5 CPU, with

ESPHome (Addon) 2024.3.1

HA:
Core 2024.3.3
Supervisor 2024.03.1
Operating System 12.1
Frontend 20240307.0

Update: Edited the yaml and storing the extra files in directory '/caravan-inverter' to work with an esp called 'caravan-inverter' (instead of the 'powmr-inverter' that is causing this issue) and ESPHome is able to work fine and compile the firmware.