Hi,
When trying out the programme for the first time using a Fronius inverter+smart meter I received the following error message:
"Modbus Error: [Connection] Modbus TcpClient(192.168....): Connection unexpectedly closed 0.001 seconds into read of 8 bytes without response from slave before it closed connection"

In the first moment it seems to connect successfully to both the Fronius and the Lambda but after a few seconds the mentioned error message appears.

The programme runs on a RaspberryPi. First I tested it using a Modbus simulator programme instead of the Lambda heatpump - this worked fine.

Did you ever experience such behaviour? The question is whether the error is caused by the Raspberry or the Lambda HP. It sounds a bit like a timeout at Lambda but I don't have access to any deep settings there.
Which E-Meter communication type are you using in the Lambda settings? My setting is "Modbus EM300" what I cannot change myself. (Indeed there is no EM300 smart meter installed, I have the Fronius sm.). If you know: are there any Modbus timeout settings?

Hi @hendrikmuhs, thanks for sharing your script.
You are covering exactly my future setup. I currently have a SolarEdge SE8K RWS with SolarEdge Electricity Meter installed and I am in the process of ordering a Lambda EU08L. What I'm not clear yet if I need to include the Lambda Smart Meter as well into my configuration. Does the script in your setup require the presence of the Lambda smart meeting? Any insight would be highly welcome.

Thanks!

Hi @hendrikmuhs,
thanks for sharing your script.
Are you open for a PR to also support Fronius Inverter as "source"?
From the code base it looks like that this is intended.
I have a Fronius inverter and smart meter and could add a new source-type + logic for this.