Add Tasshack/dreame-vacuum platform
Tasshack opened this issue · comments
Integration repository
https://github.com/Tasshack/dreame-vacuum
Supported features
- Zone cleaning (using 4 coordinates)
- Room cleaning (using room id/number)
- Going to point (using 2 coordinates)
- Cleaning a point (using 2 coordinates)
- Others
Vacuum entity/entities
Service calls
Other info
I have already made the required changes. I am creating this issue just to link it with the pull request.
Is the feature "Going to point" necessary for a merge? I just stumbled upon this and would be happy to use these awesome cards in my Home Assistant Setup with Tasshack's Dreame Integration. I could also look into that feature if help is needed.
@thebiff999, no, it's not necessary. I will merge it soon
@thebiff999 it has been so long since i have opened this pull request i have started developing my own interative map card just for the dreame_vacuum integration and you are going to love it.
@PiotrMachowski is there an ETA for the next release so the dreame integration can be used?
@Tasshack do you share some beta access to test this?
@xBourner it's already perfectly possible to use it, you just have to override default service calls: https://github.com/Tasshack/dreame-vacuum#with-xiaomi-vacuum-map-card
@PiotrMachowski thanks for the answer. i am getting the error:
missed comma between flow collection entries (2:2)
1 | {# ----------------- PROVIDE YOUR ...
2 | {% set camera_entity = "camera." %}
------^
3 | {% set vacuum_entity = "vacuum." %}
4 | {# ------------------- DO NOT CHA ...
seems like templates are not allowed. do i need anything to enable this?
i tried to add the code to your custom card.
@Tasshack Could you provide more info about following attributes of vacuum entity?
water_volumemop_pad_humidity
I'm especially interested in possible values and units
@PiotrMachowski vacuums with onboard water tank uses water_volume for controlling the amount of water used while cleaning.
Vacuums with washing station does not have water_volume attribute instead they use mop_pad_humidity to control the drying amount of the mop after each wash cycle. Currently, it is not possible for a robot that has both attributes at the same time.
Although these attributes tied to different properties on the device, customized cleaning settings (in the map data) uses same array index for both types of robots as water volume and mop pad humidity.
Names of the possible values extracted directly from the Mi Home app for convenience to the users.
You can checkout all possible values from the translation files.
None of the option entites has exposed units therefore atrribute value of the equivalent entity does not append a unit to the value string.
@Tasshack One more thing: in your PR you have added tiles using attributes of vacuum entity. Do you plan to add support for attribute translations to your integration?
@PiotrMachowski it was not possible when i first started the project so i wasn't planning on translating attribute values. All values for all attributes has already translations for sensor and select entities but i have to check how it is possible to translate vacuum attribute values from latest version of the HA.
@Tasshack I've asked about it because I have already added support for using integration's translations to the card (both states and attributes). If you plan to add translations to attributes then the card will be able to use them as well. In the other case I think it would be better to use dedicated entities instead. Additional benefit of using entities is that they will be translated even in earlier HA versions.
@PiotrMachowski I have tried to use the entities instead of attribues but the problem is not all entities are available (returns state as unavailable) all the time, that is why i choose to use vacuum attributes instead.
@Tasshack which entities have this problem? It's possible to use attributes just for these entities that return unavailable states
Done in v2.2.0