How to read single register from multiple different modbus memory areas?

[murik85]

[davidrapan]

What do you mean?

[murik85]

Work:

• group: Inverter
  code: 0x04
  items:
  • name: "Run State"
    rule: 1
    registers: [0x09C4]
    isstr: true
    lookup:
    • key: 1
      value: "Stand-by"
    • key: 2
      value: "Start"........

If I add ('EMSMode' "select"), 'Run State' stops working:

• group: Inverter
  code: 0x04
  items:

  • name: "Run State"
    update_interval: 60
    rule: 1
    registers: [0x09C4]
    isstr: true
    lookup:
    • key: 1
      value: "Stand-by"
    • key: 2
      value: "Start"........

• group: Settings
  code: 0x03
  items:

  • name: "EMS Mode"
    platform: select
    rule: 1
    registers: [0x09C4]
    lookup:
    • key: 0
      value: "SelfUse"
    • key: 1
      value: "ChrFst"............

[davidrapan]

Yes because they use the same register, you can only use one or the other. Just transform Run State into platform: select. You can still use it as sensor to show value. 😉 In other words, you don't really need two entities.

[murik85]

I did (RunState....select) - it doesn't fit, it doesn't update, and the EMSMode value (key1-key2.......) changes when selecting. The problem is that RunState should only be read (fc:0x04), and EMSMode should be changed (fc:0x06). And the register is the same. So we need two entities.

Maybe the update delay should be shifted: RunState (fc:0x04) update_interval: 15......EMSMode (fc:0x03) update_interval: 20. Though I doubt it will help.

I don't understand how it is organized in one register.

[davidrapan]

If you change that entity to select it does not affect how it's read, it will still use separate function codes for reading and writing...

So if you need 0x04 for reading and 0x06 for writing you add:

code:
  read: 0x03
  write: 0x06

You can find it for example here

Edit: If your inverter uses single register like that it's not possible to create separate requests for single register using different modbus codes in current implementation.

Edit2: If I were you I would ditch the "Run State" and added only "EMS Mode" as select. 😉

Edit3: That update interval difference could maybe work but only if there are no overlaps over register 0x09C4.

[davidrapan]

Hey @murik85,

I evaluated your input as a valid feature request and thus implemented requesting to separate modbus memory areas in feat: Add requesting to separate modbus memory areas

Now you can define multiple entities with the same register addresses which are read using different modbus function codes.

Test from your side would be appreciated.

Thanks.

[davidrapan]

It does look like the requests are generated properly:

{'code': 3, 'start': 211, 'end': 211, 'len': 1}
{'code': 3, 'start': 2500, 'end': 2500, 'len': 1}
{'code': 3, 'start': 3000, 'end': 3000, 'len': 1}
{'code': 4, 'start': 500, 'end': 560, 'len': 61}
{'code': 4, 'start': 1002, 'end': 1027, 'len': 26}
{'code': 4, 'start': 1503, 'end': 1514, 'len': 12}
{'code': 4, 'start': 2000, 'end': 2008, 'len': 9}
{'code': 4, 'start': 2500, 'end': 2515, 'len': 16}
{'code': 4, 'start': 3004, 'end': 3017, 'len': 14}

Can you enable debug log and show me if are the values requested according to the table above?

[murik85]

home-assistant_solarman_2024-11-01T04-08-19.480Z.log

[davidrapan]

Ahhhh okay.. I found the issue.... data are overridden during processing. I'll try to fix it and will let you know. 😉

[davidrapan]

Should fix: Modbus data overwriting during processing

[murik85]

That's perfect. It's working.
Reads, writes, switches without any problems. And then the tests... tests...

Thank you.

[davidrapan]

Could you please help me test and evaluate if custom sensors added into the afore_hybrid.yaml file are working?

• Power losses
• Today's Losses
• Total Losses

You can maybe add them into your custom one, they are imo really valuable. 😉

[davidrapan]

And what are those respective values for those sensors? (Grid Import/Export PV and Load)

[davidrapan]

BTW I noticed that you are incorrectly using state_class: "total" it should be always state_class: "total_increasing" in almost 99% of cases.

state_class: "total" is for sensors which can go into negative numbers. For example if you have Grid both Import and Export as single entity, and so...

[murik85]

The values are minimal because I restarted the inverter. After restarting, the values are not saved in the inverter memory.

"total" > "total_increasing" - Corrected. Thank you.

[davidrapan]

The values are minimal because I restarted the inverter. After restarting, the values are not saved in the inverter memory.

Ah okay so let's see tomorrow. 😉

"total" > "total_increasing" - Corrected. Thank you.

Sure thing!

Could you maybe provide your modbus documentation you have for your device? So I can update the one in the wiki. 😉

[murik85]

https://github.com/user-attachments/files/17560226/Afore.communication.protocol.v1.4.xlsx