ZHA not providing Aqara E1 position

[bromleyman]

The problem

After upgrade from 2025.3.1 to 2025.4.1 all my Aqara E1 position entities are no longer being provided by ZHA.

What version of Home Assistant Core has the issue?

2025.4.1

What was the last working version of Home Assistant Core?

2025.3.1

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

ZHA

Link to integration documentation on our website

No response

Diagnostics information

Nothing abnormal is showing in logs. The only message when clicking on the position entity is "This entity is no longer being provided by the ZHA integration." I have 19 Aqara E! roller blinds and the position entity for each is now unavailable. The operators still respond to cover commands to move to a percentage position but ZHA is no longer providing the current position entity.

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of zha 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 zha 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)}}

---

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

[mib1185]

please follow the Reporting issues guide from the docs, thx 👍

[TheJulianJES]

Please download and attach the diagnostics information for the device. Also take a screenshot of the device page.

There were some underlying changes for this device, but the cover entity that controls all basic functions of the device should still work as expected.

[bromleyman]

Attached are screen shots.

Aqara E1 ZHA screen shots.pdf

When adding these devices using ZHA, two control entities were created - cover and number. I tried adding a new E1 today and now only one control entity is created, just the cover.

I can confirm that my E1 cover entities are working as they should and I have used the current_position attribute in automations rather than the current position number entity. I have mainly used the number entity for dashboard purposes and can no doubt cover all my needs by using, for example, the mushroom cover card.

Thanks for the quick response.

[gasbrake]

Same issue here with most recent update.

[bromleyman]

This issue has set me wondering about exactly what the difference is between using the cover entity and the number (position) entity. The cover entity and its current_position attribute seem to provide all the control and feedback needed for the e1 operator - or am I missing something? Could the position feedback via the cover entity be a bit flaky? I've changed my dashboards to just use the cover entity so time will tell 🤔

[bromleyman]

I'm getting some odd behaviour on a couple of operators. The position attribute of the cover entity suddenly changes from 100% (the actual position) to 0% and the state changes from open to closed. I have to operate the blind to correct the error. There is nothing showing in logs associated with this behaviour. Prior to update to core 2025.4.1 this had never happened in over a year of stable operation of these devices. Is it possible to revert to an earlier version of ZHA without reverting the whole core to see if the problem is with the affected devices rather than any changes to ZHA?

[bromleyman]

home-assistant_zha_log_extract.log

Another issue I have experienced for some time is lockout of an E1 device that has failed to respond to a command from an automation (e.g. to close). In such cases, the only fix I have is to restart ZHA and this always fixes the problem - the offending device immediately becomes responsive again and works perfectly. I have no idea if this is a bug in the E1 device or a bug in ZHA.

The attached log provides an example. The log shows that at 17:23:30 when an automation commanded a group of 6 blinds to close in sequence, two at a time. One of the six did not respond and thereafter was non-responsive to dashboard controls. At 18:36:17 I turned on ZHA debug and made some more attempts to operate the blind in question. At 18.43:03 I restarted ZHA and when that finished, I closed the blind in question. Does this log extract indicate anything useful?

[uhTWO]

I'm having this issue too. It worked perfectly and reported position before the update. Now, HA is saying the integration is not providing that entity.