Command ModbusTCPConnect - for which use case

[wjohn007]

I'm currently working on Modbus topics.
I cannot recognize a use case for the ModbusTCPConnect command.
It connects to a Modbus TCP slave as as Modbus-TCP-Master.

But why?

How do you trigger a Modbus request in this scenario ?

The command ModBusSend always uses the serial port (ModBr RX/TX).

[wjohn007]

some comments from @jeroenst about this topic

ModbusTCPConnect ,<ip_address> = connect to a remote Modbus TCP server on remote tcp port˙ and ip_address
I believe it was a request from some user who also tested it. I never used it myself though.
...
Tasmota is always master on the serial line modbus and a modbus slave on the network in the current design.
So it can connect to an external tcp device and waits for modbus data from the tcp master. I could imagine this like a serial to tcp converter connected to a modbus master device.

In my opinion, the "ModbusTCPConnect" command appears to be a proprietary solution, since a TCP client in the Modbus world is always a Modbus-master.

[wjohn007]

Additionally, the "ModbusSerialTimeout" command is not part of the documentation
https://tasmota.github.io/docs/Modbus-Bridge/#commands