I had to start a new Topic as this system won’t allow multiple replies. I’ve tagged you so hope you see this @weorme62
I still actually use the SunSynk cloud API although I’m not a massive fan. For me it has been a little problematic, but others have made it work I think. I have also found what some describe as a firmware bug where you cannot turn off the “use timer” flag. I got SunSynk to update my Inverter Firmware to version 3.3.8.7. which has helped a little but it seems the Inverter doesn’t want to wait with no timer.
My work around has proved to be quite complex, although it’s now working. I found I can update the Inverter with the Timer set to ON by using the time slots. I fixed in my code times slots one, two and six. One and Six cover my standard off peak and two gives me my stop time for then morning (learnt the hard way). I am now at my limit of replies so will update this one if needed.
By the way, William, did you have relatives in Welwyn Garden City? I went to school with somebody sharing your surname.
Hi this is of high interest to me as currently I’m having issues with my system not being efficient. Since octopus intelligent go can often charge outside of the typical 23:30-05:30 time slot I often have issue where the car will charge from the battery which I really don’t want that.
Would love the ability to turn off Sunsynk battery power to grid when the EV charging at odd times
yes this can be done and I am happy to help show you how. Before we chat about this… I am having some issues I need to solve. The Octopus API does not correlate with the smart charging of IOG. Previously I was getting 3 second latency which I thought to be fine but yesterday it went up to 15 minutes and this morning the car carried on charging for an hour and 50 minutes which the API told HA I was at peak rate. This discharged some of my battery.
I’ve raised a support request with Octopus but I might have to add a CT clamp sensor (Shelly or the such) to my charger. The API doesn’t share the actual commands to the charger which is a shame. I thought I’d found a bug in my code but it’s an API issue for sure.
My sensors have come back on but they are a bit all over the place. I’ve stuck a Shelly CT on the power to my charger and i’ll combine the sensors probably… Shelly latency is less than a second but i need to deal with the test charge logic. Each time the car is plugged in IOG does a short test change to confirm it has control.
On the bright side it will be more robust. thanks for the info!
I’ve integrated the Shelly as an override which is working super fast. It helps a little avoid my home batteries charging the car. I set the pause on start to a minute which is too long for the test control IOG use to be sure they have control of the charger. 20sec is probably enough but I’ll measure it and see. I’m still using the Octopus API as it solve issues such as bump charging. I don’t want to charge my home batteries on peak when I bump change although that’s not often.
