Roshan Rajaratnam

Hi any update on this? colon in a path variable seem to be encoded as `%253A` instead of just `%3A`.

Hi thanks for pointing this out. This indeed is a known drawback in the library as of now. We'll try to get this fixed for the next release.

Hi never seen this happening. Seems like the firmware dropping the connection here. Are you using our examples or is this happening on your own firmware?

Hi, you are correct java stores multibyte values in big endian format. However IMHO the 3 byte opcode for a vendor model should be depicted according to the specification. Therefore...

Here's the link to the spec. https://www.bluetooth.com/specifications/specs/mesh-profile-1-0-1/ The behavior I mentioned is what's expected due to the company identifier being a 16-bit value where the Endianness gets applied. When sending/receiving...

So basically when both sending and receiving the order should be as follows `0xE3 0x36 0x01` and `MeshParserUtils.getOpCode()` will now return the opcode on its own without the company identifier...

Hi @Kleak, could you elaborate a little bit more on this? As of now every time the network is changed due to a mesh message that is sent/received you receive...

Right I see, this is something I can look into but it will have to wait a little bit unfortunately. What I can do is add a callback for each...

ok, as of now I have some other priorities but i will look in to as soon as I get some time.

Hi, if the message is segmented or is acknowledged you should wait for the first message to be processed. A node can already be busy processing a message or if...