Sofar: Battery DOD - write value

[pustek]

Hi, is possible to modify value inverter_battery_dod in sofar_g3hyd?

address : 0x104D
BatConfig_Depth_of_Discharge

1-90 %

_action: solarman.write_single_register
data:
device: XXXX
address: 4173
value: 60

Failed to perform the action solarman.write_single_register._

Thanks!
Tomas :)

[andreabafile]

I'd like to have this feature too!
Would be fantastic if it can be added automatically as configuration entity.

[davidrapan]

Hi @pustek, what if you use solarman.write_multiple_registers ACTION instead?

[davidrapan]

That sounds great!

I'm currently also trying to solve similar problem of managing large consumptions according to spot energy prices w/o touching energy stored in the batteries + also charging batteries from the grid but unfortunately it's not that simple w/ my device.

[pustek]

That sounds great!

I'm currently also trying to solve similar problem of managing large consumptions according to spot energy prices w/o touching energy stored in the batteries + also charging batteries from the grid but unfortunately it's not that simple w/ my device.

I did little observations about Storage Control Mode settings and behavior of each. I would expect different that it is named for.

I will do separate discussion. :)

[pustek]

I found the value which can be used for Passive control of battery. So you can even charge battery from grid if you need, during the charging the car battery from grid in chep hours.

Unfortunatley this mysterious registry also does not work to control Single or multiple write :(
From application by bluetooth it is working, you can even discharge your battery to grid.

4487

Passive_Manual_Gdes

Manual mode expected grid power (Gdes);
A positive value indicates the power direction "from the grid to the system";
Negative values indicate the power direction "from system to grid".

This would be nice to have :)

[PiervitoCreanza]

Hi, I’m experiencing a similar issue with the HYD 6000-ZSS inverter, which I believe is a rebranded version of your Sofar model. When I try to write to certain registers to control the anti-reflux power, I receive the following error:

Incorrect response w/ function code 144 instead of 16 received.

My assumption is that some of these registers are write-protected and need to be unlocked before they can be modified. I’m still investigating how to do that—I’ll share any findings if I make progress.

[davidrapan]

It's very likely that you need to write into multiple registers in bulk.

[pierinho]

I have a ZCS Azzurro (Solarman rebranded) and when try to change the DOD of battery with this script i receive an error.
Script:
action: solarman.write_multiple_registers
data:
device: 60016e292b11a6cb4d00ac66c7b732cc
address: 4173
values: 60

Error: solarman.write_multiple_registers CRC validation failed.

[davidrapan]

Okay, so it must begin with 4164 therefore use first Solarman: Read Holding Registers (Modbus Function Code 3), set address to 4164 and count to 10. Then use those values w/ Solarman: Write Multiple Registers (Modbus Function Code 16), set address again to 4164 and replace the last one with your value (60).

Example:

action: solarman.write_multiple_registers
data:
  device: bd3eff81f9b0984e91f40426cba9c0e1
  address: 4173
  values:
    - ??
    - ??
    - ??
    - ??
    - ??
    - ??
    - ??
    - ??
    - ??
    - 60

[pierinho]

try now, same error

[davidrapan]

Try it w/ 19 registers then. Also, turn on debug logging and call it w/ that. I'd like to see it.

[pierinho]

try with 19, same error:
Registratore: homeassistant.components.websocket_api.http.connection
Fonte: components/websocket_api/commands.py:825
Integrazione: Home Assistant WebSocket API (documentazione, problemi)
Prima occorrenza: 15:32:05 (15 occorrenze)
Ultimo accesso: 17:46:45

[546919694720] The value contained in the request data field is not an allowable value for the server.
[546919694720] Modbus exception: AcknowledgeError
[546943828672] CRC validation failed.
[546901783744] CRC validation failed.
[546933400544] CRC validation failed.

[davidrapan]

No, can you please Enable debug logging on the integration? Then try to do the write, disable debug logging and upload the log file here with the message. I need to see the whole flow. 😉

[pierinho]

home-assistant_solarman_2025-05-10T17-29-16.276Z.log
Log file...

[pierinho]

the are some line with RECD:
one is: 2025-05-10 23:49:01.732 DEBUG (MainThread) [custom_components.solarman.pysolarman.pysolarman] [192.168.1.174] RECD: a5 15 00 10 15 44 ad c4 13 15 a3 02 01 b1 4f 4f 03 a4 13 00 00 1d 7a d0 64 01

[davidrapan]

But it must be response to to the write.... this one is not even whole, there is a chunk missing.

[pierinho]

Any news for this problem?

[davidrapan]

Did you try write it w/ register 0x1053 - 4179 set to 1?

[pierinho]

yes, but same error

[pierinho]

home-assistant_solarman_2025-05-10T21-48-59.647Z.log
This is the complete log.

[davidrapan]

Hi @pierinho, there is some write control register (0x1053 - 4179) which should be set to 1 when writing:

action: solarman.write_multiple_registers
data:
  device: bd3eff81f9b0984e91f40426cba9c0e1
  address: 4173
  values:
    - 0
    - 0
    - 3
    - 545
    - 535
    - 440
    - 460
    - 10000
    - 10000
    - 60
    - 60
    - 100
    - 500
    - 0
    - 20
    - 1 # This is address 4179, according to docs you need 1 here
    - 0
    - 0
    - 0
    - 0
    - 0
    - 0
    - 0

[pierinho]

I try, but same error

[davidrapan]

I'm out of ideas then... You could try something like firmware update because this is how it should work according to documentation.