Good idea @Delphy, I’ll add that to our firmware backlog.
If someone wanted to implement this in the meantime, or submit a pull request, those enums are used here:
The different types are sent as part of the payload to the device service, and they’re byte encoded (I am having trouble remembering the standard off the top of my head). I’m guessing we’ll be able to get to this when we address the different variable return type / weird encoding bug mentioned in other threads.
Thanks for the response. I was curious about why DOUBLE was listed as 9 in the enum - if it was binary, shouldn’t it be 8 instead? I’ll have a browse through the core-communication-lib and see if I can’t contribute something rather than asking lots of questions.