search

britkat1980 / giv_tcp

TCP connection (from inverter) and MQTT implementation
71 stars 32 forks source link

Cant force charge - Gen 2 Hy5 #115

Closed swinbsp closed 7 months ago

swinbsp commented 9 months ago

I am trying to force a charge on my Gen2 Hy5 to be coincidental with charging my car as I am on Intelligent Octopus.

I can't see a "forceCharge" function so am just trying to dynamically use the charge schedular, mirroring what the app does. I set the time to start "now" and end in 60 or 120 minutes. The call returns a status of 200, implying that it has worked but no setting have changed.

I did manage to do this years ago on early versions when I was on Agile so changed the charge times regularly. I didnt need to do this for the 2 years I was on Octopus Go but do again now I am on Intelligent.

http://192.168.1.13:6346/setChargeSlot1 {"start":"1309","finish":"1509","chargeToPercent":"100"}

I run this via NodeRed. All the authorisation etc is ok as other calls work sucessfuly

Any ideas?

swinbsp commented 9 months ago

I remain unable to use the SetCharge1 function, but have sucessfully used the "forceCharge" function that I discovered in the code

I am now sucessfully monitoring load and charging the battery for 30 minute slots when it is clear that the car is ( or has been ) charging. I then reverting to the standard overnight schedule when car charging is completed.

I wasnt sure how Intellignet octopus billing works so was a little weary of doing this. It could have been very expensive! I couldnt see costs until the bill came so acted on faith the system would work as descibed. I have now had a bill and can see daytime cheap slots are indeed billed at the times the car is charging via Octopus automations. I note this is the case only when the car has has at least some charge added ( the whole 30 mins is cheap rate if the car has done any automated charge within the slot, even if only for a few mins ). Hence checking load to trigger battery charging

swinbsp commented 9 months ago

sussed the issue with setChargeSlot1. The times need to be in the "hh:mm" format, not "hhmm" as per the help text