ESPHome config for various PowMr Hybrid Inverter models.
All models that are supported by the WIFI-VM device should work:
This configuration can be used on the ESP8266, but you won't be able to use all the sensors due to the memory limitations of the ESP8266. You can use minimal set of sensors/selects, leaving only the ones you need. You can use "Heap size" sensor of Debug module to determine how much free memory left. Looks like minimum heap size, that ensures stability, is near 6Kb. Although I still strongly recommend using ESP32.
1) Create new project subdirectory within your ESPHome configuration directory (let it be powmr-inverter
, for example)
2) Copy the contents of the src
repo folder to a newly created project directory.
3) Now, the main.yaml
file must be located under <esphome_config>/powmr-inverter
4) Create file powmr-inverter.yaml
in the esphome config directory root and copy contents of example config
5) Edit substitutions & customize powmr-inverter.yaml
. You can add contents of common_system & common_sensors to this file or include them separately following the example.
6) Flash firmware to your ESP32
There are 2 versions of PCB design available. Advanced version is more compact but needs SMD soldering skills, basic version uses 2.54 parts & modular approach.
In version 1.2, a PZEM module was added for measuring parameters of the input AC grid. If you do not wish to use it, comment out the include of the corresponding module in the main.yaml file.
For easy integration into Home Assistant, you can use the following snippet. It compiles all the essential inverter sensors and controls in a compact manner. The following custom plugins are required: sunsynk-power-flow-card, stack-in-card, tabbed-card, canary.
ESPHome reads sequential Modbus registers in one batch. If you have gaps in register addresses, you need to use the register_count
parameter to skip N registers and continue the batch.
Details in ESPHome docs.
You can debug your register ranges by setting the global log level to VERBOSE
and muting all "noisy" components except the modbus_controller
.
logger:
level: VERBOSE
logs:
component: ERROR # Fix for issue #4717 "Component xxxxxx took a long time for an operation"
modbus_controller: VERBOSE
modbus_controller.text_sensor: WARN
modbus_controller.sensor: WARN
modbus_controller.binary_sensor: WARN
modbus_controller.select: WARN
After this, the ranges map will be printed in the logs:
[15:55:14][C][modbus_controller:307]: ranges
[18:41:21][C][modbus_controller:307]: ranges
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x1196 count=37 skip_updates=0
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x11BC count=16 skip_updates=0
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x138A count=1 skip_updates=2
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x138F count=1 skip_updates=2
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x1391 count=1 skip_updates=2
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x1399 count=1 skip_updates=2
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x139A count=1 skip_updates=2
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x139E count=1 skip_updates=2
[18:41:21][C][modbus_controller:310]: Range type=3 start=0x13A0 count=1 skip_updates=2
In the example above, the sensor registers batches starts from
0x1196
&0x11BC
(one large batch causes data errors). Select registers starts from0x138A
. Using batches for selects triggersModbus device set offline
warning messages, so you need to read them separately.
You will see gaps in register ranges map. To calculate register_count
, you need to convert HEX addresses to decimal and subtract them.
# debug:
# direction: BOTH
# dummy_receiver: false
DEBUG
or VERBOSE
logger:
level: WARN