reset_consumable command params

[CalamityDeadshot]

How do I know all possible params of the reset_comsumable command?

Auto-generated tiles use main_brush_work_time, sensor_dirty_time and so on as values of the params, but what value should I use if I want to, say, reset the detergent bottle state, or any other consumable? I'm using the dreame-vacuum integration, and none of its docs made me understand the mapping, and I can't seem to find anything in the HA UI besides the "Reset detergent" button that comes from the integration, but using a button.press action for that seems like such a hack. Can someone please point me in the right direction or, better yet, explain how it actually works, and where the values come from?

Thanks!

[PiotrMachowski]

but using a button.press action for that seems like such a hack

Why? As far as I know this is exactly what you should do :) Values used in the Xiaomi Miio template (main_brush_work_time, sensor_dirty_time) are passed to action vacuum.send_command which is considered to be a suboptimal solution - optimally there should be button entities for such actions.

Do you want to add such actions to your Vacuum Map card? If so, please post your config here

[CalamityDeadshot]

considered to be a suboptimal solution - optimally there should be button entities for such actions.

Why? Is this a convention?

Anyway, thank you. I implemented my detergent tile like this:

  - tile_id: detergent_left
    attribute: detergent_left
    label: Detergent left
    icon: mdi:dishwasher
    unit: "%"
    tap_action:
      action: call-service
      service: button.press
      target:
        entity_id: button.pookie_reset_detergent  # My vacuum is called Pookie, and she has a pink bow tie glued to her lidar btw
      confirmation:
        text: Did you actually buy and install a new detergent bottle?

I haven't tested this, cuz I didn't actually buy and install a new detergent bottle, but from what I googled it should work.

I'm still curious, though, as to where the params values come from, and how did you know the ones you used in the Xiaomi Miio template. I'm also curious - what is the call-service action? It's not in the possible actions list according to the Actions docs, nor could I really google any docs on it.

You can probably tell I'm new to this, huh :)

[PiotrMachowski]

Why? Is this a convention?

Generally vacuum.send_command is a bit of a "hack" that allows users to perform actions that are not "officially" supported by HA (e.g. in a form of button entities).

I'm still curious, though, as to where the params values come from,

They are specific to a vacuum, in case of Xiaomi vacuums they can be found here

I'm also curious - what is the call-service action?

"service" is an old name for "action". This card hasn't yet been adjusted to these changes, so it still uses old naming

[CalamityDeadshot]

It's OK, even preferred, to use button entities for that purpose. The protocol is available here, although, from what I can tell, not in full.

Thank you, @PiotrMachowski!