Registers 0xF103 and 0xF105 (in code) or should it be 0xF104 and 0xF106 (in specs). Which ones are correct?

[nessnaj]

Hi, first of all, thanks a lot for providing solaredge_modus! I have used it last year as an example for making a similar interface to the Alfen Eve Charger that I use with my Domoticz system.

Now, I am using solaredge_modbus 0.8.0 and looking for ways to influence the power output of the SolarEdge inverter. So far, I have not been able to achieve the proper results, but while troubleshooting, I noticed an apparent difference between the code and the specifications.

solaredge_modbus/src/solaredge_modbus/__init__.py

Lines 498 to 499 in 28f86ea

	"reactive_power_config": (0xf103, 2, registerType.HOLDING, registerDataType.INT32, int, "Reactive Power Config", REACTIVE_POWER_CONFIG_MAP, 4),
	"reactive_power_response_time": (0xf105, 2, registerType.HOLDING, registerDataType.UINT32, int, "Reactive Power Response Time", "ms", 4),

Here I see register 0xF103 ad 0xF105.

While I see in the specification document: documents/application_note_power_control_configuration-v1.3.pdf on page 7:

Here I see register 0xF104 ad 0xF106.

Which one is correct? I have tried to use both references to see if I could write to the registers: with 0xF103 and 0xF105 I get no error message (so response 0 in register 0xF100 after attempt to commit), but the two registers are not being updated, while using 0xF104 and 0xF106 I see values being updated, but once I want to commit the changes (writing 1 to 0xF100), I get an error code in register 0xF100.

I am looking for guidance why the code seems to be different from the specifications. I guess there has been a good reason for it, but I have not been able to find out. Do I miss something?