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
Describe the issue
After enabling remoteConfiguration option I see a lot of the following messages in the gateway logs:
thingsboard-gateway | 2023-12-10 08:15:53 - |DEBUG| - [tb_device_mqtt.py] - tb_device_mqtt - _on_disconnect - 205 - Disconnected client: <paho.mqtt.client.Client object at 0x7f8255c045d0>, user data: None, result code: 7
while in a server log
2023-12-10 08:16:23,228 [nioEventLoopGroup-4-12] ERROR o.t.s.t.mqtt.MqttTransportHandler - [e58f2d14-914c-47c7-92d8-180e40d38fd1] Message decoding failed: too large message: 148657 bytes
Then I set NETTY_MAX_PAYLOAD_SIZE server option to 1000000 and restart, but no success result
Connector name (If you need help with some connector/converter):
There is one connector of MQTT type with the following config. Gateway payload size is: "maxPayloadSizeBytes": 1024000, mqtt.json
Versions (please complete the following information):
TB server: 3.6.0
Gateway in Docker: 3.4.3.1
The text was updated successfully, but these errors were encountered:
Disconnect event - it is OK in case of updating general configuration on the dashboard, but 2023-12-10 08:16:23,228 [nioEventLoopGroup-4-12] ERROR o.t.s.t.mqtt.MqttTransportHandler - [e58f2d14-914c-47c7-92d8-180e40d38fd1] Message decoding failed: too large message: 148657 bytes - is an issue and we will investigate this point.
Describe the issue
After enabling
remoteConfiguration
option I see a lot of the following messages in the gateway logs:while in a server log
Then I set
NETTY_MAX_PAYLOAD_SIZE
server option to1000000
and restart, but no success resultConnector name (If you need help with some connector/converter):
There is one connector of MQTT type with the following config. Gateway payload size is:
"maxPayloadSizeBytes": 1024000,
mqtt.json
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: