Just pushed an update to github which should fix this issue.
HI @rogro82
would you care to make this card ‘trackable’ by the custom_component updater card please? https://github.com/custom-cards/tracker-card
would make updating you CC so much more comfortable .
thanks for considering
2 Likes
could it be that the restore state functionality of the Variable component is somehow compromised lately?
On each restart my variables lose their history, while I have enabled restore:
variable:
solar_angle_outside_light:
value: 'Not set'
restore: true
attributes:
icon: mdi:format-rotate-90
name: 'Solar angle'
virtual_light_outside_light:
value: 'Not set'
restore: true
attributes:
icon: mdi:brightness-5
name: 'Virtual light'
I did move from the default recorder to MariaDB lately but still have variable included in the domains in recorder,yaml. HA 84.3
Do you use the latest version of hass-variables? This issue has been fixed already - see https://github.com/rogro82/hass-variables/issues/11 .
yes I have dl’d that version, and think (…) it worked al right.
Unfortunately this component hasn’t got a version number in the file, and can’t be tracked by the updater card, but I’ve secured it manually
Is there a way to pass multiple values to this? For example, if I wanted to use the attributes (I use the motion example, works fine and I understand it’s “rolling” the values forward, so to speak) to hold device_tracker information? I’m not really clear on how I can do this with attribute template with perhaps value template? IE:
attributes_template: >
{
"latitude": "{{ ??? }}",
"longitude": "{{ ??? }}"
}
Not sure how to populate this using states.attributes.device_tracker.attributes.latitude/longitude (for example.)
EDIT: Solved it. Now to make it more template-ish as I do passing entity-id to the python script.
chris_gps:
value: 'Unknown'
restore: false
attributes:
latitude: 0
longitude: 0
trigger:
- platform: state
entity_id: device_tracker.homeassistant_chris
action:
- service: python_script.calc_gps_coords
data_template:
entity_id: '{{ trigger.entity_id }}'
zone_entity: 'None'
zone_data: 'None'
- service: variable.set_variable
data:
variable: chris_gps
attributes_template: >
{
"latitude": "{{ states.device_tracker.homeassistant_chris.attributes.latitude }}",
"longitude": "{{ states.device_tracker.homeassistant_chris.attributes.longitude }}"
}
1 Like
@rogro82 is it possible to manipulate variables from python script? I keep running into a roadblock (which I’ve googled around) that at first was due to using direct assignment, ie:
foo = foo # object does not support item or slice assignment
foo += foo
Which I thought I solved but now I’m running into an issue trying to use hass.states.set() which produces this error:
Line 72: Augmented assignment of object items and slices is not allowed.
Hi,
Just wanted to share that I used this to track my daily rainfall. Since my oregon scientific pcr800 rain gauge only track cumulative rain from last reset as a standard. Perhaps it of use for someone else. replace “sensor.rain_total” with your own cumulative rain sensor.
configuration.yaml
- platform: template
sensors:
rain_daily:
value_template: ‘{%- if not (is_state(“sensor.rain_total”,“unknown”) or is_state(“variable.rain_cum_prior”,“unknown”) )-%} {{ ((states.sensor.rain_total.state | float) - (states.variable.rain_cum_prior.state | float)) | max (0) | round(1) }} {%- endif -%}’
friendly_name: ‘Rain Today’
unit_of_measurement: ‘mm’variable:
rain_cum_prior:
value: ‘unknown’
rain_daily_autmation.yaml
alias: ‘record cumulative rain to midnight’
trigger:
- platform: time
at: “00:00:01”
action:
- service: variable.set_variable
data:
variable: rain_cum_prior
value_template: ‘{{states.sensor.rain_total.state}}’
1 Like
This script adds 1 to the variable corresponding to the minute, and then check if it is equal to 60, if true assign zero the variable.
This work for me.
xxx_sc_exalarmeduplo2_alarm1_on_minute_schedule:
sequence:
- service: variable.set_variable
data:
variable: xxx_vb_exalarmeduplo2_alarm1_on_minute_schedule
value_template: "{{ (variable.state | int) + 1 }}"
- service: persistent_notification.create
data_template:
message: "{{ states.variable.xxx_vb_exalarmeduplo2_alarm1_on_minute_schedule.state }}"
title: "Minute test"
- condition: state
entity_id: variable.xxx_vb_exalarmeduplo2_alarm1_on_minute_schedule
state: '60'
- service: variable.set_variable
data:
variable: xxx_vb_exalarmeduplo2_alarm1_on_minute_schedule
value_template: "0"I am restructuring my configuration to make it more manageable and run into this issue with variables:
When I put variables directly below the variable: line, properly indented and all, it works fine.
But what I want to do is:
variable: !include_dir_list ../variables
And then have separate files for each variable in the mentioned directory, for example, in …/variables sits a file named house_state.yaml with these contents:
house_state:
value: 'Unknown'
restore: true
attributes:
icon: mdi:home-heart
name: 'House status'
The error I see in the build log is then:
Testing configuration at /builds/[redacted]/hass-config/.
Failed config
homeassistant.packages.variable.variable:
- Package variable setup failed. Component variable cannot be merged. Expected a dict.
- variable: ?
- house_state: [source /builds/[redacted]/hass-config/./components/packages/../variables/house_state.yaml:4]
attributes: [source /builds/[redacted]/hass-config/./components/packages/../variables/house_state.yaml:7]
icon: mdi:home-heart
name: Huis status
restore: True
value: Unknown
Not sure what that error means? Does the variable component not support the !include directives, or am I missing something here?
Using packages with variable here too. No dash in front of variable.
##########################################################################################
# Variables
##########################################################################################
variable:
solar_angle_outside_light:
value: 'Not set'
restore: true
attributes:
icon: mdi:format-rotate-90
name: 'Solar angle'
using
homeasistant:
packages: !include_dir_named packages
Thanks, but that is not what I am trying to do. I want to use an !include directive with the variables itself, not the packages
You might review the different alternative include mechanisms here https://www.home-assistant.io/docs/configuration/splitting_configuration#advanced-usage if you’ve not seen it.
The include mechanisms are generic in the YAML parsing, not specific to any component.
So maybe you could use incude_dir_merge_named ../variables with the way you have each individual file constructed per your example?
1 Like
That’s what I thought, and I am familiar with the directives but I must have been looking at it for too long that I did not see the wrong include I tried (copy/paste from another file in my config). Thanks for pointing it out and making my look twice (more actually) 
Has anyone gotten this working with 0.89.1?
I’m getting the following error:
Traceback (most recent call last):
File “/usr/src/app/homeassistant/setup.py”, line 154, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
AttributeError: module ‘custom_components.variable’ has no attribute ‘setup’
I’ve moved the variable.py into custom_components/variable/variable.py and also created an empty init.py
Works for me in custom_components/variable.py.
No need for this, because this is no modified core component.
Ah, thanks for this. I must have misunderstood, and thought this was ultimately going to be required for all custom components.
since ha 92.0 I get this error
Unable to find services.yaml for the variable integration
I think is related to this https://github.com/home-assistant/home-assistant/issues/23197
It’s just a warning.
Create an empty services.yaml in your custom_components folder and it’s gone.
2 Likes
don’t we need a manifest.json, and/or init.py from HA 92.2 upwards? Asking because being at the verge of upgrading my systemHub instance…