[Update] - Configuration Clarity

README.md

@@ -38,11 +38,13 @@ I recommend using one of the pairs from the Ethernet cable for RS485 wiring. e.g
 
 ## Configuration
 **Still under review - see** https://github.com/alienatedsec/solis-ha-modbus-cloud/discussions/7 
-- The `TCP Server` on my [diagram](https://github.com/alienatedsec/solis-ha-modbus-cloud#diagram) and [presented here as 187 GW](https://github.com/alienatedsec/solis-ha-modbus-cloud#final-result) acts as a gateway for other devices (datalogger and HA integration), and it has a baud rate of 9600. The `Modbus gateway type` is `Auto query storage type`, and I enabled `multi-host`, so the datalogger queries will not create conflicts - at least that is my reasoning.
-
-- The `TCP Client` [presented here as 171 DLG](https://github.com/alienatedsec/solis-ha-modbus-cloud#final-result) is pointing at the IP and the port of the `TCP Server` with the same Serial config - screenshots below
-
-- Both `TCP Server` and `TCP Client` have the `Modbus_TCP Protocol` as the `Transfer Protocol` - see the screenshot below.
+- The `TCP Server` on my [diagram](https://github.com/alienatedsec/solis-ha-modbus-cloud#diagram) and [presented here as 187 GW](https://github.com/alienatedsec/solis-ha-modbus-cloud#final-result) acts as a gateway for other network devices (e.g., the datalogger wired to `TCP Client` and for any compatible HA integration).
+- The Serial baud rate is 9600 - default on the inverter
+- The `TCP Server` - `Modbus gateway type` is set to `Auto query storage type`, and I enabled `multi-host`, so the datalogger queries will not create conflicts - at least that is my reasoning based on Waveshare documentation.
+- The `TCP Client` - `Modbus gateway type` is set to `Simple Modbus TCP to RTU`, and `multi-host` is not enabled.
+- You should use the IP address and the port number of the `TCP Server` when configuring any `Modbus TCP` compatible integration - e.g., like in the [Home Assistant Solax Modbus](https://github.com/wills106/homeassistant-solax-modbus#installation) installation notes.
+- Therefore, the `TCP Client` [presented here as 171 DLG](https://github.com/alienatedsec/solis-ha-modbus-cloud#final-result) has its own IP address (irrevelevant), but within its `Dest IP/Domain` and `Dest. Port` config fields, it has to use the IP and the port of the `TCP Server`, and it needs the same Serial config - screenshots below
+- Both `TCP Server` and `TCP Client` have the `Modbus_TCP Protocol` set as the `Transfer Protocol` - Waveshare is converting `Modbus RTU` messages to `Modbus TCP` and vice-versa - screenshots below.
 
 **TCP Server Config**