Intergration stopped working
See original GitHub issueFor some reason the intergration seems to have stopped working. When I click on one of the entities it says ‘This entity is no longer being provided by the octopus_energy integration. If the entity is no longer in use, delete it in settings.’ I tried uninstalling and re-installing, however after putting in the API key and account, It just says ‘Unknown error occured’
Looking at the logs it says: `Logger: custom_components.octopus_energy Source: custom_components/octopus_energy/api_client.py:120 Integration: Octopus Energy (documentation, issues) First occurred: 07:29:14 (1 occurrences) Last logged: 07:29:14 Unexpected error fetching rates data: ‘NoneType’ object is not subscriptable
Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 205, in _async_refresh self.data = await self._async_update_data() File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 164, in _async_update_data return await self.update_method() File “/config/custom_components/octopus_energy/init.py”, line 79, in async_update_electricity_rates_data tariff_codes = await async_get_current_electricity_agreement_tariff_codes(client, config) File “/config/custom_components/octopus_energy/init.py”, line 54, in async_get_current_electricity_agreement_tariff_codes account_info = await client.async_get_account(config[CONFIG_MAIN_ACCOUNT_ID]) File “/config/custom_components/octopus_energy/api_client.py”, line 112, in async_get_account “gas_meter_points”: list(map(lambda mp: { File “/config/custom_components/octopus_energy/api_client.py”, line 117, in <lambda> “agreements”: list(map(lambda a: { File “/config/custom_components/octopus_energy/api_client.py”, line 120, in <lambda> “tariff_code”: a[“tariff”][“tariffCode”], TypeError: ‘NoneType’ object is not subscriptable`
and
`Logger: homeassistant.components.sensor Source: helpers/update_coordinator.py:178 Integration: Sensor (documentation, issues) First occurred: 07:29:14 (1 occurrences) Last logged: 07:29:14 Error while setting up octopus_energy platform for sensor
Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 205, in _async_refresh self.data = await self._async_update_data() File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 164, in _async_update_data return await self.update_method() File “/config/custom_components/octopus_energy/init.py”, line 79, in async_update_electricity_rates_data tariff_codes = await async_get_current_electricity_agreement_tariff_codes(client, config) File “/config/custom_components/octopus_energy/init.py”, line 54, in async_get_current_electricity_agreement_tariff_codes account_info = await client.async_get_account(config[CONFIG_MAIN_ACCOUNT_ID]) File “/config/custom_components/octopus_energy/api_client.py”, line 112, in async_get_account “gas_meter_points”: list(map(lambda mp: { File “/config/custom_components/octopus_energy/api_client.py”, line 117, in <lambda> “agreements”: list(map(lambda a: { File “/config/custom_components/octopus_energy/api_client.py”, line 120, in <lambda> “tariff_code”: a[“tariff”][“tariffCode”], TypeError: ‘NoneType’ object is not subscriptable
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 281, in _async_setup_platform await asyncio.shield(task) File “/config/custom_components/octopus_energy/sensor.py”, line 97, in async_setup_entry await async_setup_default_sensors(hass, entry, async_add_entities) File “/config/custom_components/octopus_energy/sensor.py”, line 113, in async_setup_default_sensors await rate_coordinator.async_config_entry_first_refresh() File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 178, in async_config_entry_first_refresh raise ex homeassistant.exceptions.ConfigEntryNotReady: ‘NoneType’ object is not subscriptable`
Hoping you might be able to help.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top GitHub Comments
Everything has started working again!
This issue has been closed because it has been inactive for 14 days since being marked as stale. This is done to help keep on top of active issues. If you still think it’s an issue, please respond to this issue