-
Notifications
You must be signed in to change notification settings - Fork 82
make TX_PAYLOAD_BUFFER_SIZE overridable #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @ravelab, I'm ok with merging the changes you proposed in #11. One note, before I do, if you happen to know the size of your message before hand you can pass it into Would this cover your use case? |
Hi, @sandeepmistry It does cover my use case, I missed that beginMessage(...) option. It's up to you if you want to make TX_PAYLOAD_BUFFER_SIZE overridable. Thanks. |
Hi @ravelab, Great! I'm going to close your pull request for now, if someone requests the feature in the future we can re-open the your pull request and merge. |
Hi @sandeepmistry and @ravelab, Time has come. :) Could you re-open this issue, merge the PR #11 and release it as next version, please? I hit one issue when uploading JSON document of ArduinoJson.
See also: How to use ArduinoJson with ArduinoMqttClient? Thank you. |
It would be much appreciated if you could reopen this. The payload for auto discovery in Home Assistant is often > 256! |
please reopen this - I had the issue that (depending on the floating point conversion) sporadic the MQTT messages are invalid. This is really hard to find if it occurs roughly once per day... Thank you. |
Fixed by #44. |
Hi, is it possible to make TX_PAYLOAD_BUFFER_SIZE overridable, as an instance variable, or compile build option? I was surprised to find that it is only 256 bytes. Thanks
The text was updated successfully, but these errors were encountered: