Entities are no more available after upgrading to 4.0.0

[lionellem]

Hello,
I have upgraded HACS integration to 4.0.0 without changing anything on my airsend.yaml. My spurl is also still in the secrets.yaml. Both files are still in the /config folder.
But now all my entites are marked as "no more provided by Airsend integration".
I have removed the full integration and restarted the installation of the HACS integration from the beginning but again I have 0 entities under Airsend integration despite the fact that I have listed 9 covers in the airsend.yaml file.

The only difference between the airsend.yaml generated from airsend.cloud and my old one is that my old one has the option
wait: true
But even though i remove it, my covers still do not appear as valid entities.
Thank you very much in advance for your help. I extensively use your solution to automate my covers at home, for example I close them when it is too hot. I am looking forward to making this integration work again. Or please provide the older version as it was working perfectly for me but unfortunately I have not saved it before upgrading.

[mathieuruellan]

I've a similar behaviour: on ha upgrades.my airsend entities become unavailable. I have to reconfigure the integration and they are back. I speak about that in #30.
I'm waiting for the next update to see if the issue still occurs.

[38decibel]

Hi, thanks for the detailed report!

Version 4.0 introduced a config flow (UI-based setup) which changes how the integration is loaded.

Please follow these steps:

1. Remove the old YAML reference from configuration.yaml

If you have this line in your configuration.yaml, remove it:

airsend: !include airsend.yaml

The airsend.yaml file itself stays in /config — do not delete it.

2. Restart Home Assistant

3. Add the integration via the UI

Go to Settings → Integrations → Add integration and search for AirSend.

The internal URL will be auto-detected if the AirSend addon is running. Confirm and your 9 covers should appear automatically.

4. If covers still don't appear

Check that your airsend.yaml has the correct structure with a devices: section:

devices:
  My Cover:
    type: 4098
    spurl: !secret spurl
    channel:
      id: 25455
      source: 94311

The wait: true option is still fully supported, it should not cause any issues.

Let us know if this solves the problem!

Daniel

[Passific]

I installed a few day back the integration (on commit b688219 I presume) through the UI.
But as of 4.0, the first released version, all previous entities are unavailable, while they all have been duplicated with a _2 at the end.
I hope they don't duplicate every restart.

[38decibel]

I installed a few day back the integration (on commit b688219 I presume) through the UI. But as of 4.0, the first released version, all previous entities are unavailable, while they all have been duplicated with a _2 at the end. I hope they don't duplicate every restart.

Hi, I assume you keep you the line in your configuration.yaml

airsend: !include airsend.yaml

In this case please delete it.

[Passific]

Hi, I assume you keep you the line in your configuration.yaml

airsend: !include airsend.yaml

In this case please delete it.

There was no need for this line, I have never set it.

[38decibel]

Hi, I assume you keep you the line in your configuration.yaml
airsend: !include airsend.yaml

In this case please delete it.

There was no need for this line, I have never set it.

Did you wrote the airsend device config directly in your configuration.yaml ?

If yes, please move it to specific airsend.yaml file in config folder.
If not, please share your config details.

[Passific]

Did you wrote the airsend device config directly in your configuration.yaml ?

If yes, please move it to specific airsend.yaml file in config folder.
If not, please share your config details.

I have nothing related to AirSend in configuration.xml.
I juste have the airsend.xml with box and devices, and integration was configured through the UI.
I guess after the update they somehow change of UUID.

Edit: I changed the screenshot as it was misleading

[38decibel]

Thnks for screenshots.
Try to remove the integration completely (don't delete your yaml file, keep it in config folder), then please reinstall it from HACS

[Passific]

I removed and reinstalled the integration. No more duplicate (this is expected) but I have now only the new ones. I renamed the entities name to remove the _2 and it looks like it's working.
Note that during this process I discovered that in fact the deviceID changed, that may have caused the duplication.

[alainvdu69]

yes, i confirm that the upgrade silently create new cover entities with _2 ... and all what you do with the original names stop working.
so i have to delete the original cover names, restart HA, and remove the _2 for the actual cover names to have all working back.

[38decibel]

Hi,

This issue is caused by a specific situation: a version of the integration with manifest.json set to 4.0.0 was available before the official v4.0.0 release tag was published on GitHub. If you installed during that window, HACS later treated the tagged release as an "update" and reinstalled the integration on top of the existing one — leaving Home Assistant with duplicate entity entries in its registry (hence the _2 suffix or the "no longer provided" status).

Fix — one-time cleanup

This is a registry cleanup, no changes to your airsend.yaml or secrets.yaml or in source code are needed.

For everyone in this case, please follow this steps:

1. Go to: Settings → Devices & Services → AirSend
2. Delete all duplicate or unavailable entities (those ending in _2 or marked as "no longer provided")
3. Delete any duplicate device entries if present
4. Restart Home Assistant

The integration will re-register cleanly and your original entities will be restored.

Daniel