Connection and polling interval best practices ? about solaredge_modbus

[nmakel]

What is the best practice for fetching the data? Leave the connection open between pollings or close it each time?

Unless there are other devices or applications that need to poll the inverter you should be keeping the connection open. Running example.py in a loop, or via cron, probably isn't what you want to do.

And how often can we pool the data? Today I do it every 20 seconds... I don't know if I'm abusing or if it's slow!

I'm unsure of the refresh rate of the data, which would be the lower limit of how often it is useful to poll the data. You're unlikely to break things, though. Polling these registers causes no measurable CPU load.

[jburdy]

Yes today I have a variant of your example running in a systemd timer. I'm thinking of putting it into service. So I'm going to try to leave the connection open, but I'm not a fan of thinking that it's blocking access to other connection. I hope it doesn't block anything on the SolarEdge side either. Although my access should be exclusive (after I relay to MQTT for all my other consumers. I took the liberty of making a push request, it might be interesting for others).

[Jusufs]

Hi, Thanks for the job, it's been running in my house for a few months now and it's allowed me to automate my W consumers very well! Mainly from Home-Assistant.

What is the best practice for fetching the data? Leave the connection open between pollings or close it each time?

And how often can we pool the data? Today I do it every 20 seconds... I don't know if I'm abusing or if it's slow!

Thanks for your advice,

I can poll via python script each 5 seconds. My python poll part sends data to Raspi Openhab2, Influx, Grafana.