Replies: 6 comments 8 replies
-
|
Yes that is possible. You would do it by controlling the maximum charge current (it’s DC, to the charge power multiply it by your battery volts) Probably easiest to have a simple automation that sets it to a lower value at night for when you charge from grid, and then reset it to 40A (the default) for day time charging from PV. |
Beta Was this translation helpful? Give feedback.
-
|
That sounds perfect - please forgive my ignorance but how do I set the maximum charge current from home assistant. I was unsure what sensor to set. |
Beta Was this translation helpful? Give feedback.
-
|
Aaah yes I spotted it straight away, it’s definitely a subtle one There are 2 types of number set service call, one for number helpers (input_number.set_value) and one for number entities (number.set_value). You have used the input_number.set which won’t work here as it is a number entity - you’ll need to change this line
to
You can test it to make sure it is working, when you are in the automation, the 3 dots to the right hand side of each action drops down a menu and you can ‘run’ each action independently from there - if you open another tab and watch the value of |
Beta Was this translation helpful? Give feedback.
-
|
So I tried this and its not working either. The register. I have also tried to display number.foxess_max_charge_current and it is showing as unavailable on the dashboard. The logs did throw up this curious error though: Logger: custom_components.foxess_modbus.modbus_controller tcp://192.168.8.60:502 247 - 5 failed poll attempts: now not connected. Last error: Error reading registers. Type: RegisterType.HOLDING; start: 31000; count: 55; slave: 247 from tcp://192.168.8.60:502: Exception Response(131, 3, IllegalAddress) could this be a problem with the inverter? I havent upgraded the firmware since I got it as I read on this forum that there were issues with later ones: Master version: 1.18 many thanks in advance in your help |
Beta Was this translation helpful? Give feedback.
-
|
Ok yes agree, I think that’s the problem here, you need to be on the latest version of KH firmware and also the latest version of this integration. The latest versions for the KH are now - These are much more stable than the inter-mediate firmware releases. Can you arrange to get them updated at your convenience, then once you’ve done that make sure that you are on the latest beta version of the modbus integration (as of today it’s v1.10.2b5) |
Beta Was this translation helpful? Give feedback.
-
|
Update should be done in next 48 hours. Also sorry but is there an obvious way to force an upgrade to the latest beta? have looked all over the integration in HA and cant find a way to do this. Sorry if I have missed something obvious |
Beta Was this translation helpful? Give feedback.
-
|
Great, hopefully not long to wait 👍 On the beta versions probably easiest if I link you to this description hacs beta |
Beta Was this translation helpful? Give feedback.
-
|
That is brilliant - thank you!
…
On Apr 16, 2024 at 3:52 PM, <Dave Foster ***@***.***)> wrote:
The sensor to modify is:- number.max_charge_current
You can set it like this in an automation action as follows -
IMG_1576.jpeg (view on web) (https://github.com/nathanmarlor/foxess_modbus/assets/113460294/e3913b03-8910-4572-87e0-63a7a7eac4b7)
—
Reply to this email directly, view it on GitHub (#595 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AGLBCT4CWE7LND4OWX5AH53Y5U3JNAVCNFSM6AAAAABGJHTWBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCMZRGI4TA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
So I tried that last night and unfortunately that didnt seem to work. As soon as the battery charge kicked in, the current went up to nearly 40 Amps. This is the code I used in the automsation (which Ran with no issues):
Any suggestions would be appreciated. Thanks a gain for all your help |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Dave - that is amazing support. You are a true gent.
…
On Apr 17, 2024 at 8:42 AM, <Dave Foster ***@***.***)> wrote:
Aaah yes I spotted it straight away, it’s definitely a subtle one
There are 2 types of number set service call, one for number helpers (input_number.set_value) and one for number entities (number.set_value).
You have used the input_number.set which won’t work here as it is a number entity - you’ll need to change this line
service: input_number.set_value
to
service:number.set_value
You can test it to make sure it is working, when you are in the automation, the 3 dots to the right hand side of each action drops down a menu and you can ‘run’ each action independently from there - if you open another tab and watch the value of number.foxess_max_charge_current you should see it change.
—
Reply to this email directly, view it on GitHub (#595 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AGLBCT26KV554GWJI3TCHPDY5YRUPAVCNFSM6AAAAABGJHTWBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCMZYHAZTG).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
ok perfect - thank you. I cant believe how quickly you respond. this is really great.
…________________________________
From: Dave Foster ***@***.***>
Sent: 18 April 2024 17:30
To: nathanmarlor/foxess_modbus ***@***.***>
Cc: cperricos ***@***.***>; Author ***@***.***>
Subject: Re: [nathanmarlor/foxess_modbus] KH10 limit battery charge current (Discussion #595)
Ok yes agree, I think that’s the problem here, you need to be on the latest version of KH firmware and also the latest version of this integration.
The latest versions for the KH are now -
Master: 1.30
Manager: 1.22
These are much more stable than the inter-mediate firmware releases.
Can you arrange to get them updated at your convenience, then once you’ve done that make sure that you are on the latest beta version of the modbus integration (as of today it’s v1.10.2b5)
—
Reply to this email directly, view it on GitHub<#595 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGLBCT3L7JSURBQHRIONHUTY57YLTAVCNFSM6AAAAABGJHTWBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNJXGMYTC>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot Dave. The latest beta appears to have worked! Still getting some connection errors but will check once the firmware has been upgraded.
Thanks
Costi
…
On Apr 18, 2024 at 6:30 PM, <Dave Foster ***@***.***)> wrote:
Great, hopefully not long to wait 👍
On the beta versions probably easiest if I link you to this description hacs beta (https://hacs.xyz/docs/faq/beta/)
—
Reply to this email directly, view it on GitHub (#595 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AGLBCT2ACBGSQT4TWVP4YPTY577KZAVCNFSM6AAAAABGJHTWBOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNJXHA4TE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hello,
I have a new Fox ess solar KH10 installation and love the modbus integration. I would like ideally to manage the loads on my supply (I need to keep it under 80A), and so ideally would want to limit the charge current to the batter when I top up the battery at night as it can pull up to 10KW. Is there a way of doing this via HA?
many thanks
Beta Was this translation helpful? Give feedback.
All reactions