Intelligent Slots Displayed

[liquidv]

Hello, is there anyway to show the Intelligent slot hours on HA like this but using this integration rather than using Megakids Intelligent integration? I'm running both at the moment and it's a bit fiddly as I want both gas tracker price from this integration, and OI slot hours from the other one.

Megakids intelligent integration appears to go to an unknown state a bit too often, whereas this integration appears more stable hence I want to stick with this one only.

[Dave-Parry]

I also am interested in displaying the slots on my dashboard, but no idea how to access the data

[BottlecapDave]

Hi, sorry for the late response. The same data is available as attributes on the binary_sensor.octopus_energy_intelligent_dispatching sensor. If you can supply a link to where you got the screenshot, I might be able to help.

[liquidv]

The code is here if you need it for the other Octopus Intelligent integration.

https://community.home-assistant.io/t/octopus-energy-intelligent-tariff/418680/123

[Dave-Parry]

Thanks for reply, but I'm on agile not intelligent Tariff so don't have that range of sensors

[liquidv]

Hi, sorry for the late response. The same data is available as attributes on the binary_sensor.octopus_energy_intelligent_dispatching sensor. If you can supply a link to where you got the screenshot, I might be able to help.

https://community.home-assistant.io/t/octopus-energy-intelligent-tariff/418680/123

{% if state_attr('binary_sensor.octopus_intelligent_slot', 'plannedDispatches') | length > 0 %}
{% for dispatch in state_attr('binary_sensor.octopus_intelligent_slot', 'plannedDispatches') -%}
⏰ {{ (dispatch.startDtUtc | as_datetime | as_local).strftime('%H:%M') }} to {{ (dispatch.endDtUtc | as_datetime | as_local).strftime('%H:%M') }}
{{ "\n" }}
{%- endfor %}
{%- else -%}
⏰ None
{%- endif %}

[BottlecapDave]

This can be adjusted to look at the sensor for this integration like so

{% if state_attr('binary_sensor.octopus_energy_intelligent_dispatching', 'planned_dispatches') | length > 0 %}
{% for dispatch in state_attr('binary_sensor.octopus_energy_intelligent_dispatching', 'planned_dispatches') -%}
⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }}
{{ "\n" }}
{%- endfor %}
{%- else -%}
⏰ None
{%- endif %}

[liquidv]

hmm doesn't seem to be working.....

[BottlecapDave]

I've updated the above example which should now work

[liquidv]

Brilliant it works, thank you!
Now I can uninstall the other Intelligent integration and just use your one. Cheers

[reedy]

I came here looking for the same thing, and putting the instructions together (I'll move it to one of the docs files when I've got it working)...

Install /~https://github.com/thomasloven/lovelace-template-entity-row

Add this to your card

  - type: custom:template-entity-row
    name: Planned slots
    secondary: >-
      {% if state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching', 'planned_dispatches') | length > 0 %}
        {% for dispatch in state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching', 'planned_dispatches') -%}
          ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }}
           {{ "" }}
        {%- endfor %}
      {%- else -%}
        ⏰ None
      {%- endif %}

replacing XXXXXXXX as appropriate...

Which is currently giving

The lack of newlines is a bit annoying, but a limitation of the card, seemingly - https://community.home-assistant.io/t/octopus-energy-intelligent-tariff/418680/108 / thomasloven/lovelace-template-entity-row#71 / thomasloven/lovelace-template-entity-row#84

Though later comments in the thread make it sound like it works for them...

I'd like to make the "off" disappear too... But that seems it's a different known bug, ala thomasloven/lovelace-template-entity-row#106

So setting state: '' fixes it. Also adding an icon to make it look a bit more consistent:

type: custom:template-entity-row
name: Planned slots
state: ''
icon: mdi:clock
secondary: >-
  {% if
  state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching',
  'planned_dispatches') | length > 0 %}
    {% for dispatch in state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching', 'planned_dispatches') -%}
      ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }}
      {{ "\n" }}
    {%- endfor %}
  {%- else -%}
    ⏰ None
  {%- endif %}

[BottlecapDave]

You can also use the built in markdown card, which might support new lines (I'm not on intelligent myself)

[reedy]

type: markdown
title: Planned slots
content: |-
  {% if
  state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching',
  'planned_dispatches') | length > 0 %}
    {% for dispatch in state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching', 'planned_dispatches') -%}
      ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }}
      {{ "\n" }}
    {%- endfor %}
  {%- else -%}
    ⏰ None
  {%- endif %}

gives

[reedy]

If we install /~https://github.com/thomasloven/lovelace-hui-element too...

  - type: custom:hui-element
    card_type: markdown
    title: Planned slots
    content: |-
      {% if
      state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching',
      'planned_dispatches') | length > 0 %}
        {% for dispatch in state_attr('binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching', 'planned_dispatches') -%}
          ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }}
          {{ "\n" }}
        {%- endfor %}
      {%- else -%}
        ⏰ None
      {%- endif %}

[neildsb]

awesome just what I was looking for, top job!!

[neildsb]

any ideas how to integrate an availability state on bootup to stop a log error?

like -
availability: "{{ (is_state('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching','off' )) or (is_state('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching','on' )) }}"

Error while processing template: Template<template=({% if state_attr('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching', 'planned_dispatches') | length > 0 %} {% for dispatch in state_attr('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching', 'planned_dispatches') -%} ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }} {{ "\n" }} {%- endfor %} {%- else -%} ⏰ None {%- endif %}) renders=2>
Error while processing template: Template<template=({% if state_attr('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching', 'planned_dispatches') | length > 0 %} {% for dispatch in state_attr('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching', 'planned_dispatches') -%} ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }} {{ "\n" }} {%- endfor %} {%- else -%} ⏰ None {%- endif %}) renders=2>
Error while processing template: Template<template=({% if state_attr('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching', 'planned_dispatches') | length > 0 %} {% for dispatch in state_attr('binary_sensor.octopus_energy_a_xxxx_intelligent_dispatching', 'planned_dispatches') -%} ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }} {{ "\n" }} {%- endfor %} {%- else -%} ⏰ None {%- endif %}) renders=6>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 936, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
TypeError: object of type 'NoneType' has no len()

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: TypeError: object of type 'NoneType' has no len()

[Dave-Parry]

Can I ask how to get "binary_sensor.octopus_energy_a_XXXXXXXX_intelligent_dispatching" as I don't have any dispatching sensors.

[BottlecapDave]

You have to have an active Octopus intelligent tariff. If you have just switched tariffs, you need to restart your HA instance or reload the integration to get the new sensors. If you have just switched, it can sometimes take a few days for the API to report the new tariff.

[Dave-Parry]

No on agile, ok so that's why I don't have them. Shame would have liked to use this.

[CraigCallender]

@Dave-Parry, if you're still in need, something like this is how I get the charge slots I've configured for my home battery via this integration:

{% if
state_attr('binary_sensor.octopus_energy_target_battery_charge_slots',
'target_times') | length > 0 %}
  {% for dispatch in state_attr('binary_sensor.octopus_energy_target_battery_charge_slots', 'target_times') -%}
    ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }} @ {{ '%0.2f' % (dispatch.value_inc_vat*100) }}p/kWh
    {{ "\n" }}
  {%- endfor %}
{%- else -%}
  ⏰ None
{%- endif %}

Which gives this:

The binary_sensor.octopus_energy_battery_charge_slots is the name a target rate I've configured via the Octopus Energy HA Integration.

[Ron-ski]

I've tried to implement this, I do get the list, but I get no title.

I've tried adding title: Planned Slots but this gets moved to the end, and doesn't appear, also tried adding label: Planned slots, still nothing.

Any ideas please?

type: custom:hui-element
card_type: markdown
content: |-
  {% if
  state_attr('binary_sensor.octopus_energy_a_XXXXXX_intelligent_dispatching',
  'planned_dispatches') | length > 0 %}
    {% for dispatch in state_attr('binary_sensor.octopus_energy_a_XXXXXX_intelligent_dispatching', 'planned_dispatches') -%}
      ⏰ {{ (dispatch.start | as_local).strftime('%H:%M') }} to {{ (dispatch.end | as_local).strftime('%H:%M') }}
      {{ "\n" }}
    {%- endfor %}
  {%- else -%}
    ⏰ None
  {%- endif %}
cards:
  - type: heading
    heading: Planned Slots

[reedy]

Use ``` (line before and line at the end) for blocks of code :)

What if you just have a title? As per #500 (reply in thread)

Trying to add a type: heading in place, my HA doesn't like it... It needs to be under a card etc...

So you may need to post your code with the wider context for it to work...

[Ron-ski]

Thanks, I originally copied and pasted reply 500, but it moves the title bit to the end as per my code above, and I don't get a title.

Not sure what you mean by "It needs to be under a card etc..." or you're last sentences, sorry but I'm not overly familiar with HA, or laying out cards.

Well, bizarrely, I moved the code to an existing section, but a new card, added the title and it works.

Previously it was a new section, I'm guessing each section has cards, and that's what you meant by under a card, stuff needs to be in cards, and cards reside in section.

Thanks

[reedy]

I can't say I'm particularly familiar with them either... Just know that there's a hierarchy and that some stuff can go under others, but then not under some others.

Glad you figured it out though!

Depending on how you're doing it, it will give you some visible errors in their "visual editor". They're not the most obvious some of the time, but should be pointing you in roughly the right direction.