(16.02.2022, 12:43)admin Wrote: Do you have some documentation on the available registers? Without this info there's not much that can be done.

(16.02.2022, 12:48)CristianAgata Wrote:

(16.02.2022, 12:43)admin Wrote: Do you have some documentation on the available registers? Without this info there's not much that can be done.

Sorry, I solved.... Sun2000 has no modebus TCP open, but Huawei solar inverter has the RTU on pin 1 and 2.
I've done.
BR Cristian

(26.03.2023, 14:50)KoBra Wrote:

(16.02.2022, 12:48)CristianAgata Wrote:

(16.02.2022, 12:43)admin Wrote: Do you have some documentation on the available registers? Without this info there's not much that can be done.

Sorry, I solved.... Sun2000 has no modebus TCP open, but Huawei solar inverter has the RTU on pin 1 and 2.
I've done.
BR Cristian

Hi cristian, can you share the registers you used?

(28.03.2023, 18:32)fleeceable Wrote: You need dongle to communicate with Modbus TCP.
I have integrated two SUN2000. First unit communication is not the best (sometimes it gonna show wrong values or zero but controlling commands work). Haven't diagnosed that if problem is in the network, dongle or inverter. With other one all works like a charm. Make sure that dongle FW is latest.
Here is register list for SUN2000.
https://javierin.com/wp-content/uploads/sites/2/2021/09/Solar-Inverter-Modbus-Interface-Definitions.pdf

(28.03.2023, 19:19)fleeceable Wrote: Here is manual how to set Dongle:
https://forum.iobroker.net/assets/uploads/files/1648205803725-sdonglea-05-modbus-tcp-guide.pdf

No, You don't lose fusionsolar connection when controlling and monitoring inverter over modbus TCP.

I made system what I'm offering to my clients. When electricity price is low then sending command to inverter that it's time to buy from grid and charge battery. If price is high then sending command that it's time to sell.
So far have integrated SUN2000 over dongle and SmartLogger3000.
Same system works on SolarEdge and Goodwe inverters (if they have battery packs)

Let me know if you have any additional questions about connection...

(28.03.2023, 18:32)fleeceable Wrote: You need dongle to communicate with Modbus TCP.
I have integrated two SUN2000. First unit communication is not the best (sometimes it gonna show wrong values or zero but controlling commands work). Haven't diagnosed that if problem is in the network, dongle or inverter. With other one all works like a charm. Make sure that dongle FW is latest.
Here is register list for SUN2000.
https://javierin.com/wp-content/uploads/sites/2/2021/09/Solar-Inverter-Modbus-Interface-Definitions.pdf

(25.06.2023, 12:42)123einerlei Wrote:

(28.03.2023, 18:32)fleeceable Wrote: You need dongle to communicate with Modbus TCP.
I have integrated two SUN2000. First unit communication is not the best (sometimes it gonna show wrong values or zero but controlling commands work). Haven't diagnosed that if problem is in the network, dongle or inverter. With other one all works like a charm. Make sure that dongle FW is latest.
Here is register list for SUN2000.
https://javierin.com/wp-content/uploads/sites/2/2021/09/Solar-Inverter-Modbus-Interface-Definitions.pdf

Hello fleeceable,
Can you please share your modbus.json for the Huawei Sun2000 and battery system?
I will receive my PV system in a few weeks and would like to integrate it into my Schneider Homeylink.
Unfortunately I have never worked with Modbus.

(28.06.2023, 15:55)fleeceable Wrote:

(25.06.2023, 12:42)123einerlei Wrote:

(28.03.2023, 18:32)fleeceable Wrote: You need dongle to communicate with Modbus TCP.
I have integrated two SUN2000. First unit communication is not the best (sometimes it gonna show wrong values or zero but controlling commands work). Haven't diagnosed that if problem is in the network, dongle or inverter. With other one all works like a charm. Make sure that dongle FW is latest.
Here is register list for SUN2000.
https://javierin.com/wp-content/uploads/sites/2/2021/09/Solar-Inverter-Modbus-Interface-Definitions.pdf

Hello fleeceable,
Can you please share your modbus.json for the Huawei Sun2000 and battery system?
I will receive my PV system in a few weeks and would like to integrate it into my Schneider Homeylink.
Unfortunately I have never worked with Modbus.

Hi!

First I tried to use modbus template but it didn't worked out. I moved to scripting with special delays for reading and writing. On second project delays was not needed (maybe dongle firmware update has solved these problems) so you can try to use that template what I created. 
I add two files template and esf file (please change "Huawei Sun2000 Group Addresses.json" to "Huawei Sun2000 Group Addresses.esf" - can't upload esf file in here) so you can import file in Utilities -> import ESF file. Then variables is created automatically. Change group address as you need...
Also you can try to edit/remove "read_delay": 1 in json file so maybe it's not needed now.

If you have any problems, let me know.

(09.10.2023, 20:32)KoBra Wrote:

(28.06.2023, 15:55)fleeceable Wrote:

(25.06.2023, 12:42)123einerlei Wrote:

(28.03.2023, 18:32)fleeceable Wrote: You need dongle to communicate with Modbus TCP.
I have integrated two SUN2000. First unit communication is not the best (sometimes it gonna show wrong values or zero but controlling commands work). Haven't diagnosed that if problem is in the network, dongle or inverter. With other one all works like a charm. Make sure that dongle FW is latest.
Here is register list for SUN2000.
https://javierin.com/wp-content/uploads/sites/2/2021/09/Solar-Inverter-Modbus-Interface-Definitions.pdf

Hello fleeceable,
Can you please share your modbus.json for the Huawei Sun2000 and battery system?
I will receive my PV system in a few weeks and would like to integrate it into my Schneider Homeylink.
Unfortunately I have never worked with Modbus.

Hi!

First I tried to use modbus template but it didn't worked out. I moved to scripting with special delays for reading and writing. On second project delays was not needed (maybe dongle firmware update has solved these problems) so you can try to use that template what I created. 
I add two files template and esf file (please change "Huawei Sun2000 Group Addresses.json" to "Huawei Sun2000 Group Addresses.esf" - can't upload esf file in here) so you can import file in Utilities -> import ESF file. Then variables is created automatically. Change group address as you need...
Also you can try to edit/remove "read_delay": 1 in json file so maybe it's not needed now.

If you have any problems, let me know.

Hi Fleecable, 

i think there is something wrong in your profile as you did not specify the bus_datatype, just the datatype

further i see you mis also some datapoints of the list from Huawei, i would add all and just map the ones you need

further you get for example grid voltage in as 5000 but this must be devided to 50.00 Hz

If i have some more time i will tweak it.

Code:

    {
  "manufacturer": "Huawei",
  "description": "HuaweiSun2000",
  "mapping": [
    {
      "name": "Inverter Model ID",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 30070,
      "read_delay": 1
    },
    {
      "name": "Inverter State",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32000,
      "read_delay": 1
    },
    {
      "name": "Alarm 1",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32008,
      "read_delay": 1
    },
    {
      "name": "Alarm 2",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32009,
      "read_delay": 1
    },
    {
      "name": "Alarm 3",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32010,
      "read_delay": 1
    },
    {
      "name": "Inverter Phase A voltage",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32069,
      "read_delay": 1
    },
    {
      "name": "Inverter Phase B voltage",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32070,
      "read_delay": 1
    },
    {
      "name": "Inverter Phase C voltage",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32071,
      "read_delay": 1
    },
    {
      "name": "Inverter Active Power",
      "bus_datatype": "int32",
      "type": "register",
      "address": 32080,
      "read_delay": 1
    },
    {
      "name": "Inverter Grid Freaquency",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32085,
      "read_delay": 1
    },
    {
      "name": "Inverter Status",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32089,
      "read_delay": 1
    },
    {
      "name": "Inverter Fault Code",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 32090,
      "read_delay": 1
    },
    {
      "name": "Power Meter Collection - Active Power",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37113,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Running Status",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37000,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Charge And Discharge Power",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37001,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Bus Voltage",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37003,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - State Of Capacity",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37004,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Working Mode",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37006,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Rated Charge Power",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 37007,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Rated Discharge Power",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 37009,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Fault ID",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37014,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Current Day Charge Capacity",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 37015,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Current Day Discharge Capacity",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 37017,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Bus Current",
      "bus_datatype": "int16",
      "type": "register",
      "address": 37021,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Battery Temperature",
      "bus_datatype": "int16",
      "type": "register",
      "address": 37022,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit - Remaining charge/discharge time",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37025,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit 2 - State Of Capacity",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37738,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit 2 - Running Status",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37741,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit 2 - Charge And Discharge Power",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37743,
      "read_delay": 1
    },
    {
      "name": "Energy Storage Unit 2 - Battery Temperature",
      "bus_datatype": "int16",
      "type": "register",
      "address": 37752,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - State Of Capacity",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37760,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Running Status",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37762,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Charge Or Discharge power",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37765,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Current Day Charge Capacity",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 37784,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Current Day Discharge Capacity",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 37786,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Maximum Charging Power",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 47075,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Maximum Discharging Power",
      "bus_datatype": "uint32",
      "type": "register",
      "address": 47077,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Working Setting Mode SETTINGS",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 47086,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Charge From Grid Function SETTINGS",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 47087,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Grid Charge Cutoff SOC SETTINGS",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 47088,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Power Of Charge From Grid SETTINGS",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 47242,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Maximum Power Of Charge From Grid SETTINGS",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 47244,
      "read_delay": 1
    },
    {
      "name": "Energy Storage - Time Of Use Chargin And Discharging Periods SETTINGS",
      "bus_datatype": "uint16",
      "type": "register",
      "read_count:": 43,
      "address": 47255,
      "read_delay": 1
    },
    {
      "name": "Electricity Meter Status",
      "bus_datatype": "uint16",
      "type": "register",
      "address": 37100,
      "read_delay": 1
    },
    {
      "name": "Electricity Meter Grid Voltage A Phase",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37101
    },
    {
      "name": "Electricity Meter Grid Voltage B Phase",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37103
    },
    {
      "name": "Electricity Meter Grid Voltage C Phase",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37105
    },
    {
      "name": "Electricity Meter Active Power",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37113
    },
    {
      "name": "Electricity Meter Frequency",
      "bus_datatype": "int16",
      "type": "register",
      "address": 37118,
      "value_multiplier": 0.01,
      "units": "Hz"
    },
    {
      "name": "Electricity Meter Positive Active Electricity",
      "bus_datatype": "int32",
      "type": "register",
      "address": 37119
    },
    {
      "name": "Electricity Meter Reverse Active Power",
      "bus_datatype": "int16",
      "type": "register",
      "address": 37121
    }
  ]
}

(09.10.2023, 21:06)KoBra Wrote: TCP

Need to check I am not on site atm.