Merge branch 'develop' into feat/fan-club-discount

Author: BottlecapDave

.husky/prepare-commit-msg

@@ -1 +1 @@
-exec < /dev/tty && npx cz --hook || true
+# exec < /dev/tty && npx cz --hook || true

_docs/faq.md

@@ -182,6 +182,19 @@ Cost sensors are calculated by multiplying the consumption by the rate for each
 
 Each half hour block has it's consumption rounded to the nearest 0.01kwh before multiplying by the rate, which is rounded to the nearest penny. The rounding method used is rounding half to even, where numbers ending in 5 are rounded up or down, towards the nearest even hundredth decimal place. As a result, 0.015 would be rounded up to 0.02, while 0.025 is rounded down to 0.02. This is based on [Octopus Energy API documentation](https://developer.octopus.energy/rest/guides/endpoints)
 
+## I'm having issues with a sensor. Is there any way I can see the attributes for a certain point in time?
+
+The majority of attributes for entities are stored in the database for a short amount of time (default is around 10 days). Unfortunately, the only way of obtaining historic attributes is via the database. This can be done via the [SQLite Web Add-On](https://my.home-assistant.io/redirect/supervisor_addon/?addon=a0d7b954_sqlite-web), where the following SQL query can be executed. You'll need to change the target entity id from `binary_sensor.octopus_energy_xxx_intelligent_dispatching` to the one you want to target.
+
+```
+SELECT states_meta.entity_id, states.state, state_attributes.shared_attrs, DATETIME(last_changed_ts, 'unixepoch'), DATETIME(last_updated_ts, 'unixepoch')
+FROM "states"
+join state_attributes on states.attributes_id = state_attributes.attributes_id
+join states_meta on states_meta.metadata_id = states.metadata_id
+where states_meta.entity_id = 'binary_sensor.octopus_energy_xxx_intelligent_dispatching'
+order by last_updated_ts desc
+```
+
 ## Do you support older versions of the integration?
 
 Due to time constraints, I will only ever support the latest version of the integration. If you have an issue with an older version of the integration, my initial answer will always be to update to the latest version. This might be different to what HACS is reporting if you are not on the minimum supported Home Assistant version (which is highlighted in each release's changelog). 

_docs/repairs/no_active_tariff.md

@@ -3,7 +3,8 @@
 If you receive this repair notice it means that no active tariff was found for one or more of your meters. There are a few reasons why this might be the case.
 
 1. You are in the middle of switching tariffs. There can sometimes be a gap in your tariff information coming through when your existing tariff ends and your new tariff begins.
-2. You are new to OE and your tariff hasn't begun yet. Once your tariff starts, the integration will pick it up and should start working.
-3. There is a configuration issue with your account. In this scenario, you'll need to contact Octopus Energy support to get this rectified.
+2. You have had a meter swap. When your meter is replaced, it can take time for systems to fully update, leaving a gap in tariff information until this is complete.
+3. You are new to OE and your tariff hasn't begun yet. Once your tariff starts, the integration will pick it up and should start working.
+4. There is a configuration issue with your account. In this scenario, you'll need to contact Octopus Energy support to get this rectified.
 
-All of the above scenarios can be confirmed within your [diagnostic data](../faq.md#ive-been-asked-for-my-meter-information-in-a-bug-request-how-do-i-obtain-this). This will contain your account data including your meters. Under each of your meters, you'll have a list of tariff agreements. For each meter, you should have an agreement with a start date in the past and an end date either in the future or with no end date.
+All of the above scenarios can be confirmed within your [diagnostic data](../faq.md#ive-been-asked-for-my-meter-information-in-a-bug-request-how-do-i-obtain-this). This will contain your account data including your meters. Under each of your meters, you'll have a list of tariff agreements. For each meter, you should have an agreement with a start date in the past and an end date either in the future or with no end date.

custom_components/octopus_energy/electricity/previous_accumulative_cost_override.py

@@ -130,8 +130,8 @@ async def async_update(self):
             self._standing_charge is None or
             self._rates[0]["start"] != period_from or
             self._rates[-1]["end"] != period_to or
-            self._standing_charge[0]["start"] != period_from or
-            self._standing_charge[-1]["end"] != period_to):
+            self._standing_charge["start"] != period_from or
+            self._standing_charge["end"] != period_to):
 
           _LOGGER.debug(f"Retrieving rates and standing charge overrides for '{self._mpan}/{self._serial_number}' ({period_from} - {period_to})...")
           [rate_data, standing_charge] = await asyncio.gather(

custom_components/octopus_energy/gas/previous_accumulative_cost_override.py

@@ -131,8 +131,8 @@ async def async_update(self):
             self._standing_charge is None or
             self._rates[0]["start"] != period_from or
             self._rates[-1]["end"] != period_to or
-            self._standing_charge[0]["start"] != period_from or
-            self._standing_charge[-1]["end"] != period_to):
+            self._standing_charge["start"] != period_from or
+            self._standing_charge["end"] != period_to):
 
           _LOGGER.debug(f"Retrieving rates and standing charge overrides for '{self._mprn}/{self._serial_number}' ({period_from} - {period_to})...")
           [rate_data, standing_charge] = await asyncio.gather(