andig
> all these cases [no new connection will be accepted](https://github.com/lorenzodonini/ocpp-go/blob/master/ws/websocket.go#L542), until the old one was properly cleaned up. It is theoretically possible that your scheduler takes away CPU during execution...
> So in theory CPU scheduler can cause some confusion, but again I do not believe this to be realistic. Unless the callback is run in a go routine I...
So what would "zero feed in" controller mean?
See https://github.com/evcc-io/evcc/discussions/19715#discussioncomment-13421941 for related apis. > When the charger can consume more or if you for instance plug in your EV, the "dimming" of the PV can be reduced or...
How do you know a charger „wants“ to enable in PV mode? The whole definitionnof PV mode is that it enables on surplus. Which you don‘t have in this case.
> based on a non-dimmed PV value ...and that would come from...?
> I guess Dimming refers to kWp, not to actual potential production.
I repeat: we need a mechanism to allow start charging or scaling charging demand under zero feed-in regime. We do have this experimentally for battery boost but it's only one-shot...
Wondering what the device API for zero feed-in should be. I guess we would need something like: ```go type FeedinController interface { SetMaxFeedinLimit(float64) error } type FeedinLimiter interface { GetMaxFeedinLimit()...
We also need to align on the feed-in tariff. Do we treat positive values as "I make money by feeding into the grid"?