What will happen after HA has an official Sleep as Android integration?

[davux]

Starting with 2025.9, Home Assistant is getting an official Sleep as Android integration. What will happen with this one? Are the two going to coexist?

[davux]

I'm seeing that the core integration is based on webhooks. So one idea is for this integration to be renamed as HA-SleepAsAndroid-MQTT or something around those lines. Surely either approach will have its pros and cons.

Another approach would be to combine the two: the momentum around the core integration, and the stability of this one — by proposing to merge the MQTT functionally into the core integration. More visibility, more functionality.

[ALERTua]

Is there a way to use both the official integration and this one? Their names are the same, and this integration overrides the core one.

[isewise]

I've tried out the new core functionality and I'm really disappointed by it. Other than it easily integrates to HA remotely, I don't like how it publishes events.

The official integration publishes as "event" entities, while this MQTT version publishes as a "sensor" entity.

Reviewing the history of a "sensor" entity is much easier as it provides the "state" during the different blocks of time. Event entities primarily record timestamp data, which isn't very useful if you are reviewing your sleep patterns in HA.

I removed the official and went back to this version.

[sshaikh]

Yes this is pretty jarring and it's a wonder that they didn't take inspiration from the existing integration - although I'd say even intuitively it should be a state and not an event.

Will have to see how if at all my existing automations can be updated.

[sshaikh]

So it wasn't that bad. The state equivalent is {{ state_attr('event.sleep_as_android_sleep_phase', 'event_type')}}, although the states are now (correctly) split across different types.

You can probably restore close to what you want by wrapping the above up in a template sensor.

I think I'm a fan but will see if I wake up tomorrow or not!

[sshaikh]

So turns out I missed the previous state too so knocked up the following template sensor:

{%set tracking = state_attr('event.sleep_as_android_sleep_tracking', 'event_type')%}
{%set phase = state_attr('event.sleep_as_android_sleep_phase', 'event_type')%}
{%if tracking in ['started', 'resumed']%}{{phase}}{%else%}{{tracking}}{%endif%}

[IATkachenko]

It will be better to contribute to official integration to create sensor and make it better, based on our experience.
I am going to move this repo to archive as soon as I switch to official version.

[davux]

Renaming the integration and contributing to the official integration are two separate things @ALERTua, one doesn't exclude the other.

• Contributing code and experience does indeed sound like the right thing to do.
• Renaming the integration ID is also wise for the short term, however there must be a transition process for people who already have the integration. Not sure how this is handled, both at HACS level and at Home Assistant level.

[IATkachenko]

Why? Just rename it for it not to be in a name conflict. The official integration contribution can take months, and this one is working good.

Renaming does not look like simple step -- I'm not sure that it will be smooth. I'm on vacation now and still at 2025.8. Will try to upgrade soon.
I'll rename integration if it will not affect current installations and really simplify life, but for now it looks like users should install new integration from HACS after renaming.
For now (from 2025.8 point of view) there is an issue with DOMAIN and/or manifest.json settings, and we have to migrate to new one to let this integration work at 2025.9 with default.

I'll try 2025.9 soon to check/fix issues and I'm not going to drop this repo before making official integration comfortable to use. But goal for now is to migrate to official version.

[isewise]

Let us know the name of the new integration ASAP. I would like to run both alongside each other if possible

[IATkachenko]

For now I can't find a way to migrate without full reinstallation :(

The name will be sleep_as_android_mqtt. New release with renaming will be in a few days.

[ALERTua]

For now I can't find a way to migrate without full reinstallation :(

The name will be sleep_as_android_mqtt. New release with renaming will be in a few days.

IMO, if you want the safest way, you could modify the current integration to be updated to a new dummy version and display a message that it is deprecated due to the rename. And redirect users to a copy of this repository, but with the new name. So the users could stay on the old repo without updates or migrate when they are ready.
But I don't know whether you want this hustle or not :)

[sshaikh]

I'm having trouble removing the old version. In HACS, I found the card, clicked and then clicked remove in the top right hand menu. But it I still get the "overridden by custom integration" symbol while trying to add it in HA. I also still see the folder in custom_components.

Any tips?

EDIT: deleting the folder did the trick