Matter Device Missing Features? Check the Supported Version, Clusters and Controller

Basic control and complete feature support are different

A Reddit homeowner considering Matter asks whether functions remain trapped in manufacturer apps. Commenters describe devices that support ordinary control but expose fewer options elsewhere. Those are individual reports, not a current compatibility list or proof of a platform-wide defect. They frame the useful question: which exact function is missing from which control path?

Write down the desired action or reading, the device model and firmware, and the controller and integration used. A working on/off command establishes one capability. It does not establish energy reporting, calibration, schedules or every manufacturer-specific effect.

Source: Owner asks about Matter feature limitations; commenters report native-app differences

Check the feature definition and both implementations

Matter defines device types and clusters. A cluster is a defined group of related commands or data attributes. New specification versions can add device types, clusters and revisions, but products and controllers must actually implement the relevant functionality. Do not assume a higher version number makes every optional feature available.

For example, the Connectivity Standards Alliance identifies Electrical Power Measurement and Electrical Energy Measurement as additions introduced with Matter 1.3. A plug that exposes switching but not those measurements may need different device firmware, controller support or both. A transport change from Thread to Wi-Fi would not by itself add a missing application feature.

Source: CSA: Matter Energy Measurement Clusters Introduced in 1.3

Example: Eve Energy changed how it reports measurements

Eve’s April 10, 2025 announcement describes a firmware update moving Eve Energy from proprietary energy reporting to Matter-defined reporting. It also states that platforms supporting those reporting functions, with Home Assistant as its example, can receive power, voltage, current and cumulative consumption. This dated implementation example is not a claim that every platform exposes all Eve measurements today.

For an installed plug, verify the exact hardware and released firmware, then check whether the intended controller displays the required instantaneous and cumulative readings. Do not confuse the Eve Android app’s version number mentioned in the announcement with the Matter specification version. Avoid resetting an otherwise reachable plug before establishing which layer lacks support.

Source: Eve: April 2025 Energy Reporting Firmware and Platform Support

A supported native integration may remain useful

Home Assistant’s Matter guidance notes that a product-specific local integration can expose features absent from its Matter path. Keep a required native feature on a documented supported path if necessary, and avoid creating duplicate everyday controls without a purpose.

Use a focused record: required function, device support, controller support, retained app and verified result. Firmware updates and account administration may still have their own requirements. Whole-home dependency inventory and migration ownership are covered separately in the local-control guide.

Source: Matter - Home Assistant

Put it into practice

A decision table to keep handy