Multiple input numbers entities with a min-max in common

[andrex (Andrea)]

I need to create about 15 input number entities that will act as set point to our eating system (I need to send those values via MQTT.
Is it possible to use a unique set of min-max-step values?
How can I send to MQTT those value as soon as they change?
Thanks!

[123 (Taras)]

min, max, and step options are specific to each Input Number you create.

If you want to create fifteen Input Number entities with the same values for min, max, and step then I suggest you configure them in YAML, as opposed to the UI, because you can easily duplicate (via copy-paste) one Input Number’s configuration fifteen times.

You can publish an Input Number’s value, to an MQTT topic, using an automation with a State Trigger. It will publish the value the moment it changes.

alias: example
trigger:
  - platform: state
    entity_id:
      - input_number.one
      - input_number.two
      - input_number.etc
    to:
condition: []
action:
  - service: mqtt.publish
    data:
      topic: your/topic/goes/here
      payload: "{{ trigger.to_state.state }}"

[andrex (Andrea)]

Yes, I was gonna do that in config files, I prefer that way, I feel to have more control.
Your code throw me the error Integration error: action - Integration ‘action’ not found
It could be an indentation error, but I’m just starting with this and I really can’t see the problem.

What if I want those values to also change based on a MQTT values?

Thanks a lot!

[123 (Taras)]

Do you have the MQTT integration installed and configured to connect to your MQTT broker?

[andrex (Andrea)]

I do and I’m already using it.

[123 (Taras)]

Then I’m not sure why the automation produced this error:

Integration error: action - Integration ‘action’ not found

I entered the automation’s code on my system and it saved it without producing an error.

Post your automation’s code.

[andrex (Andrea)]

Here it is:

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

#automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
#input_number: !include_dir_merge_list input_numbers  
input_number:
  setpoint_amministrazione:
    name: "Setpoint amministrazione"
    initial: 24
    min: 24
    max: 28
    step: 0.5


alias: example
trigger:
  - platform: state
    entity_id:
      - setpoint_amministrazione
    to:
condition: []
action:
  - service: mqtt.publish
    data:
      topic: office/setpoints/amministrazione
      payload: "{{ trigger.to_state.state }}"

mqtt:
#    light: !include_dir_merge_list lights/  #!include lights.yaml
#    cover: !include cover.yaml
    switch: !include switch.yaml
#    button: !include buttons.yaml
    sensor: !include_dir_merge_list sensors

[123 (Taras)]

OK, now the mistake is visible. You can’t simply drop an automation into configuration.yaml like that.

You should uncomment this line:

#automation: !include automations.yaml

For organization purposes, it’s best to store automations in a separate file.

I suggest you remove your automation, restart Home Assistant, then use the visual Automation Editor to create the automation.

When you’re in the Automation Editor, creating a new automation, switch the Editor into YAML mode, delete whatever you see displayed, then copy-paste the example into the Editor. click the Save button and it should save it without any errors.

[andrex (Andrea)]

Mmm…I will do, but why?

[123 (Taras)]

@andrex

I now see in the notification this error

With all due respect, it’s becoming apparent to me that you are a beginner because you are making fundamental errors while attempting to compose a basic automation. That’s why I recommend you use the Automation Editor. In visual mode, it guides you to avoid making basic errors. For example, this is an invalid entity_id

  - platform: state
    entity_id:
      - setpoint_amministrazione

@andrex

The automation “Set temp slider” (automation.set_temp_slider) has an action that calls an unknown service: setpoint_amministrazione.set_value.

I have not seen the code for automation.set_temp_slider but I know for a fact that there’s no such service call as setpoint_amministrazione.set_value. The correct name is input_number.set_value. Once again, the Automation Editor, in visual mode, would have helped you avoid making that mistake.

[andrex (Andrea)]

I’m definitely a beginner, sorry for not have pointed that out in the beginning.
About the second error, I’ve just realized that was an old one (I’ve removed it from my post i guess just as you were posting your reply, sorry).

[andrex (Andrea)]

I got the error: I didn’t realize that your code was an automation.
I’ve put it under the automation and doesn’t throw any error now.
Thanks!

automation:
    alias: example
    trigger:
      - platform: state
        entity_id:
          - setpoint_amministrazione
        to:
    condition: []
    action:
      - service: mqtt.publish
        data:
          topic: office/setpoints/amministrazione
          payload: "{{ trigger.to_state.state }}"

[123 (Taras)]

No problem. Just follow my instructions posted here. You want your system to store automations in a separate file (automations.yaml). When you create automations with the Automation Editor, they will be automatically stored in that file.

• Use the Automation Editor in visual mode to help avoid making basic errors whe creating modifying automations.

• Use the Automation Editor in YAML mode for copy-pasting examples from the forum or when you become more familiar with the correct syntax for entities, service calls, Home Assistant’s scripting, etc.

[123 (Taras)]

The latest example you posted still has the wrong entity_id (it should be input_number.setpoint_amministrazione). You are also still saving the automation in configuration.yaml which isn’t the best long-term strategy for organization.

[andrex (Andrea)]

@123

input_number.setpoint_amministrazione

Thanks a lot, it works!!!

I use to put everything in the configuration.yaml file at first and then, when everything works, I move the code in the different files (as I just did!).
This because sometimes I use wrong indentation or…I don’t know what else and the code works in configuration.yaml but not in the single files, so first I solve the code errors (if there are) and then I move the code.
I guess that I can start writing the code directly in separate files!

Now…if you still have a bit of patience: how can I change that value from MQTT?

[123 (Taras)]

@andrex

I use to put everything in the configuration.yaml file at first and then, when everything works, I move the code in the different files (as I just did!).
This because sometimes I use wrong indentation or…I don’t know what else and the code works in configuration.yaml but not in the single files, so first I solve the code errors (if there are) and then I move the code.

That’s a time-consuming way to compose error-free automations.

If you compose your automations in the Automation Editor, it will help you avoid making errors. Any errors you do make will be reported the moment you attempt to save the file. After you have saved it, you can switch the Editor to YAML mode and see the error-free YAML that was produced (a faster, better way for you to learn correct YAML syntax).

[andrex (Andrea)]

I know, but I had problems everywhere, not only in the automation! Buuuut I think that I will use the automation editor (I didn’t know it existed before you told me ), it surely help!

[123 (Taras)]

@andrex

didn’t know it existed before you told me

Automation editor

[andrex (Andrea)]

@123

If you want to create fifteen Input Number entities with the same values for min, max, and step then I suggest you configure them in YAML, as opposed to the UI, because you can easily duplicate (via copy-paste) one Input Number’s configuration fifteen times.

Is it possible to use a variable for min and max of all the setpoints?

[123 (Taras)]

I don’t see anything in Input Number’s documentation indicating that’s possible.

If the YAML configuration of your 15 Input Numbers contains a lot of duplication, you can use the YAML feature called ‘Anchors and Aliases’ to minimize duplication. Here’s an example of its use for reducing the configuration of multiple light entities:

Way to create multiple sensors per device with template?

Here’s how I use it. The following is a portion of my lights.yaml file. The configuration of the first light includes the definition of a node anchor called dimmer. All subsequent light configurations refer to the dimmer anchor. - name: "Foyer" state_topic: "premise/foyerlight/powerstate" command_topic: "premise/command/foyerlight/powerstate" brightness_state_topic: "premise/foyerlight/brightness" brightness_command_topic: "premise/command/foyerlight/brightness" <<: &dimm…