Richyrich

Unfortunately I am sold out and none of the local shops have any stock of the parts needed. 
I ordered some samples from China and if they are any good I will order larger quantities.
I am working on 2 different designs, we will see where it leads. Realistically we are looking at the end of September.
You are welcome to subscribe to this thread for now. I will post updates.

Thank you for posting the snippet, clearly there is a way to define numbers/switches/sensors etc via MQTT then. Having native Home Assistant types helps to make the integration a lot better. When I built my first MQTT integration  (Daly BMS Bluetooth -> MQTT) I was not aware of the types so it made the integration a pain to work with
Clearly I need to revisit the howto of HA MQTT

Could you please post an example integration you are using to adjust inverter values/settings. Be interested to see the level of detail required.
I wrote a Bluetooth DALY BMS to MQTT integration, and I quickly discovered that working with MQTT works for the basic case like a switch but quickly becomes troublesome for anything with properties and settings
Using something like "scenes" with the video above will not be achievable through MQTT. Well technically you could define a number, add onChange triggers that would send MQTT messages, but that seems like a lot of work to change a value in the first place.
"Technically possible" does not mean everyone would want to build their smart home like that

@Richyrich Yes both are available. It did put considerable effort towards getting all the available values on the inverter (reverse engineering what I could), wrote several workarounds for the bugs in the framework so it would work. There are something in the 140 entities (granted some are for the american split-phase setup and not useful to us in SA) I provided my workarounds to the opensource community to help them overcome some limitations. 

My thinking was that I could save someone a couple of weeks of their time it must be worth something to them. Build the hardware, test it, polish the software so the whole experience is a smooth 10 minute setup.
But some people want to build their own dongle, that is cool too
Thank you @johanp for answering. I see you are enjoying the dongle you bought.
You can toggle grid charge and specify the Amps that the grid must charge. You could easily change these via automations if you need different profiles for different days
The time of use menu allows you to change the time (formatted as a time) power, SOC, and the charge settings you can get the exact same values than the time of use menu on the inverter. You could add an automation that changes your time of use for each day of the week, (eg my weekend usage is different than the week)

Hi
That’s very possible with this:
 

 
and Home Assistant. 

If you have Home Assistant, try this: 
 

I agree, the more I'm thinking of this question raised by Richy, the better it is looking.
I'd be keen to watch that video @Sc00bs

On rainy days I monitor the daily battery charge in kWh, if by 12 I have not reached a certain minium amount I change my setting to become "priority Battery" that means, my inverter will run from the grid (till it reaches the time of use SOC) en every little bit of sunshine charges my battery. Those days I might only get to 70% battery but I am at least not charging from the grid. Every evening an automation changes my automation back to "priority load".
That way I am giving Eskom the least amount of business , and still I do not change a thing, everything happens automatically.
Combining the Time of Use with automations can improve the effectiveness of you solar and save you money in the long run.

What is the ultimate goal, because depending on your system and the reason behind this need, could the timer settings along with percentages not get this done in the sunsynk menu?
I am asking this out loud to others, because maybe this could be possible.
 
Alternatively Scoobs, suggestion is going to work for your needs

Hi @Richyrich
I did a video on adjusting your settings based on the load shedding level from EskomSePush. 
You can use pretty much the same automation and just change the entities from ESP to Solcast and adjust the values as you want. 
Can do a video if you like 🙂 
 
 

Basically if the grid is ticked then it is the target for grid charging and if there is no tick then its the minimum SOC that the batteries will no longer be used. 
No tick on 40% will use batteries to 40% SOC. Tick in grid charge will result in batteries being charged from the grid until they reach 40%.

Correct.  But one thing I forgot - you must check 'Use Timer' as well.  If not checked, then battery is only used when grid is not available (and charging is according to the battery configuration pages only).
No need to restart the inverter - settings are applied immediately.

1) Check 'Priority Load' - this will direct solar energy to first power the load, with any excess used to charge the battery.
2) Set time of use settings (you can make them all the same). Set SOC/V to your minimum acceptable battery charge. If battery charge is above this, additional load will come from batteries. When battery charge is lower than SOC, then load will be powered by grid. If you check 'Grid' for a time slot, then the battery will also charge to that SOC from grid in that time window.