EG4-3000 writing attributes

[gcamp]

I've been trying to write attributes to my EG4 3000EHV-48 without success.

After fiddling a bit with config, I have write commands working correctly. However, they never succeeded.

I've also tried sending messages directly with pymodbus and I have the same results. However, I've had solar assistant able to write settings successfully. Restarting the inverter changes nothing.

What can I try to get this working?

DEBUG:pymodbus.logging:Adding transaction 0
DEBUG:pymodbus.logging:Getting transaction 0
DEBUG:pymodbus.logging:Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
INFO:.transport_base[transport.0]:WRITE: 3 => 0 ( 3 => 0 ) to Register 331
DEBUG:pymodbus.logging:Current transaction state - TRANSACTION_COMPLETE
DEBUG:pymodbus.logging:Running transaction 16
DEBUG:pymodbus.logging:SEND: 0x1 0x6 0x1 0x4b 0x0 0x0 0xf8 0x20
DEBUG:pymodbus.logging:Resetting frame - Current Frame in buffer - 
DEBUG:pymodbus.logging:Changing state to IDLE - Last Frame End - 1756776146.841775 Current Time stamp - 1756776146.85286
DEBUG:pymodbus.logging:New Transaction state "SENDING"
DEBUG:pymodbus.logging:Changing transaction state from "SENDING" to "WAITING FOR REPLY"
DEBUG:pymodbus.logging:Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 4 bytes (0 received)) 

[gcamp]

Well I had to create an issue to find the solution. Seems the EG4 3000 has a buggy firmware and can't respond to x06 calls but only to x10.

client.write_register(331, 0) fails
but
client.write_registers(331, [0]) works

[HotNoob]

partial modbus implementations are kinda common. i'll have to add in a x06/x10 option in the future.