warmek

I would like to implement a write attribute at client side and I looked at [#484](https://github.com/eclipse/leshan/pull/484), but I'm not sure where to start, as from what saw part of the...

@sbernard31 Could you explain this? > use this attributes to raise notification Do you mean that attributes need to be sent in observations?

So when we send notifications should be influenced by attributes? For example, after exciding pmax? If so, could you point me to where notifications are triggered from after exciding said...

Response to https://github.com/eclipse-leshan/leshan/issues/1488#issuecomment-1684155286 >Maybe we can use : https://github.com/eclipse-leshan/leshan/issues/534 unless you see a good reason to not use it ? I looked through it but decided it would be easier...

>I explore it since few days and I begin to get clearer idea but this will lead to some deep modification at client side. I let you know as soon...

I looked through the code and other than the multi-threading "issue" described by https://github.com/eclipse-leshan/leshan/pull/1514#issuecomment-1726792151, I didn't have any issues. Also, it might be a good idea to be more clear...

> The "Server Public Key" Resource MUST NOT be used in the Pre-Shared Key mode. > As I see it, the "mandatory" field seems to be referring to the client...

Do attributes persist after de-registration and re-registration or do you have to send them again? For both options, why? Would it be possible to create a flag that could switch...

>I didn't think about Observe-Composite the code is not complete but this is more a proof of concept which can be used as base for more development about that. What...

AVSystem, IoTerop and 6D Tech LwM2M Server implementation of ETS 229 are suporting Read Composite with the overlapping paths, as-is, since the status is "passed" with some clients (for example...