Thank you for the reply, it is greatly appreciated and I acknowledge that the transition to fully utilised the DDF is still in progress.
I know as previously you indicated that “For REST-API plans there will be separate detailed post” and this may have been an early question and feedback however, I do agree with @lakehawk feedback. It is an especially good response whilst this is still under review and development. The proposal would result in more consistent, and efficient api if this was designed similar to lights capabilities as you detailed in the 2025 deCONZ Development Overview / Roadmap(ish). In doing so, this would enable a single call to extract the full dataset and you could potentially eventually deprecaite Introspection.
REST-API
For REST-API plans there will be separate detailed post. One goal is to continue to cleanup the internals and split out device and vendor specific handlers. The
devices/endpoint reading side needs to be completed and hooked into Websocket events. Last year we got thecapabilitiesfor devices in DDFs for lights. The API should also dynamically make use of this information so we can phase out more modelid specific code.