Is there a reason some features / known modbus addresses are not implemented (yet)?

[hamster65]

Hi,
I wonder why some features, like system on/off, EPS on/off, are not implemented for the H3. I think the modbus addresses are known, for example 41014 for systen on/off.

[TonyM1958]

Hi, I don't have access to a H3 inverter for testing the Modbus addresses so, if someone doesn't ask for an address, it may not get added.

The addresses you mentioned are in the file as they have been verified on my H1 but they are marked tbc because they have not been verified on H3:

I'm happy to add specific sensors to a file for you if you let me know which modbus file you are using and the details for what you want to test?

[hamster65]

Hi Tony,

I used modbusH3_RS485_lan.yaml but currently I am testing Nathan's addon and also modbus writing with node-red.

This HA automation works to switch the H3 on and off: I can also read back holding and input registers.

• id: '1737231855928'
  alias: fox_on
  description: ''
  triggers: []
  conditions: []
  actions:
  • action: foxess_modbus.write_registers
    metadata: {}
    data:
    start_address: 41014
    values: '1'
    inverter: 791ef40ad930fba7c38f8ac9a6573f40
    alias: Fox_on
    mode: single
• id: '1737231929977'
  alias: Fox_off
  description: ''
  triggers: []
  conditions: []
  actions:
  • alias: Fox_off
    action: foxess_modbus.write_registers
    metadata: {}
    data:
    start_address: 41014
    values: '0'
    inverter: 791ef40ad930fba7c38f8ac9a6573f40
    mode: single