olavt

@marcelveldt Did you make any explicit changes lately to address this? When testing now with 5.8.0, I get the format like this again: "0/51/0": [ { "0": "OpenThread-9244", "1": true,...

I still see "randomness" in format. This is from 5.8.1 setup from a blank data directory: "0/53/61": { "activeTimestampPresent": true, "pendingTimestampPresent": false, "masterKeyPresent": true, "networkNamePresent": true, "extendedPanIdPresent": true, "meshLocalPrefixPresent": true,...

I have a question about the format if index are used for structs that are fabric-scoped. This is an example where names are used: "0/42/0": [ { "providerNodeID": 1, "endpoint":...

I found the answer to my last concerns about the index of the "fabricIndex" field and it is documented under 7.13. Global Elements to be 0xFE (245).

I wasn't aware that the WEB_GUI flag wasn't on by default. I have later been made aware that one need to set that flag.

Not sure. I'm using a Raspberry Pi 4 with Raspberry Pi OS (latest).

Why limit the result to 200 and not allow for larger number of users?

Shouldn't the maximum number of users returned by the API be implemented similar to other Azure API's that potentially return a large number of items like the ListBlobs API documented...

Great! I was just looking at the API-commands in the source code and couldn't see how one could trigger the update from a provided Url. Can you give me a...

Wouldn't it be better to put the updates directory under the data directory by default?