I am currently developing an air quality monitoring device that supports the Matter protocol and is intended to integrate with HomeKit. During the development process, I've encountered a couple of issues regarding sensor data display within the Home app and would appreciate any insights from the community. Issue 1: Temperature Sensor Display We have observed that when the temperature sensor is implemented as a cluster within the device, its data fails to appear in the Home app interface. However, if it is configured as an independent endpoint, it displays correctly. Is this a specific requirement of HomeKit regarding the structure of clusters and endpoints in Matter devices? Issue 2: Support for HCHO and TVOC Sensor Display Does HomeKit currently support displaying real-time data from HCHO (Formaldehyde) and TVOC sensors? If so, are there specific cluster specifications or data types that need to be followed?

Hi Team, I’ve tried downloading the EnableBluetoothCentralMatterClientDeveloperMode.mobileconfig certificate from multiple sources, but all the links I found point to expired versions. Could you please help me with the URL to the latest version of this certificate? Here are the links I’ve already tried, but none of them worked: https://project-chip.github.io/connectedhomeip-doc/guides/darwin.html#profile-installation https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/darwin.md Apple Site Looking forward to your support. Thanks, Mantosh Kumar

My iOS app uses the Matter framework to commission devices over Wi-Fi (not Thread). With the Matter Client Developer Profile installed, commissioning works perfectly. However, in TestFlight builds without the profile, commissioning fails, even though the app includes the Matter Allow Setup Payload capability and the following in Info.plist: <key>NSBonjourServices</key> <array> <string>_matter._tcp</string> <string>_matterc._udp</string> <string>_matterd._udp</string> </array> How can I enable Matter device commissioning using the Matter framework in production/TestFlight builds without the Matter Client Developer Profile? Please provide guidance or specific configurations needed for production environments

I am working on an app (iOS, iPadOS & macOS (Mac Catalyst)) for a Home Automation device. I am using HomeKit APIs to access commissioned devices and provided APIs to get a MatterNodeID and then a MTRBaseDevice so I can query the device. Since the current APIs for accessing Matter devices this way do not support subscriptions I am using the readAttributes() method of the MTRBaseDevice to get information from the device. There can be significant lag time in these reads and I realize my network speed and congestion can contribute to this. The time lag makes me wonder how readAttributes() obtains the data? Does the method query the Home hub which replies using cached data, or does the hub in turn query the device to insure it is providing the latest data? I am pretty sure all this communication goes through the hub because it works whether I am on the same network as the device or in a location far, far away.

Connect the Zigbee color temperature light bridge to the Home app through the Matter Bridge (a device with a screen), and adjust the color temperature of the light on the screen. However, the color temperature of the corresponding device on the Home app is not synchronized, as shown in the following figure What information is missing from the Home app when my device reports color temperature during control?

Hi, We are developing a Matter switch product. The switch contains 4 buttons, and each button supports click, double click, and held actions. Currently, the device can be successfully commissioned with a HomePod mini, and in the Apple Home app, it is displayed as 4 buttons with options for click, double click, and held for each. The only issue is that the order of the 4 buttons in the Home app does not correspond to the endpoint order (endpoint 1–4). For example, the following mapping might occur: endpoint 1 → button 2 endpoint 2 → button 3 ... We found a related issue on the Apple Developer Forums that matches what we're experiencing: https://developer.apple.com/forums/thread/772367?utm_source=chatgpt.com According to the official response, the problem seems to be caused by insufficient metadata being reported by the device. Could you please provide more specific guidance on what exact information needs to be reported from the device side? We have already tried adding the Fixed Label and User Label clusters to the device, but they don't seem to have any effect. Ideally, we would like the button labels in the Home app add our custom names in the correct order, as below: button 1 (right_button) button 2 (up_button) button 3 (down_button) button 4 (left_button) This would provide a much better user experience. Thank you in advance!

since macOS 15.5 and iOS 18.5 bridged matter devices have isBridged set to false and the respective bridge device has an empty uniqueIdentifiersForBridgedAccessories list. before these updates both were set as expected. i also noticed that the bridged matter devices include all endpoints for all bridged devices. not only the ones for themselves.

Hi, I have tried to add Eve energy plug but still pairing failed, it reported always same error. Error Domain=com.apple.MatterSupport Code=1 "(null)" Could anyone help? Regards