Hi Konstantin,
same as @DanielMalmgren I’m using the Solar Forecast binding. I found SolCast more accurate, even though it only has 10 API calls for free / day. Strangely it seems that every refresh is using two calls for me so its basically 5 updates per day, but I use script to desdable the binding, so that I don’t waste them (kind of brute force). See the linked thread for detail.
It hase very convenient “Remaining Today” parameter which I use for calculations both early morning and during the time of peak price.
As said above my key lessons learned are:
- Solax seems to honor “Forced Charge” window even when Night_Charging is disabled, so to prevent using grid in that window I also set it to 0:00-0:00 when disabling Night_Charging
- Easiest way to “force export” during peak hours in the morning when battery is still empty is to switch to “FeedIn mode” (1). Don’t forget to set it back (timer and/or cron)
- Setting export to 0 prevents exports during time with negative price (can adjust provider margin)
- IMPORTANT: Export in modbus is in 10s of Watts, so for setting 14kW I need to set 1400
- IMPORTANT: Dis/charging date/time in Modbus are 8bit (upper and lower from 16bits) for reading, but Modbus binding can’t write 8bits so you can only write byte. The guys in Solax planted a big trap as the Hour/Minute are reversed when Writing, so sometimes it kind of works (like 1:01 = 1:01), sometime is screws setting, but works (like 2:01 <>1.02 but is valid time) and sometimes it just forces error 4 (Modbus refused) (eg. 3:30 <> 30:03 but it is also invalid value).