Intelligent#
If you are on the intelligent tariff, then you'll get the following entities.
Warning
If you switch to the intelligent tariff after you have installed the integration, you will need to reload the integration or restart your Home Assistant instance.
Is Dispatching#
binary_sensor.octopus_energy_{{ACCOUNT_ID}}_intelligent_dispatching
This sensor is used to determine if you're currently in a planned dispatch period (i.e. "smart-charge" determined by Octopus Energy) or are within the standard off peak period. This sensor will not come on during a bump charge.
Warning
If you are using this to drive other automations for cheap rates (e.g. to fill batteries), you should perform additional checks to make sure your vehicle is actually charging. If it isn't, this sensor could be incorrectly on if during a dispatch outside of the standard off peak period and you will therefore not receive the off peak rate.
If you are wanting to know when you are within a guaranteed off peak period, you should use the off peak sensor.
Info
This sensor is only partially supported for the following intelligent providers
- OHME
If you are supplied by one of the above providers, planned_dispatches will always return an empty collection and this entity will only turn on when within the standard off peak period.
| Attribute | Type | Description |
|---|---|---|
planned_dispatches |
array |
An array of the dispatches that are currently planned by Octopus Energy. |
completed_dispatches |
array |
An array of the dispatches that have been completed by Octopus Energy. This will only store up to the last 3 days worth of completed dispatches. |
provider |
string |
The provider of the intelligent features |
vehicle_battery_size_in_kwh |
float |
The size of the target vehicle battery in kWh. |
charge_point_power_in_kw |
float |
The power of the charge point battery in kW. |
current_start |
datetime |
The date/time when the dispatching or off peak rate started |
current_end |
datetime |
The date/time when the dispatching or off peak rate ends |
next_start |
datetime |
The date/time when the next dispatching or off peak rate starts |
next_end |
datetime |
The date/time when the next dispatching or off peak rate ends |
Each item in planned_dispatch or completed_dispatches have the following attributes
| Attribute | Type | Description |
|---|---|---|
start |
datetime |
The start date/time of the dispatch |
end |
datetime |
The end date/time of the dispatch |
charge_in_kwh |
float |
The amount to be charged within the dispatch period. |
source |
string |
Determines what has caused the dispatch to be generated. Will be smart-charge or bump-charge. |
location |
string |
The location of the smart charge |
Info
You can use the data_last_retrieved sensor to determine when the underlying data was last retrieved from the OE servers.
Bump Charge#
switch.octopus_energy_{{ACCOUNT_ID}}_intelligent_bump_charge
This sensor is used to turn on/off bump ("on-demand") charging.
Info
This entity is not available for the following intelligent providers
- OHME
Info
You can use the data_last_retrieved sensor to determine when the underlying data was last retrieved from the OE servers.
Smart Charge#
switch.octopus_energy_{{ACCOUNT_ID}}_intelligent_smart_charge
This sensor is used to turn on/off intelligent smart charging.
Info
This entity is not available for the following intelligent providers
- OHME
Info
You can use the data_last_retrieved sensor to determine when the underlying data was last retrieved from the OE servers.
Charge Target#
number.octopus_energy_{{ACCOUNT_ID}}_intelligent_charge_target
This sensor is used to see and set the charge target for your future intelligent charges.
Info
This entity is not available for the following intelligent providers
- OHME
Info
You can use the data_last_retrieved sensor to determine when the underlying data was last retrieved from the OE servers.
Target Time#
time.octopus_energy_{{ACCOUNT_ID}}_intelligent_target_time
This sensor is used to see and set the target time for your future intelligent charges.
Info
This entity is not available for the following intelligent providers
- OHME
Info
You can use the data_last_retrieved sensor to determine when the underlying data was last retrieved from the OE servers.
Migrating from megakid/ha_octopus_intelligent?#
If you're moving to this integration from megakid/ha_octopus_intelligent, below is a quick guide on what entities you should use
binary_sensor.octopus_intelligent_slot- Use the is dispatching sensorbinary_sensor.octopus_intelligent_planned_dispatch_slot- There is no alternative for this.binary_sensor.octopus_intelligent_slot_next_1_hour,binary_sensor.octopus_intelligent_slot_next_2_hoursandbinary_sensor.octopus_intelligent_slot_next_3_hours- These sensors felt like they would always fall short of peoples requirements as everyone has different time periods they wish to know about. The is dispatching sensor exposes the current and next start/end times which could be used in a template sensor to determine how long the rate is cheap for when on.sensor.octopus_intelligent_next_offpeak_start- The default off peak start date/time can be found as an attribute on the off peak sensor. This can be extracted using a template sensor.sensor.octopus_intelligent_offpeak_end- The default off peak end date/time can be found as an attribute on the off peak sensor. This can be extracted using a template sensor.switch.octopus_intelligent_bump_charge- Use the bump charge sensorswitch.octopus_intelligent_smart_charging- Use the smart charge sensorselect.octopus_intelligent_target_time- Use the ready time sensorselect.octopus_intelligent_target_soc- Use the charge limit sensor