ha-solcast-solar: unexpected keyword argument

The problem

Had to restart HA today which broke my exsiting Oziee install. I’ve added this repor to HACS but it’s refusing to start’ Front end reports ‘Failed to set up’, logs report TypeError: ConfigEntries.async_update_entry() got an unexpected keyword argument ‘version’

I’ve deleted from HA and reinstalled, generated a new API key, restarted and refreshed, still can’t get Solcast up and running again.

What version of Solcast Integration has the issue?

4.0.31

What version of Home Assistant are you using?

2024.2.1

Diagnostics information

No response

Logs debug/info/error output

2024-06-17 11:22:26.200 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Solcast Solar for solcast_solar
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/solcast_solar/__init__.py", line 76, in async_setup_entry
    hass.config_entries.async_update_entry(entry, options=new, version=7)
TypeError: ConfigEntries.async_update_entry() got an unexpected keyword argument 'version'

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 17 (6 by maintainers)

Most upvoted comments

I am going to try and craft a work-around for this, @BJReplay and @kernow. It will involve trying whether version= is a thing for async_update_entry() or not, and if not then falling back to what was there before.

So if you cannot upgrade, @kernow then I got ya from a Solcast integration POV.

Thanks, that’s very kind. I went all “who cares” and upgraded HA and all working now. Just have to see if something else has broken or not.

You were right, updating HA to latest has resovled my issue, thanks again for the quick reply!

The root of this is because “version=” is not recognised as a kwarg for async_update_entry(). That has to be new then, and very recent, so why change until HA say "we’re going to remove what you were doing as a breaking change? Or at very least try:/except: for it???

Gah.

I love this integration.

That still begs the question, why did oziee introduce a breaking change?

I meant breaking changes in general, I’ve got HA doing a lot of jobs and updates to various integrations often bring in breaking changes, not related to Solcast in this instance

P. S. Thanks for the detailed issue with logging!

This really interests me, @BJReplay and @Markyt77 (cc: @kernow from discussion). This relates to changes that were part of oziee’s missing 4.0.23 changes…

What version are you on @kernow?

Maybe oziee’s changes weren’t fully thought through…