I think you need to delete and reinstall. when you go to settings > integrations and select the integration it should have a button for add - at this point a pop up should appear where you add your account details. If you already did that then you should have it already configured you should then see 1 device and (for me) 11 entities and a detailed display. Sorry I can’t add screenshots as I am not at my machine. If you are still stuck I can add screen shots later.
Is the binary_sensor.octopus_intelligent_slot broken, or is it just an issue with my installation?
I’ve seen some people mention that it’s broken and suggest using smoothing code.
I did try deleting and reinstalling it.
Thanks!
Hi, many thanks for all the work you do for people like me to dip my toe into this interesting arena of control. I’m late to the party on this but am here as like many other with EV on IOG and batteries trying to use HA to charge when IOG charges my car outside of the 11.30pm 50 5.30 am slots and stopping IOG draining my batteries. My question - or statement first is - I’m confused between ‘Intelligent dispatching’ and ‘Intelligent smart charge’. I’m sure one is for the normal 11.30 to 5.30 charge slot and the other I presume is for when Octopus charge outside of the IOG slot. Can anyone confirm which is which ? Many thanks
Intelligent dispatching tells you whether you are in a slot or not, but the allocated slots only show up in a card. I created a card on my dashboard using this code. that now shows me the slots
no slots to show here because I charged from 8% to 90% last night.
this is the code for the card
{% 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 %}
I must have copied it from somebody else’s published code because I have no idea what it all does. If you paste the above into a “markdown card” you will hopefully get the information out.
I believe the answer is that “smart charging” is the switch to turn intelligent control of the car / charge on or off
This I never touch
then there is intelligent dispatching which is the flag for whether you are getting charged or not
this is mine from last night. You can see that dispatching was off between 3 and 3:30, but the electricity was still off peak.
My battery automations (tesla powerwall) are to set the backup amount to 100% if despatching is on outside of 11:30 to 05:30, and when it goes off I just reset the backup to 15%
you can see above that the backup amount is set to 100% off peak in line with the intelligent slots.
I also have an automation to reset the backup at midnight so that powerwall can do it’s thing overnight in the ordinary off peak. The dispatching on automation is also triggered at 5:31 to reset the backup to 100% if dispatching runs past the end of off peak.
I’ve had this setup for over a year now and it seems to be working ok.
Thanks for your reply. I created a markdown card as you suggested but it doesn’t seem to work.
I was in a smart charging session when I created it
UPDATE: I used this replacing the XXXXXX with your sensor value
{{as_timestamp(state_attr('binary_sensor.octopus_energy_a_XXXXXXX_intelligent_dispatching','planned_dispatches')[0].start) | timestamp_custom('%I:%M %p')}} - {{ as_timestamp(state_attr('binary_sensor.octopus_energy_a_XXXXXXX_intelligent_dispatching','planned_dispatches')[0].end) | timestamp_custom('%I:%M %p')}}
{{as_timestamp(state_attr('binary_sensor.octopus_energy_a_XXXXXXX_intelligent_dispatching','planned_dispatches')[1].start) | timestamp_custom('%I:%M %p')}} - {{ as_timestamp(state_attr('binary_sensor.octopus_energy_a_XXXXXXX_intelligent_dispatching','planned_dispatches')[1].end) | timestamp_custom('%I:%M %p')}}
{{as_timestamp(state_attr('binary_sensor.octopus_energy_a_XXXXXXX_intelligent_dispatching','planned_dispatches')[2].start) | timestamp_custom('%I:%M %p')}} - {{ as_timestamp(state_attr('binary_sensor.octopus_energy_a_XXXXXXX_intelligent_dispatching','planned_dispatches')[2].end) | timestamp_custom('%I:%M %p')}}
1 Like
Just did some research, I think there was an update to the entity name, so here is the new code I worked out, it displayed “None” when there is no planned dispatch, and will display all the planned dispatches when there are more than 1 elements in the attributes.
I am using lovelace dashboard UI btw.
don’t forget to replace xxxxxxx with your IOG account number
{% set dispatches = state_attr('binary_sensor.octopus_energy_xxxxxxxx_intelligent_dispatching', 'planned_dispatches') | default([]) %}
{% if dispatches | length > 0 %}
{% for dispatch in dispatches %}
## ⏰ {{ as_timestamp(dispatch.start) | timestamp_custom('%I:%M %p') }} - {{ as_timestamp(dispatch.end) | timestamp_custom('%I:%M %p') }}
{% endfor %}
{% else %}
## ⏰ None
{% endif %}
Thank you so much for this. I was pulling my hair out wondering why my email address wasn’t working for the account ID 
Just looking into this but cant get the integration has it changed?
Its exactly what im looking for
Hi Angus
Does this script apply to Powerwall 3 or is it designed for Powerwall 2.
I want to be able to stop my EV from discharging the PW3 and also for the PW3 to charge when EV is charging using off peak rates.
Regards
Roger
Hi @rfa
Sorry i don’t have a PW3 so would not know if this can also control the PW3. But I suspect of you have the integration control over the PW3 then it might work after you substitute the old sensors for the new PW3 sensors.
I have two automations that solve this:
- Disable the Powerwall from discharging (set discharge % to 0) when your EV charger is charging. Use the EV charger’s status sensor.
- Set your Powerwall to charge from grid when the off peak sensor in this integration is ON. Don’t use ‘dispatching’ any more as that won’t always be on during the fixed off-peak window.
And then two automations reversing the above in the opposite state.
I have found doing just #2 above leaves the batteries fully discharging for a couple of minutes at the start of a charge outside of core off-peak hours before the off peak sensor kicks in and I didn’t want that. It also means if you decide to boost it comes from the grid, you may or may not want that.
Hi All,
I am new to Octopus and just installed this integration.
It all seems to be working fine but I just wanted to Sanity Check something.
My Car charging turned on via the “Octopus Intelligent Planned Dispatch Slot” but the time was 17:30 which seemed kinda strange as this would normally be in the middle of Peak Rate time. Also, according to the Octopus App, my Car Scheduled Slots didn’t have one that matched that time period.
Is there any way to see what your live Octopus rates are for peace of mind??
Cheers
If dispatching is on then you’re on cheap rate. I believe the one exception to this is with the Ohme where if your car does not charge then you will not get the credit. With the Zappi it doesn’t matter if the car successfully charges or not, eg you unplug the car during the half hour slot, the slot ends but the 30 minutes is still on cheap rate.
IO gives lots of slots when demand is low and renewables production high outside of the core off-peak hours.
If you wanted to sense check, you could use “Current Rate Electricity” from your meter through the Octopus integration.
Just beware with dispatching it will not necessarily be ‘on’ during that fixed off-peak period anymore, even though you will be on your cheap rate. To capture both IO slots and the fixed off-peak period, use the ‘off peak’ sensor.