[DEVICE_ADD] POW-HVM6.2K-48V-LIP Add Modbus support

[v-moto]

Is your feature request related to a problem? Please describe

I cannot connect a new inverter to the HA

Describe the solution you'd like

I received a description of the inverter's communication protocol from the manufacturer, please add minimal support for this device
Modbus_RTU communication description.pdf

Describe alternatives you've considered

I did not find alternatives for this device, and it is not advisable to buy their adapter because it cannot be connected to HA

Additional context

No response

[softwarecrash]

Let it Check later.
@bigdigital See you a Chance to build it in?

[v-moto]

@softwarecrash @bigdigital
Do you have a usdt trc20 wallet for donations? Because I really like your project and want to support you a little) and maybe it will speed up the adaptation of my inverter a little))

[softwarecrash]

Badly No, PayPal ist linked in the Project for donation.
But sorry it Doenst Speed it Up, i have much Work on buissenes and less free time. So when i can get a Bit time i will Work on it.
Its Bit Tricky to Work without the device, i will try it when find some time

[v-moto]

Okay.
Then I'll send it via Paypal one of these days.
Thank you very much)
If you need any help with the tests, I am always happy to help

[bigdigital]

@v-moto pls contact me in discord so i can send you a test version

[sMusia]

Hi, I’m also an owner of such an inverter. I can join the tests too!

[v-moto]

Hi, I’m also an owner of such an inverter. I can join the tests too!

I have already received the beta, today I will test it, if everything goes well, I will write the result

[v-moto]

Hi, I’m also an owner of such an inverter. I can join the tests too!

Where are you from? And do you have an original adapter for this inverter?

[sMusia]

Hi, I’m also an owner of such an inverter. I can join the tests too!

Where are you from? And do you have an original adapter for this inverter?

I am from Ukraine. Unfortunately, I don’t have the original adapter. Here's the story: I had a POW-HVM-3.5H-24V inverter. At that time, there was no information on the internet about the communication protocol with the inverter, so I independently developed a way to retrieve some telemetry for HomeAssistant. Later, I switched to ESPHOME, which provided more telemetry data. Now, I’ve upgraded to the POW-HVM6.2K-48V-LIP and discovered the com port (RS232) and RJ45 (RS485). I couldn’t establish communication with either port—the inverter simply didn’t respond. That’s when I started thinking that the folks at POWMR might have changed the communication protocol. Then I came across Solar2MQTT and this query...

[sMusia]

Figured out the registers and made a working version based on ESPHOME.

[essergey]

@sMusia How did you manage to get the data?

[tsdaemon]

Figured out the registers and made a working version based on ESPHOME.

Hi! Thank you for sharing, can you share more details how did you do this with ESPHOME? I am also from Ukraine, and I am trying to set the monitoring for the same inverter.

[sMusia]

Figured out the registers and made a working version based on ESPHOME.

Hi! Thank you for sharing, can you share more details how did you do this with ESPHOME? I am also from Ukraine, and I am trying to set the monitoring for the same inverter.

inverter-powmr.zip

I used ESP8266, connection: esp: tx_pin: GPIO1, rx_pin: GPIO3 -> (RS-232 to UART, MAX3232) -> com_port: pin 2 - TX, pin 3 - RX, pin 5 - GND, pin 9 - +12-15V (with a step-down power module for ESP8266 and MAX3232).

ESPHOME yaml in attachment.

Very important!: Make as few requests as possible on the Modbus bus, refer to - Optimizing modbus communications - https://esphome.io/components/modbus_controller

[gyp5y]

Hi there!
I've just got data from my POW-HVM6.2K-48V-LIP using sample provided by @sMusia . It's great! Thank you!
The only thing that looks strange it's "Working Mode" values. I've got 8 and 9 on mine. Do you have extended description for those modes by any chance?

[gyp5y]

Yes. Both connected

[gyp5y]

It looks that those spikes up to int size is not caused by wrong register_count. Still has some.

[Massterzinger]

Maybe it is signed value, and it wants to pass something like -80w

[gyp5y]

You are right! There's a lot of values that are set to U_WORD in original yaml but they should be signed according to comm protocol.
Here's mine current config with signed/unsigned fixed.
inverter-powmr-esp32.yaml.txt

[gyp5y]

I've figured out why switch component worked strange. Every switch should have "bitmask 1" option set 'cos it expects to have 0x01 value as on. Now Remote switch, LCD Backlight and others are working fine. Here's updated config.
inverter-powmr-esp32.yaml.txt

[Fazabein]

Hello, my friend, can you make a tutorial on how to make a BMS cable? and which one should lead to the battery and which one should lead to the inverter? I use a hybrid inverter POW-HVM6.2K-48V-LIP and 2 amsan 48v 100ah wall mounted batteries

. Can you help me ??

[gyp5y]

I use pin-to-pin straight RJ-45 cable connected to RS-485 port on BMS and inverter but your case could be different if your batteries aren't based on JK-BMS hardware. Then I was playing with protocol selection on BMS and on inverter. I don't remember which one I'm using. I will check in a few days and write it here.

[gyp5y]

Protocol on the JK-BMS is (9600)PYLON_low_voltage and on the inverter is LI2 (PYLON US2000 according to manual)

[gyp5y]

@sMusia Using your example makes it read okay but I can't change any value. Maybe you can suggest how to solve this?
[12:34:58][D][select:062]: 'Battery charging priority' - Setting
[12:34:58][D][select:115]: 'Battery charging priority' - Set selected option to: Only PV charging
[12:34:58][D][modbus_controller.select:048]: Found value 3 for option 'Only PV charging'
[12:34:59][W][modbus_controller:027]: Modbus device=1 set offline
[12:34:59][D][modbus_controller:040]: Modbus command to device=1 register=0x14B no response received - removed from send queue
[12:35:00][W][modbus_controller:065]: Modbus device=1 back online
[12:35:00][D][modbus_controller.select:014]: New select value 0 from payload

[gyp5y]

This problem was solved using use_write_multiple: true for switches and other output sensors. PowMR supports only 0x10 function code when setting values. By default modbus controller in esphome sends 0x06 function code. use_write_multiple force it to use supported function code. Hope this will help someone.
My config attached
powmr_lip.yaml.txt

[gyp5y]

Here's version with some fixes (register sizes, measurement units, max current step and display etc)
powmr_lip.yaml.txt

[gyp5y]

Here's one more update. It's version I use for a while and it's pretty fine.
powmr_lip.yaml (1).txt

[Massterzinger]

inverter-powmr-esp32.yaml.txt
Here's my version for esp32 with fixed output source priority

[gyp5y]

If, by any chance, someone knows register address to get data equivalent to menu options 43,44,45 (SOC back-to-battery, SOC back-to-utility, SOC cut-off) - please share.

[synthesis77]

Thanks to those pioneering this! I just bought three of these POW-HVM6.2K-48V-LIP units to replace a combination of Victor NM-II 5KW units and an EASUN ISolar-SMH-II-7KW-Wifi unit. To my surprise, the WiFi-Pro dongles that were working with the older units don't establish coms with the new unit (though they power up and connect to wifi still).

So, since Smart ESS sucks anyway, I'm headed down the path of integrating ESPs into my setup. I'm handy coding actual arduino /c code and was planning on rolling my own, but a prebuilt like this certainly makes things easier.

On a side note, I just got my RS232-TTL adapters (with built in male DB9s) and I just want to verify pin numbers. I have this as a pinout, and am curious about the DB9 pins 2&3 possibly being reversed?

[gyp5y]

Hello, I'm sure that RX and TX are pins 2 and 3 but I not sure if they are reversed. I was playing with DB-9 to RJ-45 adapter and with RX, TX pins in ESP32 firmware so even if they are reversed it was fixed in firmware :) Inverter is pretty far from me so I can't check it for you. Pins 5 and 9 are VCC and GND. Voltage on VCC pin is smth about 15V so be sure to use voltage converter before powering your MCU using VCC from inverter.

[synthesis77]

as an FYI, your code worked GREAT! I'm tuning it a bit and will upload it back, and then start to work on the parallel part, aggregating multiple POW-HVM6.2K-48V-LIPs into one virtual inverter bank. Thank you!!

[gyp5y]

I'm glad that it's useful :) I have no additional inverters to test parallel functions so I skipped this part.

[gyp5y]

At last! I've got addresses not documented in protocol specification from PowMr support team so options 43, 44 and 45 are controllable too.
Here's updated config I'm using.
inverter-powmr-esp32.yaml.txt
P.S. There is commented section to control battery discharge for battery communicating with inverter and not communicating. Comment out one you're not using. Or just uncomment both and keep in mind that only one section is used

[synthesis77]

Okay, thanks to you folks, I have parallel inverters up and going on a single ESP32. I did a MAJOR refactor of the code you provided, and while it's sorta more complicated, it's more flexible and hopefully easier to use.

There's now TWO files (though you could use just the single one if you only have one inverter). For me, it's inverter.yaml and single-pow-hvm62k-48v-lip.yaml. I use the Packages feature to aggregate the "single" file into the top inverter file, and then create some prefixed aggregate sensors which combine the multiple inverters data into one.

If you only use the single file, you'll be just fine too, and if you ever update to multiple units, your data will be in the same place (i.e. the aggregate IDs will match the previous single IDs). Note that I changed most of the data IDs though, so they won't line up with your previous data. I also changed most of the names so that they'd be in groups, like "Output", "Inverter", "Battery", etc, so they sort better in the default HA UI.

I fixed several of the sensors' issues, ranging from missing units, types, etc, and tried to optimize it with register counts to make the data transmission more efficient. I have it updating every second, and it works great even with two inverters. There are some remaining issues (marked FIXME) like incorrect ranges on the battery settings, missing EQ settings, and the warnings/faults parameters weren't right (they're bitmasks, not values) so I'll clean those up too. I also want to try to use anchors/aliases to reduce the amount of copy/pasting.

I should probably put these up in github, unless you want to sMusia or gyp5y!

inverter.yaml.txt
single-pow-hvm62k-48v-lip.yaml.txt

[gyp5y]

Great job! I'll definitely give it a try in a few days

[synthesis77]

I've updated the yaml to be totally anchored/aliased which makes it like 3 times smaller. it also makes it so you can easily add more parameters and/or use it for other stuff. I added the rest of the parameters too, and corrected most things. still to do is fix the warning and fault flags from selects, but I can't decide if I want to expose that as a state string or as a number or as a ton of readonly coils/bitmasks...

sensors now look like this:

  - <<: *modbus_volts
    name: "Battery Voltage${name_suffix}"
    id: Battery_Voltage${id_suffix}
    address: 215

instead of this:

  - platform: modbus_controller
    modbus_controller_id: modbus_controller_id${id_suffix}
    name: "Battery Voltage${name_suffix}"
    id: Battery_Voltage${id_suffix}
    address: 215
    register_type: holding
    value_type: S_WORD
    state_class: measurement
    device_class: voltage
    unit_of_measurement: "V"
    accuracy_decimals: 1
    filters:
      - multiply: 0.1

it's now up in github:
https://github.com/synthesis77/esp32-stuff/tree/main