Unable to use element object in service_data for image_set service

[garyjlo]

I was trying to set a rule that, based on an HA weather entity, I could set multiple elements in my SVG floorplan, in this case, a text_set for the temperature and image_set an icon for the weather condition.

    - entity: weather.demo_weather_north
      state_action:
        - action: call-service
          service: floorplan.text_set
          service_data:
            element: sensor.weather_temperature
            shift_y_axis: 2em
            text: ${ entity.attributes.temperature }${ entity.attributes.temperature_unit }
        - action: call-service
          service: floorplan.image_set
          service_data:
            element: sensor.weather_condition
            image: /local/icons/weather/${ entity.state }.svg

I did a lot of trial and error and could not get it to work.

Eventually I found a successful workaround by splitting it into two rules, with the image_set one moving the element field up to the top level, out of service_data:

    - entity: weather.demo_weather_north
      state_action:
          action: call-service
          service: floorplan.text_set
          service_data:
            element: sensor.weather_temperature
            shift_y_axis: 2em
            text: ${ entity.attributes.temperature }${ entity.attributes.temperature_unit }

    - entity: weather.demo_weather_north
      element: sensor.weather_condition  #<-- element moved out of service_data
      state_action:
        action: call-service
        service: floorplan.image_set
        service_data:
          image: /local/icons/weather/${ entity.state }.svg

Is this a bug? The documentation lists element and elements as valid objects for all service_data sections.

[exetico]

Hi,

Could you please let me know where you find the reference, pointing you to add element as a service_data key?

    - entity: weather.demo_weather_north
      state_action:
        - action: call-service
          service: floorplan.text_set
          service_data:
            element: sensor.weather_temperature ⬅️ I'm asking about this
            shift_y_axis: 2em
            text: ${ entity.attributes.temperature }${ entity.attributes.temperature_unit }
        - action: call-service
          service: floorplan.image_set
          service_data:
            element: sensor.weather_condition
            image: /local/icons/weather/${ entity.state }.svg

The element reference neds to be at the top of the rule, in other words, at the same level, as you define state_action, tap_action and so on 😄 .

If you've found a broken example, I'd be more than happy to correct that, or look into any misleading information.

Maybe I even remember wrongly. If it was meant to work this way, and it's now not working anymore, I'll take a look at that.

[garyjlo]

This documentation implies to me it would work this way:

https://experiencelovelace.github.io/ha-floorplan/docs/usage/#services

The table seems to indicate that element and elements are allowed to be used as keys within the service_data section.

I think it is important to keep that functionality... so I am hoping it's not a bug or broken example 😅
If not, how would we approach the use case of styling multiple SVG elements based on the change in one HA entity, like in my example?

As far as I can tell, element key in service_data section seems to work for text_set and style_set services, just not image_set.

[exetico]

Thank you for providing the extra context.

[exetico]

I've introduced a solution for this in: #519 (comment)

Please provide feedback in the mentioned issue, if you find any bugs. You cannot use elements for this feature (only a single element is supported)

[garyjlo]

Hey @exetico, going over the docs again, I did find some examples showing element use within the service_data block of some other services, I believe these examples probably led me down the path of trying it for my use case with image_set:

(https://experiencelovelace.github.io/ha-floorplan/docs/usage/#using-text_set-to-render-mulitple-tspans-on-linebreakes)

- entities:
    - binary_sensor.kitchen
    - binary_sensor.laundry
  state_action:
    action: call-service
    service: floorplan.text_set
    service_data:
      element: sample.multilinegroup_text
      shift_y_axis: 1.5em
      text: |
        > /* Note that this is a JavaScript block, where you normally can do cool stuff like console.log()*/
        return 'Multiline\nTSPAN-Print';

(https://experiencelovelace.github.io/ha-floorplan/docs/usage/#using-style_set-with-a-block-of-javascript-code)

- entity: sensor.moisture_level
  state_action:
    action: call-service
    service: floorplan.style_set
    service_data:
      element: moisture-level-clip-path
      style: |
        >
        var height = Math.ceil(elements['sensor.moisture_level'].getBBox().height);
        return `transform: translate(0, ${height - Math.floor(entity.attributes.level / (100 / height))}px)`;