Any way to suppress tele/xxxx_06C6B8/RESULT MQTT messages

[UBWH]

I have a SCRIPT project that uses the Smart Meter feature to send/receive MODBUS messages. Works well.

Decided to port the project to BERRY.

Using tasmota.cmd("modbussend {"deviceAddress" ...") to send the MODBUS messages. Works well.
The responses come back in ModbusReceived messages as below.

11:45:28.551 MQT: tele/solar_06C6B8/RESULT = {"ModbusReceived":{"DeviceAddress":1,"FunctionCode":3,"StartAddress":36883,"Length":7,"Count":1,"Values":[2587]}}
11:45:29.552 MQT: tele/solar_06C6B8/RESULT = {"ModbusReceived":{"DeviceAddress":1,"FunctionCode":2,"StartAddress":8192,"Length":6,"Count":1,"Values":[41216]}}
11:45:30.552 MQT: tele/solar_06C6B8/RESULT = {"ModbusReceived":{"DeviceAddress":1,"FunctionCode":4,"StartAddress":13082,"Length":7,"Count":1,"Values":[1335]}}
11:45:31.557 MQT: tele/solar_06C6B8/RESULT = {"ModbusReceived":{"DeviceAddress":1,"FunctionCode":4,"StartAddress":13083,"Length":7,"Count":1,"Values":[-21]}}
11:45:32.510 MQT: tele/solar_06C6B8/RESULT = {"ModbusReceived":{"DeviceAddress":1,"FunctionCode":4,"StartAddress":12800,"Length":11,"Count":3,"Values":[0,7,1]}}
11:45:33.510 MQT: tele/solar_06C6B8/RESULT = {"ModbusReceived":{"DeviceAddress":1,"FunctionCode":4,"StartAddress":12560,"Length":9,"Count":2,"Values":[2937

As I am issuing, and receiving, MODBUS messages every second, I am getting MQTT messages emitted every second.

I know these MQTT messages are not spam - that is how Tasmota works.

But - it is a major problem for me as these MQTT messages will be going over a low-bandwidth link to an external MQTT server that does not need them.

So my question is: How can I use BERRY to issue/receive MODBUS messages without so many MQTT messages?

(The SCRIPT method does not have this problem).

[sfromis]

No such option exist for the RESULT messages in general.

For serial bridge (not modbus), SetOption147 exists to avoid SerialReceived messages being published via MQTT, but still available for local processing. It could make sense to extend this to where the Modbus bridge is calling MqttPublishPrefixTopicRulesProcess_P in xdrv_63_modbus_bridge.ino, in a similar way as what is being done in xdrv_08_serial_bridge.ino

[sfromis]

Suppressing everything should not be a goal, they do no harm. The point of avoiding the ModbusReceived messages being published is that these are intended as the way of processing the Modbus data, and when that processing is already done locally, that makes sense as a "takeover", in the same way as you can process a Switch or Button input with or without getting MQTT messages for these.

ModbusSend should be much lower in volume (indeed you always got them), and the command processing messages are inherent to how Tasmota commands are processed. Arguably, the message should've been more complete than just the "Done", but that's a separate consideration.

SetOption158 should already be part of the release code, thus you should not need to implement anything yourself.

[UBWH]

Appreciate all that, but as I said in the original post
But - it is a major problem for me as these MQTT messages will be going over a low-bandwidth link to an external MQTT server ..

[UBWH]

...See there was a new release 3 days ago (V14.4.0) with the new setoption158

[sfromis]

As I already told you

No such option exist for the RESULT messages in general.

This is different from reporting of incoming Modbus messages, as the Tasmota command processing always elicits a response.

[FulvioSpelta]

I confirm that the setoption158 (pls take note that there is a fix in the development branch #20733 ) suppress the "modbusreceived" messages. The "modbussend" messages follow a completely different rules and currently are not suppressed "by design".

I'll think a bit about this that really i don't know is this part of the tasmota code.