-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommended full charge interval #268
Comments
Hi Sven, it’s not that important, but to keep the batteries well calibrated (also in winter) I’d say a couple days. It also depends on your peak panel power. |
I have 2kwp with an AB2000 battary. So a good start is to set full_charge_interval to 120? |
My current config looks so, is this good: [global]
# DTY Type: either OpenDTU or AhoyDTU
dtu_type = OpenDTU
# Smartmeter Type: either Smartmeter (generic, Tasmota, Hichi, ...), PowerOpti, ShellyEM3
smartmeter_type = Smartmeter
[solarflow]
# The product ID specifies the model of Solarflow hub to use: Hub-1200: "73bkTV" Hub-2000: "A8yh63"
# defaults to 73bkTV
product_id = A8yh63
# The device ID of your Solarflow Hub (typically 8 characters), you can get these either with solarflow-bt-manager or the solarflow-statuspage
device_id = *******
# The time interval in hours that solarflow-control will try to ensure a full battery
# (i.e. no discharging if battry hasn't been at 100% for this long)
full_charge_interval = 120
# Let solarflow-control take over enabling/disabling the bypass of the hub (direct solarinput to hub output when battery is full)
# this overrides the automatic switching by the hub's firmware, which is sometimes a bit wierd
control_bypass = true
[mqtt]
# Your local MQTT host configuration
mqtt_host = *****
#mqtt_port =
mqtt_user = *****
mqtt_pwd = ******
[opendtu]
# The MQTT base topic your OpenDTU reports to (as configured in OpenDTU UI)
base_topic = solar
# your Inverters serial number
inverter_serial = *****
# List of indices of the inverter channels/ports (as reported in the DTU) that the Solarflow Hub is connected to
# typically the index starts at 1 as 0 is the output channel of the inverter
# e.g. 1,3 or 3 or [1,3]
sf_inverter_channels = [1,2]
[smartmeter]
# The MQTT base topic your Hichi, Tasmota, generic smartmeter reader reports to
base_topic = sensors/sml/******
# if the published value at the base_topic is a JSON type then these accessors are used to get the power values
# e.g. if Smartmeter reader posts { "Power": {"Power_curr": 120, "Total_in": 12345.6} }
cur_accessor = smartmeter_wirkleistung_w
total_accessor = smartmeter_wirkarbeit_verbrauch_total_wh
# rapid change difference defines the difference in W that has to be detected on the smartmeter readings to consider it a fast drop or rise in demand.
# this helps a faster adjustment in switching various limits e.g. when a water boiler is turned on/off
rapid_change_diff = 500
zero_offset = 20
[control]
min_charge_power = 0
max_discharge_power = 150
max_inverter_limit = 800
limit_inverter = true
inverter_min_limit = 10
battery_low = 10 |
I think there's something wrong with my configuration. The sun ist mostly gone, battery is full but it's not using the battery. What is wrong: 2024-06-24 14:34:09,224:INFO: HUB: S:60.0W [ 60.0,60.0 ], B:100% (100), V:50.5V (50.5), C: 0W, P:True (manual, not possible), F:0.0h, E:-1.0h, H: 57W, L: 0W
2024-06-24 14:34:09,224:INFO: INV: AC:106.4W, DC:208.2W (33.1|33.0|73.6|74.3), L:799W (199.8W/channel) [ -1W]
2024-06-24 14:34:09,224:INFO: SMT: T:Smartmeter P:338.0W [ 338.0,338.0 ]
2024-06-24 14:34:09,225:INFO: Direct connected panels (80.4W) can't cover demand (434.4W), trying to get 354.0W from hub.
2024-06-24 14:34:09,225:INFO: Based on time, solarpower (60.0W) minimum charge power (0W) and bypass state (True), hub could contribute 400.0W - Decision path: 0.2.
2024-06-24 14:34:09,225:INFO: Hub should contribute more (400.0W) than what we currently get max from panels (40.4W), we will use the inverter for fast/precise limiting!
2024-06-24 14:34:09,225:INFO: Hub has recently adjusted limit, need to wait until it is set again! Current limit: 0, new limit: 0.0
2024-06-24 14:34:09,225:INFO: Not setting inverter output limit as it is identical to current limit!
2024-06-24 14:34:09,225:INFO: Sun: 05:19 - 21:53 Demand: 434.4W, Panel DC: (80.4W), Hub DC: (36.0W), Inverter Limit: 800.0W, Hub Limit: 0.0W
2024-06-24 14:34:09,226:INFO: SMT triggers limit function: 338.0 -> 338.0: executed
2024-06-24 14:34:17,310:INFO: Reading last full time: 2024-06-24 14:34:17
2024-06-24 14:34:17,352:INFO: Reading battery target mode: discharging |
Your Bypass is still activated. Bypass means all solar input is delivered straight into your home. It is triggered, when the hub reaches 100%. There are a few possibilities:
- There is a config option: *control_bypass*. If set true, solarflow-Control will activate or deactivate bypass. If set false, you have to do this on your own, or set bypass to 0 (automatic)
|
What do you recommend, activate or not bypass control? |
I would recommend activating it or controlling it over home assistant, for me it works best with a home assistant automation.
|
I dont have Home Assistant, it's my next project after solar is working I expect :-) |
You have a Hub2k. Hub2k has issues with reporting the bypass state properly (behaves different when in auto mode or in manual mode). |
Also you haven't set the sunrise/sunset offset. So sfcontrol will by default only start discharging after sunset. To change that you can adjust these offset times:
|
Thanks for your help :-) |
@reinhard-brandstaedter |
@reinhard-brandstaedter ich wechsel mal kurz auf Deutsch, weil das jetzt gerade leichter ist für mich :D Ich habe den SunsetOff mal auf 6h gesetzt. Durchdurch greift das bei mir jetzt. Kurz zu mir, ich bin Softwareentwickler für hochverfügbare Systeme aus Mönchengladbach. |
Hi @sturowski, Ein typischer Bypass switch sollte also so aussehen: Mich wundert dass Verhalten dass quasi der ByPass nicht anspringt. Das gabs am Anfang (ältere Firmware) mal, aber in einer aktuellen Version sollte das nicht mehr passieren. Das mit dem "virtuellen bypass" wird IMO auch nicht so zuverlaessig funktionieren. Entweder man setzt dann die Ladegrenze auf 95% und den Bypass auf off. Dann wuerde der Hub trotzdem den SolarInput runterregeln wenn z.b. kein Demand vom Wechselrichter kommt (z.b. der WR auf > SolarInput des hubs geregelt ist). |
Hey @reinhard-brandstaedter, |
Hi @sturowski ,
Was heisst bei dir "keine Sonne mehr"? Den Bypass schaltet er (im auto modus) wirklich erst wieder aus wenn ca. < 15W (hub Eigenbedarf) anliegt. Da muss es schon sehr dunkel sein. |
Erstmal mein Setup: Die Anker war im Set mit dabei bei den Modulen und dem WR, das Zendure habe ich nachgekauft, weil steuerbar. Da habe ich nicht so genau drauf geachtet, kann sein, dass da noch über 15W waren. Sprich man würde dann in kauf nehmen, dass in der Zeit, wo der Bypass an ist viel Strom eingekauft wird und der Akku wird dann in der Nacht nur verwendet? |
Tatsaechlich ist es so dass es ein Zeitfenster gibt (sunset - offset) ab dem Einspeisen aus der Batterie erlaubt wird. Wenn der Bypass an ist und den Bedarf noch decken kann wird dieser nicht ausgeschalten. Wenn allerdings der Bedarf in diesem Fenster höher ist als was mit Bypass reinkommt dann wird dieser ausgeschalten. (natürlich vorausgesetzt dass die bypass Steuerung funktioniert - was ja im falle des hub2k immer noch fraglich ist). Darum sieht man im log auch soetwas wie possible|not possible:
|
@reinhard-brandstaedter das Problem hat sich jetzt in soweit gelöst, wir haben unseren Pool jetzt aufgebaut und die Pumpe läuft in Summe 14h am Tag, der Akku wird gar nicht mehr voll :D außer halt dann alle paar Tage. |
Naja, im winter wirst du dann das Thema wieder haben. |
Produziere ich da trotzdem so viel Solarstrom, dass das passiert? Wie sind denn da so deine Erfahrungen? |
Dear Contributors,
I'm completly new in solar (since 3 weeks). Can you tell me what is the beste interval for fully charge my battaries? I mean the config param: full_charge_interval
And why :-)
Thanks!
Sven
The text was updated successfully, but these errors were encountered: