Home Assistant packages

[Madcat71]

Hi, this is more a general question buti think you guys can help.
I need to add another package in the configuration.yaml

currently it looks lik this and integrates the integration folder for the Modbus Sungrow file
but i want to add the "cheapest_hours: !include advanced_cheapest_hours.yaml" but what ever i try i get errors of all kinds, yes i am a noob at Home Assistant yaml files. tryed google but dont get me anywhere so i will ask here :D

So how is the syntax supossed to be when i want to add multiple packages, hope you understand what i am trying to do :D

works fine
homeassistant:
packages: !include_dir_named integrations

" dosent work, tryed many variants but only get errors when i check the yaml in HA
packages:
!include_dir_named integrations
cheapest_hours: !include advanced_cheapest_hours.yaml

[Caroche81]

Hi everyone, I've been having the same problem since today. Is there a solution?

[Gnarfoz]

The problem described by @Madcat71 is not something that just happens "since today". They were trying to add something intentionally. So you either have a different problem or you could try and describe your problem in a bit more detail.

[Gnarfoz]

@Madcat71 not sure if this is even still relevant, but you would simply drop your additional advanced_cheapest_hours.yaml file into the same integrations directory as the modbus_sungrow.yaml file.
Because of !include_dir_named, every file in that directory gets included under its own key below homeassistant.package, with the filename (without the yaml extension) as the name.

Meaning:

homeassistant:
  packages: !include_dir_named integrations

is interpreted as:

homeassistant:
  packages:
    modbus_sungrow:
      modbus:
        - modbus sensor 1
        - modbus sensor 2
        - ...
      sensor:
        - xyz
        - ...
      <the rest of the content of modbus_sungrow.yaml>
    cheapest_hours:
      <whatever is in that file>

Refer to https://www.home-assistant.io/docs/configuration/packages/ and https://www.home-assistant.io/docs/configuration/splitting_configuration#example-include_dir_named for further details.

[Caroche81]

Hey Gnarfoz,

thanks for your message. That was the solution. Now everything is working as intended. I've always tried creating a new command under Package. But as you described, the include_dir_named integrations already references the integration. :-)

[Gnarfoz]

Excellent! 👍🏻

[TCzerny]

Can you share the advanced_cheapest_hours.yaml content ?

There are multiple ways to include them, but it depends on the content structure.

[Madcat71]

do you mean my file?
havent used it for a long time, i made some automations that reads the price and then control stuff like stop sellling electricity i price i below X, that works great for what i use it for.

but if you want the file let my know :)

[TCzerny]

Yes. I mean the file you mentioned above.

[Madcat71]

The file you wanted

# Package to create and handle cheapest hours from nord pool integration!
# This is the SINGLE entry version.
# For more details check out the blog post at https://www.creatingsmarthome.com/?p=1620

template:
  - sensor:
      # The actual cheapest hour sensor. If multiple entries are required, copy and set unique_id and configure attributes. sensor.nordpool_old
      - name: "Cheapest hours energy"
        unique_id: cheapest_hours_energy
        device_class: timestamp
        state: >
          {%- set sensor = (this.attributes.get('sensor', 'sensor.nordpool_old') | string) -%} 
          {%- set numberOfSequentialHours = (this.attributes.get('number_of_sequential_hours',1) | int) -%}
          {%- set lastHour = (this.attributes.get('last_hour',23) | int) -%}
          {%- set firstHour = (this.attributes.get('first_hour', 0) | int) -%}
          {%- set startingToday = (this.attributes.get('starting_today', false) | bool) -%}
          {%- if state_attr(sensor, 'tomorrow_valid') == true -%}
            {%- set arr = state_attr(sensor, 'today') + state_attr(sensor, 'tomorrow') -%}
            {%- set ns = namespace(counter=0, list=[], cheapestHour=today_at("00:00"), cheapestPrice=999.00) -%}
            {%- if startingToday == true -%}
              {%- set ns.starting = firstHour -%}
            {%- else -%}
              {%- set ns.starting = firstHour + 24 -%}
            {%- endif -%}
              {%- set ns.ending = lastHour + 24 -%}
            {%- for i in range(ns.starting + numberOfSequentialHours, ns.ending+1) -%}
              {%- set ns.counter = 0.0 -%}
              {%- for j in range(i-numberOfSequentialHours, i) -%}
                {%- set ns.counter = ns.counter + arr[j] -%}
              {%- endfor -%}
              {%- set ns.list = ns.list + [ns.counter] -%}
              {%- if ns.counter < ns.cheapestPrice -%}
                {%- set ns.cheapestPrice = ns.counter -%}
                {%- set ns.cheapestHour = today_at("00:00") + timedelta( hours = (i - numberOfSequentialHours)) -%}
              {%- endif -%}
            {%- endfor -%}
            {{ ns.cheapestHour }}
            {%- set ns.cheapestPrice = ns.cheapestPrice / numberOfSequentialHours -%}
          {%- endif -%}
        attributes:
          # CHANGE-ME: Set your personal configurations in here
          number_of_sequential_hours: 4 # Amount of sequantial cheapest hours in search
          first_hour: 20 # Search starting hour
          last_hour: 06 # Search ending hour
          starting_today: true # Is the first_hour today (true / false). If false, first_hour needs to be before last_hour.
          sensor: sensor.nordpool_old # Nord pool sensor id. Check it ouf from your integrations page!
          fail_safe_starting: "00:00" # If nordpool fetch fails, starting time to make the calendar entry

automation:
  # Automation to trigger when calendar event hits the cheapest hour mark
  # start/stop automation
  - id: "cheapest_hours_calendar_entry"
    alias: "Cheapest hours: Calendar trigger"
    description: ""
    trigger:
      - platform: calendar
        event: start
        entity_id: calendar.electricity
      - platform: calendar
        event: end
        entity_id: calendar.electricity
    condition:
      - condition: template
        value_template: >
          {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
          {{ (state_attr(sensorId, 'friendly_name') | string) in trigger.calendar_event.summary }}
    action:
      - if:
          - condition: template
            value_template: "{{ trigger.event == 'start' }}"
        then:
          # CHANGE-ME: Actions to do when cheapest hours starts
          - service: VVB.turn_on
            entity_id: switch.vvb_on_off
        else:
          # CHANGE-ME: Actions to do when cheapest hours ends
          - service: VVB.Turn_Off
            entity_id: switch.vvb_on_off
    mode: single

  # -- GLOBAL CONFIGURATIONS BELOW, NO NEED TO CHANGE UNLESS CREATING MULTIPLE SEQUENCES --
  # Create calendar event
  - id: "cheapest_hours_set_sequence"
    alias: "Cheapest hours: Set next cheapest sequence"
    description: "Checks tomorrow energy prices every hour and create calendar entry when available AND events not yet created"
    trigger:
      - platform: time_pattern
        hours: /1
    condition:
      - condition: template
        # from which sensor we should try the tomorrow price validation
        value_template: >
          {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
          {{ state_attr((state_attr(sensorId, 'sensor') | string), 'tomorrow_valid') == true }}
      - condition: state
        entity_id: input_boolean.cheapest_hours_set
        state: "off"
    action:
      - service: input_boolean.turn_on
        data: {}
        target:
          entity_id: input_boolean.cheapest_hours_set
      # Event creation
      - service: calendar.create_event
        data:
          start_date_time: >
            {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
            {{ as_timestamp(states(sensorId), 0) | timestamp_local }}
          end_date_time: >
            {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
            {{ (as_timestamp(states(sensorId), 0) + (3600 * state_attr(sensorId, 'number_of_sequential_hours') | float)) | timestamp_local }}
          summary: >
            {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
            {{ state_attr(sensorId, 'friendly_name') | string }}
        target:
          entity_id: calendar.electricity
    # If multiple cheapest hours sequences are required, copy 'calendar.create_event' block from aboce and change the 'sensorId' variabes values to match corresponding new cheapest hours templated sensor
    mode: single

  # Failsafe
  - id: "cheapest_hours_failsafe"
    alias: "Cheapest hours: Failsafe"
    description: "Failsafe: Set cheapest hours from fail_safe value to amount of hours"
    trigger:
      - platform: time
        at: "23:15"
    condition:
      - condition: state
        entity_id: input_boolean.cheapest_hours_set
        state: "off"
    action:
      - service: input_boolean.turn_on
        data: {}
        target:
          entity_id: input_boolean.cheapest_hours_set
      # Failsafe action
      - service: calendar.create_event
        data:
          start_date_time: >
            {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
            {{ as_timestamp(today_at(state_attr(sensorId, 'fail_safe_starting')) + timedelta( hours = 24 ), 0) | timestamp_local }}
          end_date_time: >
            {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
            {{ (as_timestamp(today_at(state_attr(sensorId, 'fail_safe_starting')) + timedelta( hours = 24 ), 0) + (3600 * state_attr(sensorId, 'number_of_sequential_hours') | float)) | timestamp_local }}
          summary: >
            {%- set sensorId = 'sensor.cheapest_hours_energy' -%}
            {{ state_attr(sensorId, 'friendly_name') | string }}
        target:
          entity_id: calendar.electricity
    # If multiple cheapest hours sequences are required, make a copy of 'calendar.create_event' block above and set the 'sensorId' values to match the new one
    mode: single

  # input_boolean reset
  - id: "cheapest_hours_clear_set_flag"
    alias: "Cheapest hours: Reset the set helper for the next day"
    description: "Clears cheapes hours helper boolean when the day changes."
    trigger:
      - platform: time
        at: "01:15:00"
    condition: []
    action:
      - service: input_boolean.turn_off
        data: {}
        target:
          entity_id: input_boolean.cheapest_hours_set
    mode: single

# We need a helper to know if the calendar mark(s) has already been set!
input_boolean:
  cheapest_hours_set:
    name: Cheapest hours set for the next day
    icon: mdi:clock