| Re: [wakaama-dev] Limit number of re-registrations: lwm2m_step() failed: 0xA3 |
Hi David, Thanks for this, It might then possibly be also a synchronization issue as I’m not sure how reliable is the real time clock of the platform. Thanks and Kind Regards, Riccardo. From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Navarro, David Hi, There is an issue with the client registration update: when the lifetime is too short, the client updates its registration at the same time the lifetime expires. If there is any delay in the communication, the Server already dropped the registration when the update message reachs it. The fix is on my TODO list. Regards, David Navarro From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Riccardo Pozza Dear all, I’ve got a setup that connects a few (non-linux) clients to a Leshan LWM2M server via WiFi. The Wakaama LWM2M client stay registered pretty much all the time (lifetime is 30 seconds to keep alive NAT), however occasionally, say on average once every hour, the client debug message outputs “lwm2m_step() failed: 0xA3“ and a re-registration take place. Is it normal to have that much re-registrations? Do you know if there is a way to limit this or avoid completely? This because the re-registration would occasionally create a hole of few seconds (which is fine but it’s not neat) in my data collection app on the cloud server requesting values from 6 sensors every second. Thanks for any help/advice, Kind Regards, Riccardo. --------------------------------------------------------------------- This e-mail and any attachments may contain confidential material for |