mzezman

this is the one SolarAssitant started using recently

Yup... Classic economics. Also panels are in very short supply as are some batteries

You can also increase battery charge amps to 50 to max out the current panels you have. When you get the second string you can increase them to 75-90amps to charge them quicker

A NUC won't work for Solar Assistant, it needs to be on a Pi.

What are the current inverter modes?

If you untick use time in system Work Mode it will use the grid to power loads and charge the batteries

Can you share your work mode screens from the inverter?

If you are on a sunsynk ask them to update firmware to the latest version - it apparently mitigates this issue

Sounds normal, especially if there is load on the inverter (either AC or DC) you can change the fan settings in Menu option 29 i think

Good callout - OP should have the detail

Thanks for the screens - the system is working as intended. The installer set it up such that AC (grid) [AC First setting] will be used first between 00:00 and 23:59 (screenshot 1). So between those times the inverter and house will ALWAYS use grid first - regardless of what is happening with solar. If there is no grid - which you observed - then the solar kicks in. Additionally the settings [AC Charge] show that the battery is to be charged from the grid at all times between 00:00 and 23:59 (screenshot 2) If you want the solar to be primary use during the day then Set your AC first time to be outside of daytime hours, e.g. 17:00-05:00 - this means between 5pm and 5am it will use grid first - you can change those settings on the app in the AC first row. You have 3 AC first rows (1-3) so you can chop and change as you see fit. Set your AC charge times accordingly - remember - during the AC charge time it will recharge your batteries from the grid. So only do this if you absolutely want to charge batteries from the grid If you look at my screenshots you'll see that i have not set a timeframe for AC first - so the inverter will never use grid to power loads I do have an AC charge setting for 23:15 - 23:45 - as this system only has 1 battery I top it up just in case Find AC first and AC charge settings that work for you as those determine when the grid is used. Outside of those times the system will use DC (solar and Battery). Additionally (to further complicate things) if you click [Take Load together] the system will blend AC, PV and Battery to meet the load requirements. start with the 2 above then once you have that set you can try this 3rd complication goodluck 🙂

Also - from another thread on another forum - make sure you're on the latest Solar Assistant version - it might help with some fo the functions

How many panels and how are they connected to the inverter? When you say you get more power from the grid than the panels, in which situations does this happen? What is the battery % when this happens? Can you share your settings from the app? These screens specifically

I can take a better look at this tomorrow if that's OK? In essence the action that is triggered will be an MQTT publish message and the payload will be something like that code snippet

Per string yes. The 360V - how / where did you calculate this?

Has anything changed in your wifi setup? New router or access point? Could you also check if there is a nearby AP broadcasting on the same frequency as yours? if so then you can change your frequency and see if that helps? 2.4ghz bands are very oversubscribed so lots of interference

Looking back at the original post it goes down to 90% DOD (10% SOC)

Change this line ((states('sensor.battery_state_of_charge') | float * 9.6 * 10) to ((states('sensor.battery_state_of_charge') | float * 27.5 * 10) If you have the mushroom cards add-on then you can use a mushroom template card like this type: custom:mushroom-title-card title: '' alignment: center subtitle: | Battery runtime {{ states('sensor.soc_battery_depletion_backup_circuit_formatted_no_ago') }} at current ({{states('sensor.load_power') }}W) load If you do not have that add-on then just use a normal Markdown card type: markdown content: |2 Battery runtime {{ states('sensor.soc_battery_depletion_backup_circuit_formatted_no_ago') }} at current ({{states('sensor.load_power') }}W) load

Template sensors to be created in configuration.yaml: - platform: template sensors: soc_battery_depletion_seconds_backup_circuit: friendly_name: "Battery Depletion Seconds - Backup Circuit" unit_of_measurement: Seconds value_template: "{{ (((states('sensor.battery_state_of_charge') | float * 9.6 * 10) - 960 - 60) / ((states('sensor.load_power')) | float) * 60 * 60 ) | timestamp_custom('%s', 0)}}" soc_battery_depletion_backup_circuit_formatted_no_ago: friendly_name: "Battery Depletion No Ago - Backup Circuit" value_template: > {% set time = states('sensor.soc_battery_depletion_seconds_backup_circuit') | int %} {%- set minutes = ((time % 3600) // 60) %} {%- set minutes = '{} minutes'.format(minutes) if minutes > 0 else '' %} {%- set hours = ((time % 86400) // 3600) %} {%- set hours = '{} hours, '.format(hours) if hours > 0 else '' %} {%- set days = (time // 86400) %} {%- set days = '{} day, '.format(days) if days > 0 else '' %} {{ 'Less than 1 minute' if time < 60 else days + hours + minutes }} YAML to display: Battery runtime {{ states('sensor.soc_battery_depletion_backup_circuit_formatted_no_ago') }} at current ({{states('sensor.load_power') }}W) load The above is for a 9.6kwh battery bank. Edit: Credit to the developer (PilgrimtoHyperion on MyBB) - i just cut and paste 🙂 @PilgrimToHyperion

Hi Ahmed It could be the startup current of the pump that is the issue - so although it may only run at 650w - its initial startup may be higher than what the growatt can handle. Does the inverter show any errors?

Anything above 13a will be clipped by a Sunsynk/Deye. Not sure about others

Pylontech is one of the easier ones to add - their intra-battery cables are snap-on and the comms cables are standard ethernet cables. You should be able to add it yourself if you are so inclined

It looks to be a very new site (less than 3 months) and operation - i would stay away unless someone can give actual proof they are legit.

There currently isn't a way built into SA to do this - you would have to extract the data for each graph manually. If, however, you have SA integrated into Home Assistant then you could write the data from the MQTT messages into something like Graphana and manipulate it there

2 If installed inside you will definitely hear it when it ramps for load (charging batteries, drawing from batteries). You can change the fan curve speed settings to make it quieter but it's not silent