- LWM2M batch uploading data
Re: LWM2M batch uploading data
To be honest, it sort of seems as if the implementation assumes it has a perpetually open socket connection to cloud at all times. Perhaps this is an exaggeration, but I'd kind of like to know how (if?) the implementation handles downed interfaces and broken pipes...
You are correct. The missing piece is LwM2M queue mode support. This mode is registered during the initial client / server connection. It means there is a mutual agreement that the client will (in general) not be available for instantaneous queries, but prior to the agreed upon connection "lifetime", the client will re-establish communication with the server and answer requests. There is a set period of time where the client will remain connected afterward and then it can go back offline.
Over the last few months, queue mode in Zephyr has gotten more attention (mainly due to expanding modem support). Unfortunately, due to my current work load, I haven't had the time to implement and test it.
Here is the Zephyr issue which tracks the addition of LwM2M queue mode support:
Embedded Software Engineer
We have a use-case which I deem to be pretty normal: uplinks are really expensive and should be kept to a minimum (in fact, we want the radio completely powered off 99.99% of the time). But we have N sensors which we want to observe from the cloud, at different intervals. Looking briefly through the specification, one gets the impression that OBSERVE at some interval implies that the device uploads data at this observation interval.
What we'd like to do is to sample the data at the observation interval and batch upload it at some different, longer, interval. It's not clear to me if the specification allows this - and if it does, does the Zephyr implementation allow it?
Grateful for clarifications.
Join firstname.lastname@example.org to automatically receive all group messages.