SilverArt It’s not so much in doing the check that this happens. It’s in the disabling of the schedule.
We need to disable the schedule if your conditions haven’t been met, otherwise, next day it could kick in inadvertently if you decide to deactivate your specific export schedule in WW. This was a scenario @JMA encountered which we had to fix.
admin Rotten lot us users
.. WW's getting a rest today, nothing scheduled now until midnight.
Thanks for all of your help.
Not sure if part of this or something new....:
This morning's discharge session didn't see an ECO back to true command until I spotted it and sent one at 12:27
2024-01-16 12:27:59 You Enable Eco Mode Written Successfully false true true Portal - Inverter Settings Tab
2024-01-16 11:58:27 You Battery Reserve % Limit Written Successfully 50 4 4 API - Inverter Presets
2024-01-16 11:58:27 You Enable DC Discharge Written Successfully true false false API - Inverter Presets
2024-01-16 11:58:26 You DC Discharge 1 End Time Written Successfully 12:00 00:01 00:01 API - Inverter Presets
2024-01-16 11:58:26 You DC Discharge 1 Start Time Written Successfully 10:30 00:00 00:00 API - Inverter Presets
2024-01-16 10:25:50 You Battery Reserve % Limit Written Successfully 4 50 50 API - Inverter Presets
2024-01-16 10:25:50 You Enable DC Discharge Written Successfully false true true API - Inverter Presets
2024-01-16 10:25:49 You DC Discharge 1 Start Time Written Successfully 00:00 10:30 10:30 API - Inverter Presets
2024-01-16 10:25:49 You DC Discharge 1 End Time Written Successfully 00:01 12:00 12:00 API - Inverter Presets
2024-01-16 10:25:48 You Enable Eco Mode Written Successfully true false false API - Inverter Presets
admin Thank you, it was OK yesterday so if you've not changed anything in that area it's possibly an oddity that happens infrequently.
SilverArt Yeah, seems strange though. We have added more logging, specifically the response we get from Giv API in that Eco-reset scenario.
It might be that the HTTP response code was OK, but the raw response body wasn't valid/formatted correctly - returning error HTML instead of JSON for instance.
admin I have got a very sneaky suspicion that it might be 'busy time' related but I'll leave times as is for the moment.
Hi , for my 9000TL-XH(UP) , things seem to work fine now and tested the integration schedules. Have a problem with discharging though. It did not stop discharging at the stop discharging level (set to 30% in the Wonderwatt schedule ) and depleted my battery till I had to stop it manually at 5% or so. Any known issue ? ( I noted on the Growatt server that I have both an off grid and on-grid stop discharging SOC setting - not visible in the app). The on-grid was somehow set to zero ; any relation to that ?)-thanks
Jorrit OK, so the the issue with the TLX inverter looks like it does not seem to have percentage SOC targets or stop percentage available against the timeslots, like it has on some of the SPH hybrid inverters.
So best option might be to just cut your end time for the window short, based on a start/trigger SOC as specified in WW and the discharge rate of your inverter.
What setting do you configure and where in the Growatt portal is that? Can you put a screengrab in here for context please?
That the server page showing the two discharge settings. These are indeed no connected to timeslot. Believe these to always apply. So the timeslot would only set the mode (load, grid, battery) .
The app shows that as follows :
So in the app the setting shows UNDER time of use setting , but you can not set it in combination with timeslot , it would apply to all timeslots .. (or so I believe)
