# \[APP\]\[Pro\] Thread Diagnostics - Continuously log your Thread mesh & Matter device health

**URL:** https://community.homey.app/t/app-pro-thread-diagnostics-continuously-log-your-thread-mesh-matter-device-health/157930
**Category:** Apps
**Tags:** homey-pro-2023
**Created:** [August 5, 2026, 8:19am UTC](https://community.homey.app/t/app-pro-thread-diagnostics-continuously-log-your-thread-mesh-matter-device-health/157930 "2026-08-05T08:19:24Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![staeff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/staeff/32/79712_2.png) [@staeff](https://community.homey.app/u/staeff)
#### Post date: [August 11, 2026, 5:23am UTC](https://community.homey.app/t/app-pro-thread-diagnostics-continuously-log-your-thread-mesh-matter-device-health/157930/5 "2026-08-11T05:23:43Z")

</div>

This error message is indeed a bit weird, because if the scopes are wrong it simply tells you “Missing scope” in the reasons. If the key in general is incorrect it will tell you “Invalid session”. So this specifically sounds like an issue to call the endpoint and not like a problem with the key.

What homey are you using and which version are you on?

When you go the the homey developer page [Web API playground](https://tools.developer.homey.app/tools/api-playground) and try to run `Homey.thread.executeCommand({ command: 'leaderdata' })` does that work?

---

_[View the full topic](https://community.homey.app/t/app-pro-thread-diagnostics-continuously-log-your-thread-mesh-matter-device-health/157930)._
