Button to once fully charge Sessy?

[StevenLooman]

Now that winter is coming in the northern hemisphere, there will be days that the solar panels will not produce enough to charge the Sessy. Given the high/low-tariff system in The Netherlands, it would be nice if the Sessy can charge at night (lower tariff), when the next day will be a day with low/no solar power production, and discharge during the day (high tariff).

Although you can choose the manual strategy in the Sessy, it says something like: With great power comes great responsibility. Rightfully so. I don't wish to implement my own strategy (and control the Sessy). But I'd like to have a one-time-button with which I can say: Charge now until full, from net power. Yes, this is fully manual but at least the "damage" will be limited to one day, compared to a faulty strategy which keeps running.

Is this possible? Or would this be something that should be implemented on the Sessy itself? Perhaps @MartijnCharged can elaborate on this as well.

[PimDoos]

I don't think this should be implemented on the integration, but rather as an automation or script. The integration only proxies Sessy's API methods, and fully charging is not one of them. I do have a Home Assistant script in place which sets the strategy to API and starts charging until the battery is full. I'll polish it up a bit and publish it on ha-sessy-examples as a blueprint.

[StevenLooman]

I fully agree. It was mostly meant as an opener/gathering information, as I can imagine more people have the same question. Hence, also the tagging of @MartijnCharged.

I do have a Home Assistant script in place which sets the strategy to API and starts charging until the battery is full. I'll polish it up a bit and publish it on ha-sessy-examples as a blueprint.

Great, thank you!

[dacootmeister]

I don't think this should be implemented on the integration, but rather as an automation or script. The integration only proxies Sessy's API methods, and fully charging is not one of them. I do have a Home Assistant script in place which sets the strategy to API and starts charging until the battery is full. I'll polish it up a bit and publish it on ha-sessy-examples as a blueprint.

appreciated! I too am interested in such logic as a hybrid strategy may be season compatible.

[MartijnCharged]

we try to limit the amount of settings and strategies, to reduce the complexity of the system.

try to be as clear as possible when doing a feature request. make sure everyone hwo reads it has the exact same understanding of how the feature works, and what the feature is trying to accomplish.

getting to the point: @StevenLooman if i understand correctly, you would like a new strategy to charge sessy at low tarrif and nom during high tarrif?

[StevenLooman]

Thank you for your response Martijn. I appreciate you are coordinating with Pim to make sure this component works properly.

I was not asking for a new strategy (although I can see this strategy might be useful during certain times); I was asking for a one-time button to start charging up to 100%/fully charged. My idea is that if you know the next day is going to be cloudy (and thus low solar-power-production, most likely resulting in a discharged battery), you can click a button and the Sessy will charge itself from the network.

Of course, it is fully understandable (to me) you might not want to add this. A simpler product is usually better. This one-time action can probably be achieved via a blueprint or some custom strategy as already noted by Pim. On the other hand, with this button my own set-up becomes simpler. And perhaps other people might would like functionality like this as well (at least one!).

[MartijnCharged]

no thanks needed, i like doing this!

this request does have a lot of dependency's, like the expected solar power, the expected home usage and possibly even low tariff charging. i think its awesome if you manage to get this working!

however, the button brings a lot of dependency's and code complexity (bugs and 'unexpected' behavior among other things). (then you'll probably want a button to stop the action if it misfires or something.)

i will discuss this button but would recommend against, knowing this is why we even have an open mode. so i would recommend solving this with a blueprint, and maby (like xom) once everyone starts talking about it we have enough reason to implement this.

i will we watching from the sideline for this and other things that may pop up.

[jpduhen]

I think a new strategy would be nice in which the Sessy charges when not fully charged during low energy prices at nighttime, when energy prices are higher in the morning. Like in this graph: When fully charged (or when prices are going up) switch to NOM. Same with low energy prices during a cloudy day, when the solarpanels are not charging the Sessy to full, also charge at low cost, to cover evening and early night NOM. (Btw could the update yesterday be responsible for breaking my HA integration?) You're all doing a nice job!

[MartijnCharged]

@jpduhen, this strategy would have a lot of dependency's like having a prediction of the solar production and (possibly) a prediction of the home usage, and under the assumption that the user has a dynamic energy contract.

as for the update, the HA update has breaking changes, meaning the new update is not able to communicate with older firmware. please update the firmware on you're sessy, as sessy still runs 1.5.1 :wink:

[PimDoos]

Implemented as a blueprint script in ha-sessy-examples

[jpduhen]

Thank you all, I think this blueprint will help me to build something like this in HA. @MartijnCharged I still think the low-cost-night-charge strategy (charge Sessy to 100% at night when energy is cheap) would be also nice to have to achieve NOM in the morning hours.

[StevenLooman]

Thank you for providing the blueprint @PimDoos!

this request does have a lot of dependency's, like the expected solar power, the expected home usage and possibly even low tariff charging. i think its awesome if you manage to get this working!

I was not asking for a new strategy, just a one-time action. That way the Sessy side stays simpler, but it is up to the user to determine when to run the action.

However, given the blueprint I think I am satisfied for now. Again, thank you.