Replies: 1 comment
-
never mind, figured it out. It was the limitation on the input_number that the response was being stored in rather than the DoD value itself. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've recently setup the GoodWe experimental integration with a GEH-10 (General Electric rebadged GoodWe) and LR RESU16H Prime battery. This battery advertises having 100% of it's energy usable, so a Depth of Discharge of 100% (I won't get into whether that's good for battery longevity - probably not). However the integration appears to have a hard limit of 95% (ie 5% remaining). If I set something lower than that using goodwe.set_parameter service it completes ok, but then the message below is returned from the goodwe_get_parameter service:
"Failed to call service goodwe.get_parameter. Invalid value for input_number.battery_dod_limit: 4.0 (range 5.0 - 20.0). Got {'type': 'execute_script', 'sequence': [{'service': 'goodwe.get_parameter', 'data': {'device_id': '8b2a201be4, 'entity_id': 'input_number.battery_dod_limit', 'parameter': 'battery_discharge_depth'}}], 'id': 45}"
(see #109 - lower limits appear to be set but actually don't apply)
Is it possible to make the limit 0% or 1%, or is that too risky?
Beta Was this translation helpful? Give feedback.
All reactions