Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: zhimi.heater.mc2a not recognized as climate #124

Closed
DenisV94 opened this issue Dec 17, 2024 · 1 comment · Fixed by #135
Closed

[Bug]: zhimi.heater.mc2a not recognized as climate #124

DenisV94 opened this issue Dec 17, 2024 · 1 comment · Fixed by #135
Assignees
Labels
bug Something isn't working

Comments

@DenisV94
Copy link

Describe the bug / 描述问题

The device zhimi.heater.mc2a is not recognized as a climate thermostat object in Home Assistant. It does not behave or integrate as expected, based on the Home Assistant Climate integration.

To Reproduce / 复现步骤

Steps to reproduce the behavior:

Go to Settings > Devices & Services > Xiaomi Home Integration.
Configure or add a zhimi.heater.mc2a device.
Attempt to control the heater or observe its entity type.
Notice that it does not appear or behave as a climate object.

Expected behavior / 预期结果

The zhimi.heater.mc2a device should be recognized as a climate entity in Home Assistant, allowing it to function as a thermostat object.

Home Assistant Logs / 系统日志

No response

Home Assistant Core version / Home Assistant Core 版本

2024.12.3

Home Assistant Operation System version / Home Assistant Operation System 版本

14.0

Xiaomi Home integration version / 米家集成版本

0.1.1

Additional context / 其他说明

No response

@DenisV94 DenisV94 added the bug Something isn't working label Dec 17, 2024
@JimmyKmi
Copy link

see #117

@topsworld topsworld self-assigned this Dec 18, 2024
@topsworld topsworld linked a pull request Dec 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants