-
Notifications
You must be signed in to change notification settings - Fork 374
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
Client registration update timeout is broken for lifetime > 93.0s #613
Comments
Not directly linked but in Leshan we are using We also think that lifetime is not the best way to configure a kind of communication period. For more details, see :
Maybe this thoughts could interest you. |
@sbernard31 thanks for providing more context. The time between registration updates is defined via the lifetime resource in the LWM2M Server IPSO object /1/x/1. There is no RangeEnumeration specified there, so I would guess the whole positive Integer range (up to 64bit signed) in seconds is valid here up to 9,223,372,036,854,775,807.
|
I would suggest making the check Edited: I shouldn't respond before coffee. I had the wrong result after the limit. |
For a client lifetime value less than 93s a registration update is sent to the server every lifetime/2 as expected. Above a value of 93.0, a registration update is send every
timeout=lifetime-93.0
. The number 93.0 is results from a definitionCOAP_MAX_TRANSMIT_WAIT
as a float value.This can be reproduced by starting the client with
lwm2mclient -t 100
. After initial registration an update is sent every 7s.The following section seems to cause the problem:
https://github.com/eclipse/wakaama/blob/a1281ab4abb2199200b406545f7a169b23da143c/core/registration.c#L2071-L2081
The text was updated successfully, but these errors were encountered: