The air conditioner is connected to the Home app via Matter Bridge, and two different methods have resulted in different behaviors:
After scanning the QR code to bind the air conditioner, a fan speed slider is displayed.
If the air conditioner is first added to MatterBridge (a gateway with Zigbee functionality), and then scanned to bind it to the Home app, the fan speed slider is not displayed.
Data reporting is the same.
The air conditioner is connected to the Home app via Matter Bridge, and two different methods have resulted in different behaviors:
- After scanning the QR code to bind the air conditioner, a fan speed slider is displayed.
- If the air conditioner is first added to MatterBridge (a gateway with Zigbee functionality), and then scanned to bind it to the Home app, the fan speed slider is not displayed.
I don't have time to try and fully reconcile the two different matter configurations but a superficial scan of the logs shows enough difference that I think the MatterBridge is simply publishing a configuration that Home isn't recognizing. The next step here is to:
Fully validate both matter configurations to find any differences.
Determine whether or not those differences are within the variation allowed by the matter spec.
Depending on what you find in #2, either file bugs against HomeKit (for failing to support a valid configuration) or MatterBridge (for publishing an invalid configuration).
If the accessory has been properly certified then the issue is probably with MatterBridge, however, there's no way to know without doing the full analysis.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware
