MQTT message is to long

Question

MQTT message is to long

sp7dpt opened this issue a year ago · 15 comments

I upgrade firmware 2.3.2 to 2.4.3 and mqtt not work. I have error in log MQTT message is to long. How to fix the problem. In version 2.3.2 everything works good.

Answer 1 · 2023-10-30T10:08:18.000Z

Did you only notice the error message or is there also a problem?

Answer 2 · 2023-10-30T10:13:00.000Z

Did you only notice the error message or is there also a problem?

There is a message in the LOG and PixelIT does not execute the command.

Answer 3 · 2023-10-30T11:30:22.000Z

In firmware 2.3.2 in LOG i have MQTT_callback: Incomming JSON (Length: 1405), but in firmware 2.4.3 i have
MQTT_callback: JSON length mismatch! JSON Message to long
MQTT_callback: Incoming JSON (Topic: Dom/PixelIt/setScreen, Length: 1641/1405)

Answer 4 · 2023-10-30T15:37:49.000Z

How do you send the message?
Could you share here the message you send?

Background: In 2.4x, when the input payload and parsed json lenght mismatch, normally the json was to big or is malformed.

Answer 5 · 2023-10-30T16:08:10.000Z

I send message from Home Assistant via MQTT.
For example I tested this message:

{
    "text": {
        "textString": "Pixel it 😀",
        "scrollText": "auto",
        "bigFont": false,
        "centerText": false,
        "scrollTextDelay": 40,
        "hexColor": "#FFFFFF",
        "position": {
            "x": 0,
            "y": 1
        }
    }
}

Answer 6 · 2023-10-30T16:28:18.000Z

I need the raw mqtt message. Maybe you could try MQTT.fx or similar, connect to your broker and subscribe to Dom/PixelIt/setScreen and capture the message.

Answer 7 · 2023-10-30T16:49:19.000Z

I only have MQTT explorer

Answer 8 · 2023-10-30T16:52:53.000Z

In MQTT explorer I also put string and not working.

Answer 9 · 2023-10-30T21:55:16.000Z

Thank u. I try to reproduce it in the next days.

Answer 10 · 2023-11-05T23:52:45.000Z

I get the same error. The error happens because of the check on the json length (length != json.measureLength()), which I don't really understand. Why is this even checked?

This means that every mqtt json must be minified before sending, otherwise this will never match.

After parsing the JSON file, it does not have to be the same length as the received json. The parser will happily ignore spaces etc.

You can verify this by e.g.

{
  "text": {
    "textString": "Test It :D",
    "bigFont": true,
    "scrollText": "auto",
    "scrollTextDelay": 20,
    "centerText": false,
    "position": {
      "x": 8,
      "y": 1
    },
    "color": {
      "r": 255,
      "g": 255,
      "b": 255
    },
    "hexColor": "#FFFFFF"
  }
}

vs.

{"text":{"textString":"Test It :D","bigFont":true,"scrollText":"auto","scrollTextDelay":20,"centerText":false,"position":{"x":8,"y":1},"color":{"r":255,"g":255,"b":255},"hexColor":"#FFFFFF"}}

Answer 11 · 2023-11-06T10:51:52.000Z

@smerschjohann I checked, it actually works after proper formatting of the payload, but it is very awkward to write.

@foorschtbar Will this be fixed in the firmware or should I correct formating of all automations?

Answer 12 · 2023-11-06T11:05:13.000Z

Please test the 2.4.6-beta release and give us feedback

Answer 13 · 2023-11-06T11:22:06.000Z

Please test the 2.4.6-beta release and give us feedback

I tested the firmware 2.4.6-beta and everything works fine

Answer 14 · 2023-11-06T11:26:33.000Z

thank u. I close this issue and hope #323 and #218 will also be fixed with this.

@smerschjohann fell free to reopen you not working for you

Answer 15 · 2023-11-08T21:26:23.000Z

@foorschtbar thanks a lot, it works for me as well :)