Add Alternate/root Path to SenML path ?

[sbernard31]

Currently we don't add alternate path to SenML path.
I don't know if this is the right way to do in LWM2M v1.1 ?

In LWM2M 1.2, it seems that alternate path should be used in payload for SenML JSON, SenML CBOR, SenML-ETCH JSON, or the SenML-ETCH CBOR . See : https://www.openmobilealliance.org/release/LightweightM2M/V1_2_1-20221209-A/HTML-Version/OMA-TS-LightweightM2M_Transport-V1_2_1-20221209-A.html#6-4-1-0-641-Alternate-Path

but in LWM2M 1.1, there is nothing about it :
http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/HTML-Version/OMA-TS-LightweightM2M_Transport-V1_1_1-20190617-A.html#6-4-1-0-641-Alternate-Path

[sbernard31]

I opened an OMA issue about this : OpenMobileAlliance/OMA_LwM2M_for_Developers#564

[sbernard31]

I create a PR about that : #1638.

@cyril2maq, @JaroslawLegierski are you using alternate path ? Will this impact you ?

[sbernard31]

@cyril2maq, @JaroslawLegierski I would like integrate this in master, so I could get feedback from sandbox users and see if it breaks compatibility with some devices.

Is it OK for you ?

[sbernard31]

(If I didn't get any news, I plan to integrate it early next week)

[slaft]

I've checked and we don't have any devices that use an alternate path. So it shouldn't impact us (and we won't be able to give you some feedback on this topic unfortunately).

[sbernard31]

(and we won't be able to give you some feedback on this topic unfortunately).

no problem

I've checked and we don't have any devices that use an alternate path

This is exactly the kind of answer I wanted. So we are sure that you will not face any issue because of new behavior 👍

Thx 🙏

[sbernard31]

#1638 is now integrated in master. (will be available in 2.0.0-M17)