I agree with you, even if it is a low-level API that is not intended for explicit use, it might be useful to know what’s happening down there. So, added to the report! = )
As at the moment the
device.thread.timers doesn’t provide a human-readable reference of the timer/schedule, I think you might find useful the following references to keep track of your timers/schedules:
These resources provide the reference of the driver and device timer/schedules including the label, which can help you to debug and maintain your timers.