-
Notifications
You must be signed in to change notification settings - Fork 9
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
JSON's more than 256 bytes are сut off and can't be parsed #2
Comments
This is all correct and done by purpose. We need to ensure that push messages are as short as possible to avoid overloading push messages against the vendors Apple/Google. Another reason is also that we cache recent messages on the server to show them on mobile. One more reason is that we forward messages to our LoRa boards, again a payload limit of 256 bytes. This limit reasonable and will not be increased. |
Am I understand right it only applies to a push notification topics subscribed and not to a widget's topics?
|
The server stored message can be up to 256kB, however only a single last message is stored on the server to recover the dash board. For regular push messages there are the 100 last messages stored which allows to see missed/historical messages. |
Sorry it's still not clear to me what messages the 256 bytes restriction applies. I would need to do my tests again to see if we still have a problem here. |
It was established 256 bytes is too small for the restriction, so it's definitely a problem with this app:
theengs/gateway#193
The text was updated successfully, but these errors were encountered: