I'm now on v4.5.0. I've set up two intermittent Target Rates, one for three hours and the other for six hours. No offset and a 00:00 - 23:59 min/max. Here are the results:

Couple of things seem odd:

1. The three hours are not a sub-set of the six hours, e.g. the three hour sensor came on at 4pm for 90 mins (during a period that definitely wasn't in the top 3 cheapest hours of the day!).
2. There is much more than 3/6 hours where each sensor is activated in a 24hr period.

Today's pricing is as follows (incl. a nice plunge in the early morning!):

00:00 - 00:30 | 22.36
00:30 - 01:00 | 6.05
01:00 - 01:30 | 1.05
01:30 - 02:00 | -0.27
02:00 - 02:30 | 0.00
02:30 - 03:00 | -1.64
03:00 - 03:30 | -3.19
03:30 - 04:00 | -8.40
04:00 - 04:30 | -4.20
04:30 - 05:00 | -8.40
05:00 - 05:30 | -7.14
05:30 - 06:00 | 2.10
06:00 - 06:30 | 6.51
06:30 - 07:00 | 23.73
07:00 - 07:30 | 18.06
07:30 - 08:00 | 31.50
08:00 - 08:30 | 35.80
08:30 - 09:00 | 35.80
09:00 - 09:30 | 33.10
09:30 - 10:00 | 30.74
10:00 - 10:30 | 27.89
10:30 - 11:00 | 23.10
11:00 - 11:30 | 20.50
11:30 - 12:00 | 17.26
12:00 - 12:30 | 17.43
12:30 - 13:00 | 14.49
13:00 - 13:30 | 15.58
13:30 - 14:00 | 6.89
14:00 - 14:30 | 13.44
14:30 - 15:00 | 12.01
15:00 - 15:30 | 12.10
15:30 - 16:00 | 16.80
16:00 - 16:30 | 29.40
16:30 - 17:00 | 35.80
17:00 - 17:30 | 35.80
17:30 - 18:00 | 36.75
18:00 - 18:30 | 35.80
18:30 - 19:00 | 38.79
19:00 - 19:30 | 35.80
19:30 - 20:00 | 35.80
20:00 - 20:30 | 35.80
20:30 - 21:00 | 30.60
21:00 - 21:30 | 35.80
21:30 - 22:00 | 29.82
22:00 - 22:30 | 35.80
22:30 - 23:00 | 25.62
23:00 - 23:30 | 35.80
23:30 - 00:00 | 31.08

Finally, I'm still getting the following error when I try to create a new Target Rates sensor without entering min/max times (may also be caused by blank offset?):

Logger: aiohttp.server
Source: custom_components/octopus_energy/config_flow.py:215
Integration: Octopus Energy ([documentation](https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/), [issues](https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues))
First occurred: 18:12:16 (3 occurrences)
Last logged: 18:12:54

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 222, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 216, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 71, in post
    result = await self._flow_mgr.async_init(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 225, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 252, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data, init_done)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/octopus_energy/config_flow.py", line 246, in async_step_init
    return await self.__async_setup_target_rate_schema(config, {})
  File "/config/custom_components/octopus_energy/config_flow.py", line 215, in __async_setup_target_rate_schema
    vol.Optional(CONFIG_TARGET_START_TIME, default=config[CONFIG_TARGET_START_TIME]): str,
KeyError: 'Start time'

Appreciate any pointers!

Hi love the intergration, I was doing this manually before but so much easier now, thank you.

2.0.0 worked perfectly and was downloading data each day. Since 3.0.0 no data is ever downloaded and sensors stay at 0

Rolling back to 2.0.0 gets data again upgrading to 3.0.1 (or 3.0.0) breaks the intergration

I'm not sure they are relevant but her are the only log entries I can see that are related File "/config/custom_components/octopus_energy/__init__.py", line 89, in async_update_data hass.data[DOMAIN][DATA_RATES] = await client.async_get_rates(tariff_code, period_from, period_to) File "/config/custom_components/octopus_energy/api_client.py", line 107, in async_get_rates return await self.async_get_standard_rates(product_code, tariff_code, period_from, period_to) File "/config/custom_components/octopus_energy/api_client.py", line 49, in async_get_standard_rates data = await response.json(content_type=None) File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1119, in json return loads(stripped.decode(encoding)) File "/usr/local/lib/python3.9/json/__init__.py", line 346, in loads return _default_decoder.decode(s) File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/local/lib/python3.9/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

May be relevant that i'm an octopus energy UK customer and don't have a varible tarrif.

With 3.0.1 (and 3.0.0) the intergration is getting the following; sensor.octopus_energy_electricity_XXXXXXXXX_latest_consumption = Unavailable sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption = 0 sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0 sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_cost = 0 sensor.octopus_energy_electricity_current_rate = 0.187845 (always the same) sensor.octopus_energy_electricity_previous_rate = 0.187845 (always the same) sensor.octopus_energy_gas_XXXXXXXXX_latest_consumption = Unavailable sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption = 0 sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0 sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_cost = 0

With 2.0.0 the intergraion get the following: sensor.octopus_energy_electricity_XXXXXXXXX_latest_consumption = 0 sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption = 16.962 sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0 sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_cost = Unavailable sensor.octopus_energy_electricity_current_rate = 0.187845 (always the same) sensor.octopus_energy_electricity_previous_rate = 0.187845 (always the same) sensor.octopus_energy_gas_XXXXXXXXX_latest_consumption = 0 sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption = 2.781 sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0 sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_cost = Unavailable

Happy to test anything that might help.

I've set this up via HACS, the data appears to be there as I can see the prices under the attributes but the device targets don't have any data under them so they never trigger, this is what I see under HA states.

Describe the bug Missing gas meter sensors

To Reproduce Added integration, current and previous electricity meter added, no gas meter

A gas meter may be seen to be present when running an API curl command https://api.octopus.energy/v1/accounts/A-xxxxxxx/ (the same key and acount added to the integrations. The meter is SMETS1 but is adopted )I tried ticked and unticked).

Expected behavior Gas meter sensors to be added. Home Assistant Logs I can't find anything useful.

Describe the bug

I've just switched to Octopus last week, and as a result am on "Flexible Octopus" (for now) which contractually showed as 52p per kWh, but due to the government cap is actually 34.23p per kWh. The Octopus app and website both show as 34.23p per kWh, but obviously the API does not, as this HA integration is showing 0.52074225 GBP/kWh

rate:  
value_exc_vat: 49.5945 
value_inc_vat: 52.074225 
valid_from: '2022-10-17T16:00:00+00:00' 
valid_to: '2022-10-17T16:30:00+00:00' 
tariff_code: E-1R-VAR-22-10-01-H  
is_export: false 
is_smart_meter: true

To Reproduce

Have a government capped tariff. Sorry! I assume this is unlikely to be an issue with the integration and an API issue instead, but I thought I'd check and/or wasn't sure if you had a contact at Octopus rather than attempting to explain this to the standard customer support.

Expected behavior

The correct price is returned.

Home Assistant Version 2022.10.4

Integration Version v4.5.1

Fresh Install? Fresh install

Let me know if debug logs would help.

Hi there,

Just installed this and seems to all work (great work on this!), correctly returns my rate, however both consumption and cost values are returning 0.

Any ideas on how I can diagnose this?

Describe the bug

Sensors are created for meters which have been replaced at the same property.

To Reproduce

Have a property which returns these kind of API responses 😅

{
  "number": "A-BCD123EF",
  "properties": [
    {
      "id": 1234567,
      // redacted for brevity
      "electricity_meter_points": [
        {
          "mpan": "0123456789",
          "profile_class": 1,
          "consumption_standard": 5720,
          "meters": [
            {
              "serial_number": "XXXXXXXXX",
              "registers": [
                {
                  "identifier": "00",
                  "rate": "STANDARD",
                  "is_settlement_register": true
                }
              ]
            },
            {
              "serial_number": "YYYYYYYYY",
              "registers": [
                {
                  "identifier": "1",
                  "rate": "STANDARD",
                  "is_settlement_register": true
                }
              ]
            }
          ],
          "agreements": [
            {
              "tariff_code": "E-1R-SUPER-GREEN-24M-21-05-29-E",
              "valid_from": "2021-06-30T00:00:00+01:00",
              "valid_to": "2023-06-30T00:00:00+01:00"
            }
          ],
          "is_export": false
        }
      ],
      "gas_meter_points": [
        {
          "mprn": "12345678",
          "consumption_standard": 47722,
          "meters": [
            {
              "serial_number": "AAAAAAAAAAAAAA"
            },
            {
              "serial_number": "BBBBBBBBBBBBBB"
            }
          ],
          "agreements": [
            {
              "tariff_code": "G-1R-SUPER-GREEN-24M-21-05-29-E",
              "valid_from": "2021-06-30T00:00:00+01:00",
              "valid_to": "2023-06-30T00:00:00+01:00"
            }
          ]
        }
      ]
    }
  ]
}

Consumption API for the old meters is completely blank:

{"count":0,"next":null,"previous":null,"results":[]}

Expected behavior

No sensors are created for the old meters.

Misc

Background here: moved into property with old style meters, which where shortly thereafter replaced by smart meters. Sensors are created for the new meters just fine, but also for the meters which were removed, and have no data.

This might be a bug in the rest API - the old meters don't show in the UI, and don't appear in the graphql API afaict:

Using the REST API this might be tricky to handle cleanly because the sensors are created based on the data in the account API, which then go on to have no data in the consumption API but they have already been created at that point. I have disabled the entities for now so it's no big deal to me, but wanted to document the issue here while I had all the info in my head.

Thanks for creating this - I wanted to get some price sensors and started to look at building a small component based on the GraphQL api, this component saved me the effort 🙂

I have been using this HACS integration for a month or two, and it is great. I did some playing around with the Octopus API in Postman, and noticed that it gives consumption for half hourly time periods, with the group_by parameter allowing reduced granularity. The integration stores the data for the previous day. I understand that Octopus doesn't provide data newer than the previous day.

Do you have any plans to allow using a shorter time period in the integration? I'd be interested in helping out with this.

Firstly - thank you so much for developing this integration. Super clean and helpful! Much appreciated.

Describe the bug I have just set up my integration. But I was not sure if the gas calculation was working. It shows previous day gas consumption of some 6.5m³ but previous day gas cost of £0.49. I suspect the calculation was taking the p/kWh (around 3.6p) multiplied directly to the 6.5m³ and added standing charge of some £0.25. But in reality, the gas cost is much higher in particular in winter...

To Reproduce Steps to reproduce the behavior: Initiate the integration and read the gas cost against normal bill cycle

Expected behavior When I was reading the bill, the energy calculation is much more complicated. Your energy usage is calculated from your gas consumption using a standard industry formula: Units Consumed (Cubic Metres) × Volume Correction (for temperature & pressure) × Calorific Value (energy in each m3 of gas) ÷ 3.6 (convert from joules) ≈ Usage (in kWh) So the 6.547m³ need to be converted to some 72kWh (based on the numbers on my bill), then multiplied with the 3.6p, adding standing charge, getting to close to £3 per day, this sounds more like the case in winter...

The solution that I have is to change the utils.py, make use of your conversion from kWh to m³ but do the opposite way. i.e. I took the m³ reading and multiply Volume Correction, Colorific Value and convert from joules (change the signs in the last bit), then tick the SMET1 box in the integration (so that the conversion kicks in). Let me know your thoughts.

Home Assistant Logs N/A

Describe the bug No data for Gas sensors:

previous_accumulative_consumption
previous_accumulative_consumption_cost
previous_accumulative_cost

These sensors have attributes relating to my meter (e.g. serial number, MPRN etc) but always have a 0 value

gas_current_rate does have a value

To Reproduce Installed and connected to my account. I have electricity details. The Octopus API does return data when querying my gas metere

Expected behavior Gas data be present?

Home Assistant Logs Nothing I can see, tell me how to be useful and I'll provide

Hiya, great work, looking forward to trying this! Just wondering if you had considered submitting to the Home Assistant Component Store to make installation and updating one click easier?

https://hacs.xyz/docs/publish/start

I have created both import and export targets (I have both meters) but both get named Export (Octopus Energy Target Export 3i_import)

Can we either name as an import Target or remove the Export text from the name?

Using version 5.0.0

Don't see this addressed in the upgrade notes for 5.1.0 but haven't upgraded yet, so sorry if this is already fixed.

Describe the bug

If using Intellilgent Octopus, and Octopus decide to charge your EV during peak time, the tariff changes to the off-peak tariff. However, the tariff shown in this integration is still the peak tariff.

To Reproduce

Signup to Intelligent Octopus and observer sensor behaviour.

Expected behavior

The tariff should accurately reflect the current rate.

Home Assistant Version

The version of Home Assistant.

Integration Version

2022.12.8

The entities show the totals for kWh and Costs, would it be possible to add more entities that show the peak and off-peak separately from the totals ie the build up.

Expected behavior for example :- Peak kWH = 2 , Off-Peak kWH = 4 , Total kWH = 6 Peak Cost = 24p , Off-Peak kWH = 48p , Total kWH = 72p

This would make it so much easier to understand the total cost build up and usage and how the totals are calculated. Apologise if there is an easy way to already do this, but I'm still learning

Not sure how straightforward this would be, but I have a use case where I have a target set to run in the early morning, but want to use an Automation earlier in the evening to set charging times on my batteries(mostly so I can either choose to cancel it, or verify the time on the inverter)

From what I can see, the once a day targets seem to evaluate at midnight. would it be possible to have a service to trigger the evaluation on demand?

As part of https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues/79, it was discovered that some of the sensors were configured incorrectly with Home Assistant. Unfortunately, there doesn't seem to be an easy way of fixing this without following one of the following approaches.

Manual Statistic Removal

This approach is a little more involved and easiest to launch two browsers/tabs. In the first tab, navigate to your entities (e.g. http://homeassistant.local:8123/config/entities) and search for octopus. In the second tab, you should navigate to your statistics (e.g. http://homeassistant.local:8123/developer-tools/statistics) and search for Octopus.

Now for each sensor

1. In the first tab, click on the sensor and navigate to settings
2. Under Advanced settings click on Disabled and then Update.
3. Wait a couple of seconds
4. Click on the sensor and navigate to settings
5. Under Advanced settings click on Enabled and then Update.
6. In the second tab, find the corresponding entity
7. Click Fix issue
8. In the pop up, click Remove

Reinstall the integration

The easiest approach is to remove all references to the integration.

Once done, you will need to visit your Home Assistant statistics page (e.g. http://homeassistant.local:8123/developer-tools/statistics) and make sure all statistics are removed. If not, you'll neer to remove the statistic associated with each Octopus Energy sensor. This can be done by clicking Fix Issue button and then clicking "remove". If none are here, then

Once all statistics are removed, you can reinstall the integration.

Side Effects

The side effects of this fix unfortunately is that you'll lose all historic statistics for the integration. There doesn't appear to be any way of saving these :(

If you still have historic data after your removal of statistics, please follow the steps again as you should have no data available.

Feature request.

I'm trying to use my inverter's force_charge(minutes) feature along side the intermittent mode to make best use of the cheapest overnight 30 minutes blocks. However my problem is as the 30 minutes blocks can follow each other and would therefore only fire one off->on trigger I can't use a default of 30 in the force_charge command. If there was a simple mechanism which reported the current block size then I could use that for the force_charge command and greatly simplify my automation trigger setup, plus reduce the number of commands sent to the inverter.