britkat1980 / giv_tcp

TCP connection (from inverter) and MQTT implementation
78 stars 37 forks source link

Force Charge service #142

Open sjs-1956 opened 10 months ago

sjs-1956 commented 10 months ago

At the moment the sections maximum is 180 mins. Can this be increased to 360 as my batteries take nearly 6 hours to charge if I want to go to 100%?

sjs-1956 commented 9 months ago

Any thoughts/comments on this request?

anthonyangel commented 8 months ago

The force charge service has an option for Running, which I assumed would trigger an indefinite force charge, but it appears to do nothing.

image

gcoan commented 8 months ago

The force charge service has an option for Running, which I assumed would trigger an indefinite force charge, but it appears to do nothing.

image

I set the entity to Running and it works fine for me, but I set charge start time to 00:00:00 and charge end time to 23:59:00 beforehand

CaptSB commented 8 months ago

Indeed, you need to be within the period of Time Slot 1 for it to work by just setting it to Running.

Sent from Gmail Mobile

On Fri, 2 Feb 2024 at 23:38, Geoffrey Coan @.***> wrote:

The force charge service has an option for Running, which I assumed would trigger an indefinite force charge, but it appears to do nothing.

image.png (view on web) https://github.com/britkat1980/giv_tcp/assets/2271981/881338c8-7ec0-4eb0-b92d-d01e44857920

I set the entity to Running and it works fine for me, but I set charge start time to 00:00:00 and charge end time to 23:59:00 beforehand

— Reply to this email directly, view it on GitHub https://github.com/britkat1980/giv_tcp/issues/142#issuecomment-1924907160, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64N7OSS2DULMRDI2C6BFNTYRV2GNAVCNFSM6AAAAAA7PT2U7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUHEYDOMJWGA . You are receiving this because you are subscribed to this thread.Message ID: @.***>