MQTT vs LwM2M

Well, you probably understand the protocol of MQTT and basically it's similar to consuming an API. I always like to compare it with WebSockets where you subscribe to a certain channel or topic to listen to data.

For Laravel, you can find different packages and simplify this a lot. Here is an example package: https://github.com/salmanzafar949/MQTT-Laravel

Hi, thank you for your reply. Due to DFOTA capabilities, we are more inclined to use LwM2M. How would you suggest getting started with it please? Possibly using Laravel as well.

@lukegalea16 MQTT's reliance on TCP/IP is too heavy and doesn't really work over NB-IoT. For NB-IoT, FOTA, security, and a whole bunch of other reasons LwM2M using CoAP are preferable.

Keep in mind, although a standard not all LwM2M offerings are the same. You should look at IoTerop's SDK. It is tested, documented, and supported by the guys who have done a lot to define LwM2M at the Open Mobile Alliance. Some real heavy-hitters like Itron and others use the SDK. Get the free version here https://info.ioterop.com/eval

Hi! Thank you a lot for your reply. Could you kindly elaborate more re IoTerop's SDK? What is it exactly? i.e. for the server or embedded side?

Moreover I'm having trouble finding support for hosting/building a LwM2M server. Many seem to use Leshan. However I'm trying to think of the bigger picture where I need my NB device to fetch data from my APIs written in my Laravel project. Any help would be greatly appreciated.

Br Luke

What about using CoAP to make POST/GET requests at any point in time? I'm getting the feeling that with LwM2M, the server makes requests to the device to get the data?