Template integration

[derbadewaschl]

Hi,

The new 2.0.0 version says you can use "the Template Integration to create a sensor that shows the start time:".
I can't get it running. I copy/pasted the code from the README into a new helper in Settings/Devices/Helpers, only updating the trigger time to a time 2 minutes from now. Then I waited 3 minutes. But when I click the helper it says "Unavailable".

Also, it is not clear to me how to use it in an automation. Can I trigger on sensor "Start Appliance"? How?

Any help would be very much appreciated.

I use ha 2023.9.2

Regards

derbadewaschl

[mr-p666]

Hej,
I'm still new to HASS, but I don't think it's able to implement a template sensor as a helper like you'd like.
I implemented it directly into my configuration.yaml file and used a second trigger when starting HASS:

template:
  - trigger:
      - platform: time
        at: "00:00:00"
      - platform: homeassistant
        event: start
    action:
      - service: epex_spot.get_lowest_price_interval
        data:
          earliest_start: "00:00:00"
          latest_end: "23:59:59"
          duration:
            hours: 3
        response_variable: resp
    sensor:
      - name: "EPEX Start 24h Low Period"
        device_class: timestamp
        state: "{{ resp.start is defined and resp.start }}"

Afterwards you can use the sensor.epex_start_24h_low_period as a time triggered sensor in your automations.

[mampfes]

Please check the main branch. You can now set an offset to get the lowest/highest price interval for e.g. tomorrow.

Please let me know if this fixes your problem. I would like to wait before I release it until I receive your feedback.

[derbadewaschl]

Hi,

Thank you so much.
Here's what I configured now:

template:
  - trigger:
      - platform: time
        at: "21:30:00"
      - platform: homeassistant
        event: start
    action:
      - service: epex_spot.get_lowest_price_interval
        data:
          duration: "02:00"
          earliest_start: "22:00:00"
          latest_end: "15:00:00"
          latest_end_post: 1
        response_variable: resp
    sensor:
      - name: "EPEX Start 24h Low Period"
        device_class: timestamp
        state: "{{ resp.start is defined and resp.start }}"

Rationale: I am using this to keep the house at 10°C while I am away. Sometimes (not often, though) the cheapest period is at 22:00, I don't want to miss that. But I wouldn't want the heating to turn on at 22:00 and then again at 2:00 and then not at all until 22:00 the next day.

I'll test this for the next couple of days and will let you know how it went.

If you are open to suggestions to make the configuration easier, here is a proposal, how to configure the same thing as above:

          duration: "02:00"
          within: "17:00"

[mampfes]

@derbadewaschl If I understand your proposal correctly, then there is one major difference to the current solution: In your proposal, you have to call the service at the right time. Otherwise you will get a different result. That also means that you can't call the service upfront - which might be acceptable, but this depends on your setup.
Therefore I implemented the solution with the absolute timestamps. They are (to a certain extend) independent of the time the service is called.

[mr-p666]

I updated to the main branch (HASS is also up to date) and tried the following service call:

- trigger:
    - platform: time
      at: "20:30:00"
    - platform: homeassistant
      event: start
  action:
    - service: epex_spot.get_lowest_price_interval
      data:
        earliest_start: "06:00:00"
        earliest_start_post: 1
        latest_end: "22:00:00"
        latest_end_post: 1
        duration:
          hours: 3
      response_variable: resp
  sensor:
    - name: "EPEX Start Daytime Low Period"
      device_class: timestamp
      state: "{{ resp.start is defined and resp.start }}"

But it doesn't work. I found the following In the logfile:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 89, in _handle_triggered
    script_result = await self._script.async_run(run_variables, context)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1578, in async_run
    return await asyncio.shield(run.async_run())
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 420, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 470, in _async_step
    self._handle_exception(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 493, in _handle_exception
    raise exception
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 704, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 666, in _async_run_long_action
    return long_task.result()
           ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2012, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2049, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/epex_spot/__init__.py", line 113, in get_lowest_price_interval
    return _find_extreme_price_interval(call, lambda a, b: a < b)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/epex_spot/__init__.py", line 149, in _find_extreme_price_interval
    return coordinator.source.find_extreme_price_interval(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/epex_spot/SourceShell.py", line 144, in find_extreme_price_interval
    start_times = get_start_times(
                  ^^^^^^^^^^^^^^^^
  File "/config/custom_components/epex_spot/extreme_price_interval.py", line 145, in get_start_times
    raise ValueError("latest_end is earlier or equal than earliest_start")
ValueError: latest_end is earlier or equal than earliest_start

Would be great if someone could help me with this. 😄

[mampfes]

Ah, this happens if you call the service before data for the next day is available.

Fixed in 2.1.0

[derbadewaschl]

@derbadewaschl If I understand your proposal correctly, then there is one major difference to the current solution: In your proposal, you have to call the service at the right time. Otherwise you will get a different result. That also means that you can't call the service upfront - which might be acceptable, but this depends on your setup. Therefore I implemented the solution with the absolute timestamps. They are (to a certain extend) independent of the time the service is called.

I was not aware that there is a use case, which is independent of the time when you call it, as I am using it with the code that you provided in this thread. What's the alternative?

So far the new implementation (commit a6603eb) is working fine. Thanks again.