Validation error for the value which is not being set

[Unlik]

Hello, I am running on

Core 2024.11.1
Supervisor 2024.11.2
Operating System 13.2
Frontend 20241106.2
home-assistant-goodwe-inverter 0.9.9.27

with Goodwe Inverter ET series on firmware 1127. After upgrading from 0.9.9.13 to the latest 0.9.9.27 I am facing the issue:
if wants to set number.goodwe_grid_export_limit to some value e.g. 10000 then the value is set properly but still I get error:
HomeAssistantError: Validation error: Value 10000.0 for number.goodwe_fast_charging_power is outside valid range 0 - 100

So I am setting number.goodwe_grid_export_limit but got error from number.goodwe_fast_charging_power

Please note: I am automatizing in NODE-Red, so it means the error is preventing the automation from continuing on the node.

[janchlebek]

You mention in your example you are trying to set "some value e.g. 10000". Clearly in the error you see the number expected is between 0 and 100.

[Unlik]

@janchlebek Do you think so? I am trying to set goodwe_grid_export_limit in kw -> can be 0-10000 in my inverter case. And as I said: the value is set properly, but got error message for different entity goodwe_fast_charging_power

[janchlebek]

These values are normally set by percentage of inverter rated power so for example to set export limit to 2500W on 10K inverter you would enter 25. Give it a try. 😉

[Unlik]

@janchlebek Of course, I tried it, e.g. 50. Then the grid_export_limit is set to 50W (in percentage it should be 5000). And still got the same error.
So two things are on my mind:

• the settings of grid_export_limit in W working properly - should stay in W but checking the range is wrong here, too late here (bc the value is properly set) and the error message is wrong (copied from a different place)
• or settings/checking of grid_export_limit is somehow somewhere in the sources wrongly mixed with goodwe_fast_charging_power

To more precise what is returned for both values:

11 Nov 22:00:22 - [error] [api-call-service:Power Limit 50] HomeAssistantError: ILLEGAL DATA VALUE
11 Nov 22:00:22 - [error] [api-call-service:Power Limit 10000] HomeAssistantError: Validation error: Value 10000.0 for number.goodwe_fast_charging_power is outside valid range 0 - 10

But in both cases [50,10000] value si set correctly.

[zhouska]

I'd suggest to try the same I did, namely try to capture traffic to the inverter from SolarGo and see if you can set the export limit in the app. I think it will fail the same way. I'm suspecting it is a 'feature' of the 1127 firmware.

I was able to intermittently set SoC values lower than 78%, like 55% (in my case), but it isn't persistent change, more info here: #326.

Perhaps a support case with Goodwe support should be opened for the firmware in question, if I only could find the link...

EDIT: Found it: https://goodwetechnology.zendesk.com/hc/en-gb

[Unlik]

Hello @zhouska, That's a good point. I have tried to set up the export limit directly in SolarGo, and no issue has occurred. I can properly set tested values 50 or 10000 there without any errors. Also, with prior version of this integration (v0.9.9.13) I had no error.
Therefore I still think it is a valid issue of mletenay/home-assistant-goodwe-inverter in the current version v.9.9.27

[zhouska]

Hello @zhouska, That's a good point. I have tried to set up the export limit directly in SolarGo, and no issue has occurred. I can properly set tested values 50 or 10000 there without any errors. Also, with prior version of this integration (v0.9.9.13) I had no error. Therefore I still think it is a valid issue of mletenay/home-assistant-goodwe-inverter in the current version v.9.9.27

What I meant is that you could do the capture in SolarGo and in HA and compare the output. Maybe even try to replay the captured packet from SolarGo using python goodwe extension, like I did.

It did work with mixed results in my case, as I could go lower than 78% in SolarGo (at times, but changes didn't stick, and once I went over 78% and tried to go back I got same error), but replayed packets or newly crafted ones outside the SolarGo weren't accepted by the inverter. There seems to be some 'validation magic' done at inverter's side which is most likely related to how often one polls it for data...