search

reinhard-brandstaedter / solarflow-control

A tool to automatically control Zendure's Solarflow hub with more flexibility to match home power demand
70 stars 12 forks source link

SF Control + Zendure Cloud possible? (debugging reasons) #300

Open mavo opened 22 hours ago

mavo commented 22 hours ago

Hello @reinhard-brandstaedter,

as I am facing some weird issue with my system since a while I am in an ongoing discussion with the zendure support team. The technical side asked me to connect the hub to the zendure cloud, so that they are able to debug the issue. Is there any way to have SF-control running, whilst being connected to the zendure cloud and get the required data from their servers? I don't want to lose days of statistics and also I still want to be able to use SF-control, as it just works very well.

The issue I am facing, just for the record: Around a month ago, on one evening I noticed that the battery level was dropping way faster than it should be. I had the batteries at 100% that day and around 10pm the batteries did show they had "only" 70% left - where based on the usage of power it should have been more like 85%. I checked the app by connecting via BT and it was showing that only one battery was used, the other one was still at 97%. Ever since then the battery state is all over the place for me. The problem with this comes when we are looking at min charge states, the 10% I configured is just only a number, nothing more. When I had the batteries full (such as yesterday) and I was using 3,2kWh (of the ~4kWh) it was showing its already at 10% and did shut down. This problem amplifies itself in the days after, as charging the battery on the next day will let the system think it reaches 98% (which is not 98% in reality, it shows this very very early - usually when the total power is ~2,6kWh) and then the system will drain again in the night until it reaches 10% again. But when I am checking the actual drainage from the battery, it was able to drain more then I have charged into the batteries. This continues on and one, so that 10% shown by the batteries actually sometimes in reality is more 1%. And this is bad - especially in the winter when its cold...

Well, too much text I guess - but the important question is - is there a way to have zendure cloud + sf-control woking together? I do understand, that the update intervals might be much slower, but all is better then nothing, imo.

Best, MaVo

reinhard-brandstaedter commented 18 hours ago

No there is no feature to use the Zendure Cloud as data-provider for sf-control.

Regarding your issue: I had a similar issue once and it was due to BMS drift. When was the last time you did a full charging/discharging cycle. going from 100% to 0% and back to 100%? IMO this should still be done on a regular basis to ensure the BMS is properly calibrated.

When talking to Zendure support for battery issues it's usually good enough to provide them charts of your battery metrics (per battery), min/max volatage in relation to eachother and the battery SoC. They don't get much more either from the hub when connected to their backend.

mavo commented 16 hours ago

Was there any solution to the issue for you?

I have this issue at least for a month now, and I did charge/discharge in this time at least 10 times. Without any improvement happening.

Zendure support for me was insisting in screenshots from their app, claiming that the data that I showed them was not from their app and therefore not valid...

How to get the charts of battery voltage etc? Can I have this out of home assistant, or would I need to have something else to capture and visualize?

Best, MaVo

reinhard-brandstaedter commented 13 hours ago

My observed behavior back then looked like this: image

After all this was fixed by several full cycles and eventually a BMS firmware upgrade that was released around the same time.

The individual battery voltages are reported in mqtt, you should be able to pull it into HA with a custom sensor. Similar like this one.

And you can tell support that you get these values directly from the hub with a much finer granularity than in their app (per battery).

reinhard-brandstaedter commented 13 hours ago

@mavo another thought? is your hub2k maybe already heating the battery and thus draining more (internal) power?

mavo commented 12 hours ago

@mavo another thought? is your hub2k maybe already heating the battery and thus draining more (internal) power?

Mhhh, possible. But unlikely. It wasn't that cold when the issue started. Also, the day when it started I connected to the hub via BT in their own app and saw this broken_battery (Sorry for the large image, github does not want me to have it resized :-()

This is not shown anymore in the app, but ever since then it is "kaputt".

tuxianerDE commented 5 hours ago

Hey @mavo

quick point to verify charge/discharge means that you actually did a full cycle i.e. up to 100% (till bypass kicks in) and down to 0%, because this appears to be a calibration topic as Reinhard had some time back.

Whilst I am afraid to ask/suggest, have to tried connecting only one battery and send it through this complete charge and discharge cycle and gather the data of it?