andig
Aktuell keine Priorität, closing.
@igotsoul wie macht die openWB das denn?
Dann verstehe ich nicht, wie Dich das noch vom Umstieg abhalten kann ;). Aber das ist hier dann OT...
An alternative approach would of course be to use pointer to message consistently throughout. That would make for simpler error return values (`nil` instead of `Message{}`).
I know the difference had caused me quite a bit of confusion. I‘d be happy either way.
@MaximilianJanetschek author of https://evcc.io here. I‘m currently (leisurely) investigating how to integrate more sophisticated energy optimisation into evcc. I’m looking into EOS, but also explore different options like LLMs (https://github.com/evcc-io/evcc/pull/22121)....
@MaximilianJanetschek I couldn't resist and hat to try your model. For this purpose, I had claude rewrite it with a simple REST api wrapper: https://github.com/andig/evopt. Testing the model, results were...
If anyone wants to test the (improved) model independently from EOS, see [github.com/andig/evopt](https://github.com/andig/evopt) for a RESTified service. Thanks @MaximilianJanetschek for providing such a clean and well-structured approach!
See https://pkg.go.dev/strconv#ParseInt
I wouldn't mind if you want to grant it- much appreciated. Do you expect 4 eyes principle or would you give blanket approval?