Hi, I’m new here, so I apologize for maybe the usual things and for my English.
I integrate my Xiaomi air purifier, I have two, older 2S and newer 3H.
Home Assistant version 2021.3.4 (runs as a virtual machine on Synology NAS DS716 + II)
First I integrated 3H (name Air Purifier Office, entity fan.air_purifier_office).
I think it’s pretty cool, except for a little bugs, but I’ll leave them out now.
Now I need to add the second one, model “2S” (Air Purifier Bedroom, entity fan.air_purifier_office_2). But I don’t know exactly how to rename everything correctly.
In the basic definition of fan: (configuration.yaml) I already have both purifiers (see picture), the second purifier is now also visible, I can turn it on and off. But I need to add more sections to the sensor, switch and input sections (configuration.yaml).
And of course to the automations.yaml file
Thank you very much, I am a complete beginner in H.A.
Firstly I would like to thanks to all the contributor in this threads, got me going for years until recently…
The latest update a few things changed. 3 main things look out for
1 . It no longer accepts the fan: - platform: xiaomi_miio in configuration.yaml. Remove that. Its now in the Intergration UI.
2. Look in the Developer Tools make sure the name of the device still that same, It might now be fan.airpurifierxx_2 remove the old one and rename it back to fan.airpurifierxx.
3. Some of the service name also change eg fan.set_speed is replace by fan.set_preset_mode, it still might work but throw a lot of errors in the logs, so if things dont work as expected look through the service call see if need change there.
I am using this custom_components which setup similar to previous, and dont throw errors in the logs. Even if you dont use the components scroll through the example scripts which is much the same as this thread which might get you back on tracks.
you can also add filter life remaining in days - you have to devide hours used by 24 to get days. What I’ve noticed new filters have 145 days total, so that should give the same information as Xiaomi Home App:
One one hand, it is nice I can remove a lot of the template and binary sensors from my configuration.yaml as they are now separate entities.
But I am a bit worried how I need to update my automations that rely on Favorite Level.
Yes! I’m happy to see the team is finally adding all the sensors and switches that were missing. My configuration file will be slimmed down significantly.
Will have to do some updating my lovelace and automations.
Quick question, is anyone else hit by the warning that fan.set_speed is deprecated in their logs, while not using it?
It only happens once shortly after server startup.
[homeassistant.components.fan] The fan.set_speed service is deprecated, use fan.set_percentage or fan.set_preset_mode instead
When it was first announced a while ago, I made sure to modify all configuration to align with this. And I have gone through all my files (multiple times) with Search to see if it’s there somewhere.
That’s coming from the Xiaomi integration. Should be resolved with the next release of HA (2021.9.x). At least the changelog for this intergation shows a lot of changes… See link above to check it out.
Can you set the fan to ‘Auto’ with the latest updates? I have been testing it today, a switch for auto doesn’t seem to be exposed.
Also, it seems the new entities use the ‘Area’ name when creating the new entities instead of the device name. Is this on purpose? So instead of switch.master_bedroom_air_purifier_child_lock I have switch.master_bedroom_child_lock. IMO using the device name would be better.
No idea how to contact the devs for this feedback so I am posting here.
Hi everyone, the latest breaking update have simplify things quite alot. They have done a fantastic job. We no longer need template sensors and switches. They are now all separates entities. And we no longer need to have all the complex automation as well because of the new template entities: Number and Select.
All you need is to add the following to your configuration.yaml for the select input modes:
The lovelace humidifier card have slider for the target humidity, and the favorite levels is now a “number” entity called [ number.xxx_favorite_level ]
Thank you for your trick.
I’ve tried your “Air Purifier Mode” template but, unfortunately, in my case it doesn’t seem to work.
This is what I can find in my logs:
Logger: homeassistant.components.template.template_entity
Source: components/template/template_entity.py:94
Integration: Template (documentation, issues)
First occurred: 23:06:41 (1 occurrences)
Last logged: 23:06:41
Error validating template result 'None' from template 'Template("{{ state_attr('fan.zhimi_airpurifier_v2', 'preset_mode') }}")' for attribute '_attr_current_option' in entity select.air_purifier_mode validation message 'string value is None'