Handling desynchronized map/preset

[PiotrMachowski]

If you use activate with activate_on_switch to switch presented maps and current map preset becomes desynchronized from shown map you can just click on preset's name to manually trigger activate service call.

[eSKape-debug]

@PiotrMachowski is it somehow possible to call this activate service from a homeassistant script or automation?
I'd like to load the current preset (matching the map) of my 3 presets the time the card is shown - while not loosing the functionality of preset switching as shown in the picture above.

[PiotrMachowski]

What approach would you consider as a correct one? Just selecting the preset based on the condition, instead of hiding it?

[eSKape-debug]

i fixed that for myself using the changes here: master...eSKape-debug:lovelace-xiaomi-vacuum-map-card:master

a new top level config param is introduced which uses an input_number entity to store the currently selected map id - however, as this was just quick and dirty, this currently only works if the order of presets is the same as the numerical order of map ids, meaning 1st preset is id 0, 2nd preset is id 1, etc. (array index selection in code)

type: custom:xiaomi-vacuum-map-card
preset_name: Erdgeschoss
entity: vacuum.roborock_vacuum_s5e
current_preset: input_number.vacuum_map_id
activate_on_switch: true
activate:
  service: script.turn_on
  service_data:
    entity_id: script.vacuum_handle_map_reload
    variables:
      map_id: 0
.....

the script in the actions additionally handles the update of the entity (might also be done in the map-card code)
As a first step - this works for me

Screencast of the result: https://github.com/eSKape-debug/lovelace-xiaomi-vacuum-map-card/blob/master/docs/Bildschirmaufnahme%202024-02-22%20um%2019.32.08-1.mov

[junado]

If it has to work within the confines of the yaml card configuration, perhaps having a "selected" true/false option as part of the preset options? I'd see it as optional, defaults to false. If multiple values are true, select the first preset that matches. If all values are false, defaults to first preset (current operation). This would let us add conditional selection of active preset through Jinja templates.

[PiotrMachowski]

@junado keep in mind that jinja templates are not currently allowed in yaml config - that's why I used conditions instead.

[junado]

@junado keep in mind that jinja templates are not currently allowed in yaml config - that's why I used conditions instead.

I understand, I meant JavaScript (it's a bit confusing, since Jinja can be used inside of styles for card_mod, so it's all mixed in there). Since you already have the conditions built into the card, perhaps using conditions to select the active preset could work? It would essentially be the same as the show/hide conditions, but would select the preset if the condition is true.