message: "extra keys not allowed @ data['entity_id']"

[AlexK98]

Hello,
trying to create a slider control to set Float Voltage setting of the hybrid inverter via mqtt.
And I get the following error:

In browser console it looks like this:

code: "invalid_format"
​message: "extra keys not allowed @ data['entity_id']"

here is the code of my helper:

input_number:
  float_voltage_slider:
    name: "Float Voltage Slider"
    min: 52.0
    max: 58.0
    step: 0.1
    mode: slider

here is the code of my card:

features:
  - type: custom:service-call
    entries:
      - type: slider
        entity_id: input_number.float_voltage_slider
        range:
          - 52
          - 58
        tap_action:
          action: perform-action
          perform_action: mqtt.publish
          target:
            entity_id: input_number.float_voltage_slider
          data:
            topic: PowMr/DeviceControl/Set_Command
            payload: PBFT{{states('input_number.float_voltage_slider')}}
        step: 0.1
        haptics: false
        thumb: line
        label: "{{ value | float }}"
        autofill_entity_id: true
type: tile
entity: sensor.powmr_inverter_battery_float_voltage
name: Float

I'm not sure what should be in the:

tap_action:
  target:
    entity_id: ??????????????????????

Also, these MQTT related fields, so some reason, where not automatically enabled:

Thanks for the help.

[Nerwyn]

Try disabling autofill and removing the target.

[AlexK98]

Ok, I managed to format data properly with this code:

{% set identifier = "PBFT" %}
{% set number = value %}
{{ identifier ~ (number | float | round(1) if number | float % 1 != 0 else (number | int) ~ ".0") }}

But I still get issue that handle sticks to the old value despite changes applied.

I created another tile card with the my input_number helper:

Altering this blueish slider adjusts your slider component's handle position and displayed value but not vice versa:

Despite the changes of the value on the feature slider component, no mqtt command gets sent, which is a proper behavior, i believe.

[Nerwyn]

To clarify, the slider is now properly sending the MQTT publish action right?

It looks like you're using a helper input_number entity. Your slider action doesn't update this entity's value, but calls the mqtt.publish action instead. I'm guessing this number is the value of the entity sensor.powmr_inverter_battery_float_voltage? It sounds like you need to create an automation which updates the value of input_number.float_voltage_slider when sensor.powmr_inverter_battery_float_voltage changes.

The automation should look like this:

description: ""
mode: single
triggers:
  - trigger: numeric_state
    entity_id:
      - sensor.powmr_inverter_battery_float_voltage
conditions: []
actions:
  - action: input_number.set_value
    metadata: {}
    data:
      value: '{{ states("sensor.powmr_inverter_battery_float_voltage" }}'
    target:
      entity_id: input_number.float_voltage_slider

[AlexK98]

To clarify, the slider is now properly sending the MQTT publish action right?

Yes, I played a bit more with configuration and it now properly executes MQTT action.

Also, instead of heaving input_number entity helper in main Entity field, I use sensor.powmr_inverter_battery_float_voltage directly for it. So, now, once sensor's value is updated, the slider's handle also updates it position accordingly, but I had to set "after action update delay" value to 10000ms for things to look nice.

---

Also...
Let's say I want to make abstract slider and button next to it. With slider I will define the value and with button I will send MQTT action.
Can I somehow directly reference Value from feature slider in the payload of feature button's mqtt action?

---

It is good that users can dynamically set range in slider based on values from other numerical entities. Still it would be good to have UI to enter desired calls instead of opening the whole card definition. Something like this:

[Nerwyn]

Also, instead of heaving input_number entity helper in main Entity field, I use sensor.powmr_inverter_battery_float_voltage directly for it.

That makes a lot more sense for this use case.

Let's say I want to make abstract slider and button next to it. With slider I will define the value and with button I will send MQTT action.
Can I somehow directly reference Value from feature slider in the payload of feature button's mqtt action?

The features in a row are all separate and you can't reference sibling feature values. In this use case you should make the slider use an input_number entity like before, and then make the button use the MQTT publish action using the input number entity state.

It is good that users can dynamically set range in slider based on values from other numerical entities.

The range field is already templatable, and since this is a niche use case there is no plan to add a GUI element to better support non-numerical entry into this field. The YAML/code editor options are easy to switch to and use as is, and adding new code editor fields to the GUI is a bit of a PITA.

[AlexK98]

The features in a row are all separate and you can't reference sibling feature values.

So sad. Maybe you can think of it for the future enhancements? :) It would greatly improve and extend the usability of your addon.
Same for the templatable fields - having GUI elements significantly simplifies the discovery that the possibility exists without reading through lots of text and thus simplifies the life of users.

Anyway, thanks for the work and help!