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
When trying to create a downlink of 70 characters I got the following error:
"error":"payload exceeds max payload size"
Well described here too: https://github.com/brocaar/chirpstack-network-server/issues/391
The (subsequent) change from "Maximum allowed data-rate" to 5 was not a solution.
What did you expect?
Changing max DR in the service profile should also have an effect on registered devices
(SF7)
To solve my problem, I had to delete the device and register it again with a newly created service profile with DR5
Steps to reproduce this issue
Steps:
Create a service-profile with max DR 0
register a device with this service profile
Try a downlink longer than 51 characters
(you get the "payload exceeds max payload size" error)
change the max DR in service-Profil to 5
Try a downlink longer than 51 characters
(you get the "payload exceeds max payload size" error)
Your Environment
Component
Version
Application Server
3.17.8
Network Server
3.16.5
Gateway Bridge
3.14.5
The text was updated successfully, but these errors were encountered:
Test Chirpstack V4 with Device DR5 SF7 Region EU868 (Min DR: 0, max DR: 5)
level:"ERROR"
code:"DOWNLINK_PAYLOAD_SIZE"
description:"Device queue-item discarded because it exceeds the max. payload size"
max_payload_size:"51"
item_size:"71"
Is there somewhere else to specify the max DR (like in the service profile in V3)?
What happened?
When trying to create a downlink of 70 characters I got the following error:
"error":"payload exceeds max payload size"
Well described here too:
https://github.com/brocaar/chirpstack-network-server/issues/391
The (subsequent) change from "Maximum allowed data-rate" to 5 was not a solution.
What did you expect?
Changing max DR in the service profile should also have an effect on registered devices
(SF7)
To solve my problem, I had to delete the device and register it again with a newly created service profile with DR5
Steps to reproduce this issue
Steps:
Your Environment
The text was updated successfully, but these errors were encountered: