You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
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.
The text was updated successfully, but these errors were encountered: