## Introduction
The Xiaomi Home Assistant is a popular home automation system that integrates with various devices, including the Xiaomi fan. However, some users have encountered an issue with the fan speed control in version 3.2. In this article, we will discuss the problem, its causes, and the solution.
## Problem Description
The issue arises when trying to adjust the fan speed using the Xiaomi Home Assistant. The fan speed is not adjusted correctly, and the device only responds at 4% of the maximum speed, even when set to 100%. This problem is caused by an incorrect mapping of the fan speed levels.
## Solution
The solution to this problem is to modify the `spec_modify.yaml` file in the `custom_components/xiaomi_home/miot/specs` directory. By adding the following lines to the file, the issue can be resolved:
```yml
urn:miot-spec-v2:device:fan:0000A005:xiaomi-p43:3:
prop.2.6:
name: fan-level-a
```
## Reproduction Steps
To reproduce the issue, follow these steps:
1. Upgrade to Xiaomi Home Assistant version 3.2.
2. Try to adjust the fan speed using the Xiaomi Home Assistant.
3. Observe that the fan speed is not adjusted correctly.
## Expected Behavior
The expected behavior is that the fan speed should be adjusted correctly, and the device should respond to the set speed.
## Logs and Version Information
The issue has been verified, and the following logs and version information are available:
* Home Assistant Core Version: 2025.5.2
* Home Assistant Operation System Version: 15.2
* Xiaomi Home Integration Version: 3.2
* Log Timezone: Asia/Shanghai
## Additional Context
The solution to this problem was obtained from issue #1110. By modifying the `spec_modify.yaml` file, the issue can be resolved, and the fan speed can be adjusted correctly.
## Conclusion
In conclusion, the fan speed control error in the Xiaomi Home Assistant version 3.2 is caused by an incorrect mapping of the fan speed levels. By modifying the `spec_modify.yaml` file, the issue can be resolved, and the fan speed can be adjusted correctly. This solution has been verified, and the issue has been closed.