Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New SH- Modbus Documentation #36

Open
benni336 opened this issue Mar 22, 2022 · 8 comments
Open

New SH- Modbus Documentation #36

benni336 opened this issue Mar 22, 2022 · 8 comments

Comments

@benni336
Copy link
Contributor

Maybe even a newer version is already out there. I personally think the layout got worse

Communication.Protocol.of.Residential.Hybrid.InverterV1.0.22_20201117.pdf
|

@freman
Copy link

freman commented Mar 29, 2022

I have a rather large sungrow.yaml built based on that pdf

@neiser
Copy link

neiser commented Jun 8, 2022

@freman Would you mind sharing this yaml?

@michbeck100
Copy link
Collaborator

@neiser
Copy link

neiser commented Jun 16, 2022

In the meantime, I came up with my own little project which contains this yaml, which focuses only describing the PDF for one model. IMHO my project has some advantages compared to this project here concerning the readout of registers, but it lacks support for different models (only my own SH10RT currently is supported) and only exports Prometheus metrics. But both shortcomings could be removed with rather little effort if there's interest.

@bohdan-s
Copy link
Owner

I love seeing all the different ideas and use cases!

@neiser im not sure what advantage your script has? LVL2 in the config.yaml will return the same data for your model (and any other model).
My goal is a tool anyone can run out of the box for any Sungrow model with little to no work / technical skill required. As plug-and-play as I can make it, but as many options to allow more advanced people lots of control.

@neiser
Copy link

neiser commented Jun 17, 2022

@bohdan-s I've tried your python script and observed that it polls the inverter with a fixed delay. That is somewhat unfortunate for prometheus metrics scraping, as one could optimize it such that the inverter is only polled via modbus whenever prometheus is requesting the metrics. Also, I don't know if your script also makes heavy use of optimized reading all registers in one bunch (I've written a cache for that). I also couldn't see proper values for array-like registers such as read-only register 6196 (daily pv yields, length 31) on the exposed web interface. And since I was eager to learn some more go, I started my own project :) Also, I find building docker images with google/ko just really cool (as you get really small images).

@michbeck100
Copy link
Collaborator

I see the use case for a plain prometheus exporter, but I like the multiple outputs of Sungather. I personally use the mqtt, console and http output. @neiser it would be great to have another output for prometheus. But it should be easy to implement this, since prometheus just needs another format using the http output.

@michbeck100
Copy link
Collaborator

What about this: #55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants