I have some devices which collect some data. A connected scale for example. I am not really happy that all of these data are collect in some “Cloud” application of some random provider. I even don’t know if this provider still exists in 10 years. So, my idea: Why can’t I use a local server (Rpi or something) and collect all my data there? All devices are connected to this one Gateway. 6LoWPAN and RPL is perfect for it. Just add BLE and you can connect all devices. So, I just wanted to know if there are some kinds of standards to make this as flexible as possible. Specification how the data should look like and what transport layer should be used? QUIC? etc.
I am a proponent of LwM2M [1,2]. It runs on CoAP, usually over UDP. Checkout the integrated object registry [3]. There is an open PR to integrate a package for the Wakaama client [4], which should be merged before release 2020.01.
Ken
[1] [2] [3] [4]
You are now alone. I too want that.
I recommend you check out the IETF (IRTF actually), T2TRF, and look at the SENML specifications. It includes specifications for sending data, including dealing with questions about what units they are in.
There are also various industry-specific consortia, but they tend to be closed and often terribly stupid.
Hi,
for finding your (CoAP) resources in the first place you can install a CoRE-RD [1] server on your Raspberry Pi (e.g. the one provided with aiocoap [2]). With the cord module in RIOT your sensor nodes can then register to their resources to that server.
I recently show-cased that in a demo (Hauke was presenting it on the summit).
Best regards, Martine
[1] https://tools.ietf.org/html/draft-ietf-core-resource-directory-23 [2] https://aiocoap.readthedocs.io/en/latest/