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

Feature Request: Read all data from SolarEdge modbus #245

Open
devdems opened this issue Feb 20, 2024 · 2 comments
Open

Feature Request: Read all data from SolarEdge modbus #245

devdems opened this issue Feb 20, 2024 · 2 comments

Comments

@devdems
Copy link

devdems commented Feb 20, 2024

Problem: When you connect a device, in this case, the SmartEVSE meter, to the SolarEdge RS485-2 port you can no longer use TCP Modbus. It is either this or that.

Quote: SolarEdge systems support a single Modbus Leader only – either a single Modbus RTU OR single Modbus TCP

The problem is that this charger only grabs 3,4 values from SolarEdge, so you are stuck by not having access to all that is available in SolarEdge which we use for all sorts of metrics.

The request here would be that the meter when it's connecting to SolarEdge would take all the data that is available and we would then have access to this data by connecting to MQTT where it would be pushed.

@devdems
Copy link
Author

devdems commented Mar 1, 2024

@dingo35 Do you maybe have any pointers how would i start with implementing this change to get more data from the meter to MQTT? I'm willing to do this change by myself. Tnx.

@dingo35
Copy link

dingo35 commented Mar 1, 2024

That is not a simple thing; we are currently rewriting the modbus part; I recommend waiting until 3.5.0 comes out, because once the modbus request mechanism is stable I can judge whether this is possible or perhaps even standard available, when the TCP modbus bridge in our library proves to be stable.

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

2 participants