agilewebsolutions commented 1 year ago

Describe the bug

This entity is no longer being provided by the octopus_energy integration. If the entity is no longer in use, delete it in settings.

Reproduction steps

all entities are univialable

Expected behaviour

should be showing the rates, been working for ages fine.

Tariff Code

No response

Integration Version

latest

Home Assistant Version

2023.9.1

Fresh Install?

Not specified

Home Assistant Logs

not sure how

neojski commented 1 year ago

Observed the same issue after installing 2023.9.1 today.

agilewebsolutions commented 1 year ago

I restored backup to previous version and it fixed it. So definitely problem with version.

neojski commented 1 year ago

I backed things out to my previous backup which, unfortunately, was 2023.6.2 but that did not fix the integration for me. I get exceptions like this:

2023-09-09 12:31:15.893 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Account for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 169, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 179, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!

Update: after rolling back the unsuccessful rollback I checked the logs again and I still see this same thing as the first problem. So I suspect this is actually the root cause.

BottlecapDave commented 1 year ago

I've just upgraded to the latest version of HA and I'm running the latest version of the integration and not seeing this issue.

The logs that @neojski can be seen at times when reloading the integration without restarting HA. I've yet to discover why this occurs as I follow what other integrations do.

Have any of you tried restarting your instance of HA? If the API is unavailable (e.g. server errors on the API or no internet connection) during initialisation then this can produce this result. I have it on my list to raise a repair in this scenario.

If you're still not able to get the integration working, could someone please follow the faq and paste your logs in this thread along with your tariff. This can help me track down and solve the issue.

neojski commented 1 year ago

The first error I see after restart is this:

2023-09-10 00:01:11.813 ERROR (MainThread) [homeassistant.components.text] octopus_energy: Not adding entity with invalid device info: Invalid device info {'default_name': 'Electricity Meter', 'identifiers': {('octopus_energy', 'electricity_xxx')}, 'manufacturer': '1063 - Landis and Gyr', 'model': '00050203', 'sw_version': '38040602'} for 'octopus_energy' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-10 00:01:11.816 ERROR (MainThread) [homeassistant.components.text] octopus_energy: Not adding entity with invalid device info: Invalid device info {'default_name': 'Gas Meter', 'identifiers': {('octopus_energy', 'electricity_xxx')}, 'manufacturer': '1063 - Landis and Gyr', 'model': '47720101', 'sw_version': '03033254'} for 'octopus_energy' config entry: device info needs to either describe a device, link to existing device or provide extra information.

I've restarted Home Assistant. I've also removed the integration and installed it back again but with no luck.

I also noticed that if I give the integration invalid API key it doesn't (visibly, not logs) complain.

neojski commented 1 year ago

I'm trying to see if I can remove the entities but I can't despite removing octopus integration. Maybe that's another lead

Edit: I was hoping that restarting home assistant would fix this but it didn't. So maybe this is the duplicates problem the exception above was talking about.

BottlecapDave commented 1 year ago

The first error I see after restart is this:

2023-09-10 00:01:11.813 ERROR (MainThread) [homeassistant.components.text] octopus_energy: Not adding entity with invalid device info: Invalid device info {'default_name': 'Electricity Meter', 'identifiers': {('octopus_energy', 'electricity_xxx')}, 'manufacturer': '1063 - Landis and Gyr', 'model': '00050203', 'sw_version': '38040602'} for 'octopus_energy' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-10 00:01:11.816 ERROR (MainThread) [homeassistant.components.text] octopus_energy: Not adding entity with invalid device info: Invalid device info {'default_name': 'Gas Meter', 'identifiers': {('octopus_energy', 'electricity_xxx')}, 'manufacturer': '1063 - Landis and Gyr', 'model': '47720101', 'sw_version': '03033254'} for 'octopus_energy' config entry: device info needs to either describe a device, link to existing device or provide extra information.

I've restarted Home Assistant. I've also removed the integration and installed it back again but with no luck.

I also noticed that if I give the integration invalid API key it doesn't (visibly, not logs) complain.

That error got fixed in 8.0.0 of the integration. Are you sure you're using the latest version of the integration? This can be confirmed by following these instructions and pasting the contentes here.

neojski commented 1 year ago

Updating the integration fixed it. I didn't write realise that custom integrations have their own updates screen so I was running an old version. Presumably the new home assistant version somehow made it more likely to trigger that old problem.

Thanks!

BottlecapDave commented 1 year ago

No problem @neojski. Yeah the issue you mentioned was introduced in the last HA update iirc. The integration will release separately to HA. There is a sensor available via the HACS integration which can be used with an automation (or similar) to indicate if updates are available

BottlecapDave commented 1 year ago

I've just upgraded to the latest version of HA and I'm running the latest version of the integration and not seeing this issue.

Have any of you tried restarting your instance of HA? If the API is unavailable (e.g. server errors on the API or no internet connection) during initialisation then this can produce this result. I have it on my list to raise a repair in this scenario.

If you're still not able to get the integration working, could someone please follow the faq and paste your logs in this thread along with your tariff. This can help me track down and solve the issue.

@agilewebsolutions was this your problem as well? If not, are you able to supply some logs using the above methods?