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
zhimi.heater.na1 fails on discover climate entity #122
Comments
Do you mean |
still throws an error:
|
The exception stack trace you provided doesn't match the latest code. Perhaps you didn't install the latest commit successfully. Try again. |
Sorry, did a Seems to be discovered as a climate entity now. Any way to change from "preset" for fan swing/not swing to "swing mode"? Also, can the climate entity supporr target temperature if using an external temperature sensor? There are 2 more options on this device:
|
The climate entity can support current temperature to use an external temperature sensor. |
Afaik, HA doesn't turn off the heater when it reaches desired temperature. What you said was achived by Generic Thermostat 's code. See these: |
Any climate entity would behave the same according to https://developers.home-assistant.io/docs/core/entity/climate/, it needs to have I've been playing around a bit and ran into some more errors: This happens when trying to turn on indicator_light.
most likely because the indicator_light implementation in this device does not have switch_status and uses value When the device is in the input mapping part of the config flow it doesn't auto select lock and indicator_light anymore. If I don't choose them from the dropdown and tick the checkboxes they cannot be configured from the CONFIGURE options even though they're shown there If I add "lock" in the mapping menu, then try to add both indicator and lock from CONFIGURE menu, only the lock entity is added If I try to add the temperature sensor later in the CONFIG menu I get the following error:
I figured out the mapping for additional features on the device and will make a PR Thanks for making a lot of it customizable! |
I think you have misunderstood the document. Do you refer to that
? That means that the stop of heating was handled by the device and reported to hass, so hass will know that the device is in heating mode but it is stopping now. |
I was referring to this function in generic thermostat. Might be wrong with my limited Python knowledge, but the same feature works in Generic Thermostat and MQTT Climate entity. Something like that in miot_raw component should allow to set target temperature in the UI card even if the miot spec doesn't have target_temperature property and then control the device based on that setting. |
This commit should fix the problem on indicator_light. |
As you can see, the If your device support setting it, you can set it directly; otherwise, you can implement it by automation. |
Yes, thank you. It was clarified by HA developers that internal heating control is implemented if an integration needs it. I've resolved the problem by creating a template switch which is then used by generic thermostat. |
That's good. I've seen your comment in the issue of another integration. How did you know that integration? |
I've searching for all the ways of integrating xiaomi devices in Home Assistant. I'm doing a lot of testing for my blog and compatibility websites |
That's amazing. This integration aims to integrate ALL xiaomi devices and make users get rid of all YAMLs. Maybe I should improve English document in case others can't find it. |
While not an issue for me, having chinese as default in HACS and when adding a device in the integration will stop many users from using this component |
Many thanks for your kind and constructive feedback! |
Having issues adding zhimi.heater.na1
Climate entity throws two types of error.
Child Lock and Indicator light are discovered once enabled in Configuration.
Still missing the "Return to home" (urn:zhimi-spec:property:return-to-middle:00000003:zhimi-na1:1) and sound control (urn:miot-spec-v2:service:alarm:00007804:zhimi-na1:1) toggles
The text was updated successfully, but these errors were encountered: