Battery not recognized #58
Replies: 2 comments 4 replies
-
|
Hi @janreimen, Most of the output makes sense, but this is an issue: "batteries": { We will need to get in touch with the maintainer (nmakel) of the solaredge modbus library to figure out why the I will update the plugin to support (some of) the values reported by your battery over the next few days. Let's see if we can make that work. I will come back to you as soon as I have updated the plugin. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I will keep a look on my e-Mails then for the solaredge_modbus part and thanks in advance for supporting my installation :) |
Beta Was this translation helpful? Give feedback.
-
|
Hey @janreimen, I have added battery support to the plugin. Be aware: this is a first attempt and will probably result in errors. Once you have upgraded the plugin, you will need to restart Domoticz.
Please select Please share the logs and screenshots :-) |
Beta Was this translation helpful? Give feedback.
-
|
Hi Addie, I cloned the Plugin 2.0.2 from my Production Raspi4 (Python 3.7 / solaredge_modbus 0.7.0) to version 2.0.3 on my testing machine (having Python 3.9 and therefore also solaredge_modbus 0.7.2). Unfortunately no changes yet (Logs are below), the Battery is still not shown. For the logs WR Batt Plugin has the settings as below 2022-12-28 19:28:19.817 WR Batt: Worker thread started. |
Beta Was this translation helpful? Give feedback.
-
|
Found the issue. I forgot to complete that part of the code yesterday. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, No problem, you will get an e-Mail from me in the next minutes :) |
Beta Was this translation helpful? Give feedback.
-
As requested the results of the example.py for both IP Adresses of both inverters :
The System Master (Modbus ID = 1) is well recognized under Domoticz (Beta), Python 3.7, your plugin version 2.0.2
Attached to this Master (Modbus ID = 2) is the Solaredge Meter that is also well recognized and reporting data to Domoticz. When running the example.py without parameters, the script falls into timeouts. Also attached to the Master is an LG RESU 16H Battery with Modbus ID = 15. A topic where I will have to investigate is if I have to query this device through a 3rd IP Address or if I will be able to have it reported as well through the Plugin connected to the Master device
The system Slave is the roof connected 3phase SE16K (Modbus ID = 3) that is also well recognized under Domoticz (Beta), Python 3.7, your plugin version 2.0.2
2022-12-27 17:34:47.190 SolarEdge WR Batt: device: Inverter values: {
2022-12-27 17:34:47.190 "c_deviceaddress": 1,
2022-12-27 17:34:47.662 SolarEdge WR Batt: device: Meter1 values: {
2022-12-27 17:34:47.662 "c_deviceaddress": 2,
2022-12-27 17:34:49.136 SolarEdge WR Roof: device: Inverter values: {
2022-12-27 17:34:49.136 "c_deviceaddress": 3,
pi@raspberry4:~/solaredge_modbus $ ./example.py 192.168.178.102 1502 --json
{
"c_id": "SunS",
"c_did": 1,
"c_length": 65,
"c_manufacturer": "SolarEdge",
"c_model": "SE6000H-RWS00BNO4",
"c_version": "0004.0016.0025",
"c_serialnumber": "74072E92",
"c_deviceaddress": 1,
"c_sunspec_did": 101,
"c_sunspec_length": 50,
"current": 33,
"l1_current": 33,
"l2_current": 0,
"l3_current": 0,
"current_scale": -2,
"l1_voltage": 2312,
"l2_voltage": 0,
"l3_voltage": 0,
"l1n_voltage": 2312,
"l2n_voltage": 0,
"l3n_voltage": 0,
"voltage_scale": -1,
"power_ac": -3007,
"power_ac_scale": -3,
"frequency": 49989,
"frequency_scale": -3,
"power_apparent": 7705,
"power_apparent_scale": -2,
"power_reactive": 7700,
"power_reactive_scale": -2,
"power_factor": -3903,
"power_factor_scale": -3,
"energy_total": 94735,
"energy_total_scale": 0,
"current_dc": 65529,
"current_dc_scale": -3,
"voltage_dc": 4091,
"voltage_dc_scale": -1,
"power_dc": -3053,
"power_dc_scale": -3,
"temperature": 2888,
"temperature_scale": -2,
"status": 4,
"vendor_status": 0,
"rrcr_state": 0,
"active_power_limit": 100,
"cosphi": 0,
"commit_power_control_settings": 0,
"restore_power_control_default_settings": 0,
"reactive_power_config": 3,
"reactive_power_response_time": 200,
"advanced_power_control_enable": 1,
"export_control_mode": 0,
"export_control_limit_mode": 0,
"export_control_site_limit": 0,
"meters": {
"Meter1": {
"c_manufacturer": "SolarEdge",
"c_model": "SE-RGMTR-1D-240C-A", --> Note that this is not the right device that is installed : technically the SE-MTR-3Y-400V-A is installed !!
"c_option": "Export+Import",
"c_version": "0",
"c_serialnumber": "0",
"c_deviceaddress": 2,
"c_sunspec_did": 203,
"c_sunspec_length": 105,
"current": 173,
"l1_current": 55,
"l2_current": 51,
"l3_current": 66,
"current_scale": -1,
"voltage_ln": 23108,
"l1n_voltage": 23108,
"l2n_voltage": 23098,
"l3n_voltage": 23066,
"voltage_ll": 0,
"l12_voltage": 0,
"l23_voltage": 0,
"l31_voltage": 0,
"voltage_scale": -2,
"frequency": 4997,
"frequency_scale": -2,
"power": -3676,
"l1_power": -1077,
"l2_power": -1082,
"l3_power": -1517,
"power_scale": 0,
"power_apparent": 3898,
"l1_power_apparent": 1174,
"l2_power_apparent": 1197,
"l3_power_apparent": 1549,
"power_apparent_scale": 0,
"power_reactive": 1295,
"l1_power_reactive": 468,
"l2_power_reactive": 512,
"l3_power_reactive": 315,
"power_reactive_scale": 0,
"power_factor": 9333,
"l1_power_factor": 9139,
"l2_power_factor": 8999,
"l3_power_factor": 9860,
"power_factor_scale": -2,
"export_energy_active": 43839,
"l1_export_energy_active": 65177,
"l2_export_energy_active": 77483,
"l3_export_energy_active": 78631,
"import_energy_active": 385187,
"l1_import_energy_active": 227158,
"l2_import_energy_active": 130072,
"l3_import_energy_active": 205409,
"energy_active_scale": 0,
"export_energy_apparent": 0,
"l1_export_energy_apparent": 0,
"l2_export_energy_apparent": 0,
"l3_export_energy_apparent": 0,
"import_energy_apparent": 0,
"l1_import_energy_apparent": 0,
"l2_import_energy_apparent": 0,
"l3_import_energy_apparent": 0,
"energy_apparent_scale": -32768,
"import_energy_reactive_q1": 0,
"l1_import_energy_reactive_q1": 0,
"l2_import_energy_reactive_q1": 0,
"l3_import_energy_reactive_q1": 0,
"import_energy_reactive_q2": 0,
"l1_import_energy_reactive_q2": 0,
"l2_import_energy_reactive_q2": 0,
"l3_import_energy_reactive_q2": 0,
"export_energy_reactive_q3": 0,
"l1_export_energy_reactive_q3": 0,
"l2_export_energy_reactive_q3": 0,
"l3_export_energy_reactive_q3": 0,
"export_energy_reactive_q4": 0,
"l1_export_energy_reactive_q4": 0,
"l2_export_energy_reactive_q4": 0,
"l3_export_energy_reactive_q4": 0,
"energy_reactive_scale": -32768
}
},
"batteries": {
"Battery1": {
"c_manufacturer": "LG",
"c_model": "EH257064P8S1DMA2206081106",
"c_version": "DCDC 1.2.18 BMS 2.3.0.4",
"c_serialnumber": "2206081106",
"c_deviceaddress": 15,
"c_sunspec_did": 0,
"rated_energy": 16038.0,
"maximum_charge_continuous_power": 7000.0,
"maximum_discharge_continuous_power": 7000.0,
"maximum_charge_peak_power": 65535.0,
"maximum_discharge_peak_power": 65535.0,
"average_temperature": 13.399999618530273,
"maximum_temperature": 0.0,
"instantaneous_voltage": -3.4028234663852886e+38,
"instantaneous_current": -3.4028234663852886e+38,
"instantaneous_power": -3.4028234663852886e+38,
"lifetime_export_energy_counter": 94387,
"lifetime_import_energy_counter": 91420,
"maximum_energy": 16038.0,
"available_energy": 16038.0,
"soh": 100.0,
"soe": 4.099999904632568,
"status": 10,
"status_internal": 10,
"event_log": 0,
"event_log_internal": 0
}
}
}
Originally posted by @janreimen in #41 (reply in thread)
Beta Was this translation helpful? Give feedback.
All reactions