question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Intergration stopped working

See original GitHub issue

For 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:closed
  • Created a year ago
  • Reactions:2
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
davelegg83commented, Sep 20, 2022

Everything has started working again!

0reactions
github-actions[bot]commented, Nov 8, 2022

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Tuya Integration Stopped working - Home Assistant Community
As of this morning, the Tuya integration stopped working - seemingly following an attempt at updating the Home Assistant Core to 2022.9.7 …...
Read more >
ℹ️ Tuya integration not working · Issue #80278 - GitHub
The problem Tuya integration stopped working Recently there are many complains about Tuya integration not working, most of them are due to ...
Read more >
Why is my integration not working? - Mews Help
If an integration connected to your Mews account doesn't work, follow this troubleshooting process to try and fix the issue and re-enable data...
Read more >
VNet Integration Stopped working for all apps on same App ...
I have 5 web apps running on the same app service plan. Each app has VNet Integration setup so they can access on-premise...
Read more >
My Facebook integration stopped working - Zendesk help
Issue symptoms. My Facebook integration is not syncing or working correctly. Messages from Facebook don't create tickets.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found