Simon Thelen

The simplest way to reproduce this is to replace [lpp/usecase.go line 148](https://github.com/enbility/eebus-go/blob/b779bca324be309acf8b053ef7432dbad56c0418/usecases/cs/lpp/usecase.go#L148) with ``` go func() { time.Sleep(1 * time.Second) e.ApproveOrDenyProductionLimit(*msg.RequestHeader.MsgCounter, true, "") }() ``` And then send an LPC...

I've dropped an implementation of the first option in #105

I could reproduce the issue with at least the current versions (github.com/enbility/eebus-go v0.6.1, github.com/enbility/ship-go v0.5.3, github.com/enbility/spine-go v0.6.2). I can try creating a minimal reproducer for the issue

I threw up a branch with a minimal reproducer for the segmentation fault here: https://github.com/ConsolinnoEnergy/eebus-go/tree/test/issue-104-race-condition-reproducer on top of cmd/hems. To reproduce the crash you can run this (slightly) modified hems...

I've updated the PR with support for updating multiple measurements at the same time using the Update() function. For an example as to how to use the Update() function look...

I've updated the PR with fixes for the simple changes, will look over the rest when I have more time

I was waiting for some final qualification tests to ensure that a "spec-compliant" implementation can be achieved for LPC/LPP with this PR. The final test is still outstanding due to...

1. The logging issue should be fixed now 2. I updated the documentation in events.go for LPC/LPP with the new methods as well. 3. I don't think point 3 is...

After a discussion, we'll rewrite this to return the map[ElectricalConnectionPhaseNameType]float64 to be more explicit about whether phases were written to or not.

I've updated this PR to return a map[ElectricalConnectionPhaseNameType]float64. There is one incidental change which may be of interest. The acPowerTotal measurements must now have an acMeasuredPhases electricalConnectionParameterDescriptionData set for the...