Closed macray76 closed 1 year ago
Please confirm the fix and I will resolve
Not OP but this fixes it for me
Please confirm the fix and I will resolve
Will check this evening as for me the issue only presented itself once the initial target SoC was set by Predbat.
Looks like this issue was fixed. Thank you!
Errors being generated once target SoC has been set (e.g. first charge window 23:30, initial target SoC set at 23:04, errors start appearing from 23:09 onwards). Predbat stops the current cycle after generating this error...
Line 2080 originally has:
self.current_charge_limit = inverter.current_charge_limit
I've temporarily fixed it by converting it to a float:
self.current_charge_limit = float(inverter.current_charge_limit)
Also possibly linked to this (maybe an error somewhere else or due to my "float" change) a warning on the main appdaemon.log:
The above can't seem to read the inverter's current target SoC so it constantly sets it to the expected 29% target every 5 minutes even though it is already set to 29%.