Closed damienheiser closed 4 years ago
Thank you for reporting this. I believe I have now fixed it. It's weird that the documentation doesn't say 0 represents the user battery type. I thought 5 represented that type.
Thank you very much for an incredible project, I'd love to buy you a beer or EANAB (equally appealing non-alcoholic beverage)
That means a lot. Thanks. I'll consider setting up a way to receive donations. I'm not old enough to drink yet, so an EANAB sounds good. Could go for some lemonade right about now.
To update run a git pull and then run program/download_solarthing.sh
.
If this fixes your issue, feel free to close this issue.
I'm closing this for now. If you come across this error again, feel free to re-open this.
Thanks for using SolarThing!
So apparently this isn't just a thing for newer rover models. I tried manually changing the battery type on my rover itself, and then the battery type was 0. So the "user" battery type actually corresponds to 0 and 5. 0 is basically unlocked, and 5 is locked.
There's some more info about that here: https://support.renogy.com/en/support/discussions/topics/35000016803
I am using a Renogy Rover 60A Li. Solarthing was working fantastic while I had the Rover setup with the Battery type as SLA.
I changed the battery type to USR yesterday, and found that Solarthing started to fail at that point. The log also reveals some sort of Immutable Battery Type.
This might be due to the Rover 60A Li being a little newer and having another enumeration type for the battery within the specification, since it also handles Lithium Ion, which wasn't on the original 20A and 40A.
I'm going to to my best to dig through the code to see if I can provide a pull request, however my Java skills aren't really there.
Thank you very much for an incredible project, I'd love to buy you a beer or EANAB (equally appealing non-alcoholic beverage)
config/base.json:
Log: