Error while setting up ads platform for cover

[birdie60]

The problem

Since upgrade to HA 2024.11.3, docker version, I have this error in the logs.
While all ADS based sensors and lights are functional, all ADS based covers are not.

What version of Home Assistant Core has the issue?

HA 2024.11.3

What was the last working version of Home Assistant Core?

HA 2024.10.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

ADS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/cover

Diagnostics information

ADS based covers stopped working in HA 2024.11.3. Before, I had no problems.
Only covers ceased to work, all other ADS entities I use are working (sensors, binary-sensors, lights, etc).

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.cover
Quelle: helpers/entity_platform.py:365
Integration: Abdeckung (Dokumentation, Probleme)
Erstmals aufgetreten: 6. Dezember 2024 um 17:04:00 (9 Vorkommnisse)
Zuletzt protokolliert: 6. Dezember 2024 um 17:04:00
Error while setting up ads platform for cover

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 365, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/ads/cover.py", line 61, in setup_platform
    ads_var_is_closed: str = config[CONF_ADS_VAR]
                             ~~~~~~^^^^^^^^^^^^^^
KeyError: 'adsvar'

Additional information

Later in the logs are entries for all ADS based covers, like

Referenced entities cover.wc_beschattung_ads are missing or not currently available

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (cover) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of cover can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign cover Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

cover documentation
cover source
_{^{(message by IssueLinks)}}

[home-assistant]

Hey there @mrpasztoradam, mind taking a look at this issue as it has been labeled with an integration (ads) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ads can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ads Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

ads documentation
ads source
_{^{(message by IssueLinks)}}

[elconfa]

Hi, My COVER don't work anymore either. This entity is no longer managed by the ADS integration. Does anyone have a solution? Thanks

[mrpasztoradam]

Hi! It seems like a duplicate of another, already closed issue. Please check out and try to amend your configuration.yaml according to the solution: #129526 (comment)

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.