This is one of my internal W.I.P. projects, but I thought it may be useful for other developers and advanced users even at its current state...
Matter Advanced Device is a diagnostic and utility driver for a Matter device paired directly to your hub. Think of it as the Matter equivalent of the built-in Device driver: point it at any Matter device, and it discovers every endpoint and cluster, reads or writes any attribute, invokes any command, and manages subscriptions, through either a plain English menu or expert commands by name or by number.
Highlights:
- Full discovery, plus a Get Info Advanced dump of every cluster and attribute.
- A picker for endpoint, cluster, and attribute once the device has been discovered.
- Read Something: pick Firmware version, Battery level, Temperature, On/Off state, and more from a dropdown, no Matter knowledge required.
- Expert read, write, invoke, and subscribe commands, and a one-line command box for people who would rather type.
- Firmware version and Matter update status, including live progress of an update started by another app on the same fabric.
- The same housekeeping commands as the built-in Device driver.
It is a diagnostic tool, not something to leave assigned to a device you use every day. Change the Type back when you are done looking.
Install: There are no plans to include it in the HPM package; this one is for developers and advanced users for now.
Import directly:
https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Matter%20Advanced%20Device/Matter_Advanced_Device.groovy
Change the device Type to Matter Advanced Device, Save Device, then press Configure
once.
Status: tested so far against an IKEA GRILLPLATS plug and an IKEA DIRIGERA bridge,
platform 2.5.1.156. The write path and the picker still need real world testing.
Somoe more detailed docs and command reference: Hubitat/Drivers/Matter Advanced Device/README.md at development · kkossev/Hubitat · GitHub
Bug reports and logs from other devices are very welcome.
As everyone can probably guess by now, this driver and its documentation were mostly written by AI agents (Claude Code and OpenAI Codex), with @kkossev doing the hardware testing, the yelling at bugs, and the final judgment calls.
