Set variables, custom component variables

[a00tomsv (Tomas)]

I am using the custom compenent varaiables
https://github.com/rogro82/hass-variables

I would like to use a variable and set it to the value of an input_number, but got stuck.

configuration.yaml

    variable:
      hour_calc:
        value: 0
        restore: true
      min_calc:
        value: 0
        restore: true

automations.yaml

- alias: slider_start_time
  hide_entity: false
  trigger:
    platform: state
    entity_id: input_number.start_hour
  action:
    - service: variable.set_variable:
      data:
        variable: hour_calc
        value: input_number.start_hour

This does not work:
Configuration invalid
Error loading /home/homeassistant/.homeassistant/configuration.yaml: mapping values are not allowed here
in “/home/homeassistant/.homeassistant/automations.yaml”, line 75, column 37

I have tried to understand the value_template and data_template but still no luck … Anyone that knows how to store an input: number into another variable

Next question is how to set a variable as the value of itself multiplied with 3600.

action:
    - service: variable.set_variable:
      data:
        variable: hour_calc
        value: hour_calc * 3600

[VDRainer]

@a00tomsv

• service: variable.set_variable:

Remove the colon at the end of the service call.

@a00tomsv

how to set a variable as the value of itself multiplied with 3600

There are examples on github

rogro82/hass-variables/blob/master/examples/counter.yaml

[a00tomsv (Tomas)]

Thank you, easy one that I missed the “:” =)

Still have no luck in setting the variable even with the example. Tried this one:

- alias: slider_start_time
  hide_entity: false
  trigger:
    platform: state
    entity_id: input_number.start_hour
  action:
    - service: variable.set_variable
      data:
        variable: hour_calc
        value_template: '{{ (variable.state = input_number.start_hour | int) }}'

With this error message:
2018-07-07 14:00:58 ERROR (MainThread) [homeassistant.core] Invalid service data for variable.set_variable: invalid template (TemplateSyntaxError: expected token ‘)’, got ‘=’) for dictionary value @ data[‘value_template’]. Got ‘{{ ((variable.state | int) = (input_number.start_hour | int)) }}’

[pnbruckner (Phil)]

value_template: "{{ states('input_number.start_hour') | int }}"

[a00tomsv (Tomas)]

@pnbruckner

value_template: “{{ states(‘input_number.start_hour’) | int }}”

Thank you so much!

[a00tomsv (Tomas)]

I have yet another question. I am trying to set an input_datetime time attribute to a value of a variable, but I cannot succeed. This is my last try:

- alias: slider_start_time
  hide_entity: false
  trigger:
    platform: state
    entity_id: input_number.start_hour
  action:
    - service: variable.set_variable
      data:
        variable: hour_calc
        value_template: "{{ states('input_number.start_hour') | int  * 3600 }}"
    - service: input_datetime.set_datetime
      data_template:
        entity_id: input_datetime.start_time
        date: '{{ (as_timestamp(now()) | timestamp_custom("%Y-%m-%d", true)) }}'
        time: timestamp.variable.hour_calc

And this is the error message from the log:
2018-07-08 22:24:42 ERROR (MainThread) [homeassistant.core] Invalid service data for input_datetime.set_datetime: Invalid time specified: timestamp.variable.hour_calc for dictionary value @ data[‘time’]. Got ‘timestamp.variable.hour_calc’

Any suggestions?

[pnbruckner (Phil)]

        date: "{{ now().date() }}"
        time: "{{ states('variable.hour_calc')|int|timestamp_custom('%H:%M:%S',False) }}"

I don’t know if you’re using variable.hour_calc elsewhere. But if not, then you could do this:

        date: "{{ now().date() }}"
        time: "{{ (states('input_number.start_hour')|int*3600)|timestamp_custom('%H:%M:%S',False) }}"

Or even:

        date: "{{ now().date() }}"
        time: "{{ states('input_number.start_hour') }}:00:00"

[a00tomsv (Tomas)]

Great, thanks again!

[scstraus]

Hi all… I’m having a bit of a problem setting these variables. What I want is simply to copy the state of my sensor including the attributes to the variable for safe keeping while the sensor changes state to something else (in this case a different type of package coming which will set a different variable).

I can’t get it to set the variable at all right now and I’m not sure why. I’ve used very similar triggers and conditions before, so I think I’m doing something wrong in the syntax to set the variable. Any ideas?

- id: posta_state_change
  alias: 'Posta state change'
  trigger:
    platform: state
    entity_id: sensor.cp_packages_coming_today
  condition:
    condition: or
    conditions:
      - condition: state
        entity_id: 'sensor.cp_packages_coming_today'
        state: 'delivery'
      - condition: state
        entity_id: 'sensor.cp_packages_coming_today'
        state: 'no_delivery'
  action:
    service: variable.set_variable
    data:
      variable: posta_variable
      value_template: "{{ states('sensor.cp_packages_coming_today')}}"
      attributes_template: >
        {
          "from": "{{ state_attr('sensor.cp_packages_coming_today', 'from') }}",
          "date": "{{ state_attr('sensor.cp_packages_coming_today', 'date') }}",
          "subject": "{{ state_attr('sensor.cp_packages_coming_today', 'subject') }}",
          "body": "{{ state_attr('sensor.cp_packages_coming_today', 'body') }}"
        } 

One more thing is that the icon isn’t setting correctly. icon: appears as an attribute but the actual icon doesn’t change.

variable:
  posta_variable:
    attributes:
      icon: mdi:delivery
      friendly_name: 'Posta'
      from: ''
      subject: ''
      body: ''
      date: ''
    restore: true

[MichaelJ2600 (Mik)]

Hello scstraus

Did you ever solve this ? I have excatly the same issue. It doesn’t pupulate the attribute part.

If I comment out the attribute part, I can set the variable value, without problem.
It doesnt throw any errors in the logs.

/Michael

[scstraus]

No, unfortunately not. I’ve run out of ideas. I feel like it should work one of the ways I’ve tried but it simply doesn’t.

[Pirol62 (Jörg Nauen)]

Have you tried to delete the icon attribute?
Maybe this causes errors
I always set the icon and friendly_name via customize.yaml
That works well

[snarkysnark]

If you all are still having trouble with that variable component, you might want to check mine out to see if it suits your needs.

snarky-snark/home-assistant-variables

It doesn’t support an attributes dictionary, but it’s easy enough to just create a variable for each attribute. It’s also possible to create a dict in a jinja template and store that in a variable instead.

[MichaelJ2600 (Mik)]

Hello Snarkysnark

This worked like a charm ! Thanks.

Michael

[RickTSD (Rick de Jong)]

Allright. I hope this reply is in the right topic. If not, I’m sorry.

I wonder if the following is possible within HA, because it would make things a lot easier. Lets say:

@ 6AM I want my bedroo lights to turn on @ brightness 5 and every 3 minutes I want them to get 5+ brightness. What I do now is enter a wait of 00:03 and add a new brightless lever. Bit can this be done easier?

The same is for example my sonos
If I want the sonos to start playing at volume 0.02 @ 6.10 and get 0.01 louder every 5 minutes, I now have to add a wait / etc. Isn’t it pissible to add some kind of tempate to add X per X minutes?

[PolarLava]

I’m not at home right now so I can’t look into further at the moment. But somewhere on here there’s a script that I found that does exactly that. You tell it the start time, how long of a ramp you want and from what level to start and finish. It does ramp down as well. I use for my wife and I everyday. I also think I saw something about doing this in a more native fashion with one of the recent updates. But what I have works so I didn’t pursue it.

[AndyH80]

Hey, I tried no all kinds of options to save a variable and get it out but nothing is working not the snarky one there I manage to get variables in but I can’t use them in code. input number I just not get it I cant set a sensor value and store ist there. and then there are the Hass variables the same thing it’s a nightmare.
I just want to store a sensor value and subtract it the next day to get the difference why is that so difficult.
Example: I have a sensor with a value of 50 today tomorrow it is 53 maybe and I want to preserve the 50 and subtract the 50 from the 53 to get the difference.
it really can’t be that hard but I get it with no variable solution to work.

anyone can help me I just don’t understand the examples of why I make a query and have events if I just want the var.x back and why can’t I just use x.var and that’s it?

[guidokanschat]

I think this topic is outdated. using entities of type input_boolean etc. solved the issue for me

[lonebaggie]

will this help ?

Using Input Select as an Array (Global variables) in Automations

Not sure if this has been documented anywhere, but I have been using Input select as Global variables lists (Arrays) in Automations. Take the following input Select Array: name : Array Test options: - Option A - Option B - Option C - Option D You can convert this to a list in JInga2 with the following {% set arraytest = state_attr("input_select.array","options") %} You can extract an array element by using `{% set obj = arraytest[1] %}` {{obj}} This will r…

[finity]

@guidokanschat

I think this topic is outdated.

Not outdated at all.

I’m on v116.2 and hass-variables are still working fine for me.