ZHA `KeyError: relay_click_in_on_off_mode` with custom Inovelli quirk on 2026.8

[quhar]

The problem

After updating to 2026.8 ZHA was not able to initialize. Looks like a communication issue with the Sonoff Zigbee Dongle-E stick. After rollback to 2026.7.4 everything works.

What version of Home Assistant Core has the issue?

2026.8.1

What was the last working version of Home Assistant Core?

2026.7.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

zha

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

zha.log

[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, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@quhar Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20zha%22%20
To help us troubleshoot, please include the following information in your report:

1. Please enable ZHA debug logging, let it run for 10-15 minutes, and make sure to capture whatever problem you're having in the debug log.
2. Download diagnostics JSON for the ZHA Integration for the specific devices you're having problems with.
3. Any issues whatsoever with Tuya devices or device support requests in general need to be made in the ZHA quirks repo https://github.com/zigpy/zha-device-handlers/issues, not Core's issue tracker.
4. Fill out the issue template and include whether or not you're using a VM/Proxmox with USB passthrough, what addons you have installed, and so on.

ZHA does not have low-level control over your network, the mesh is self-organizing. If you started having network issues in a specific release, the release probably didn't cause the issue. Check your environment for new sources of 2.4GHz interference and make sure you're using an extension cable, not placing the coordinator near SSDs and USB 3.0 ports, etc. Just because things worked in the past with a bad setup doesn't mean they'll keep working in the future.
_{^{(message by IssueContext)}}

---

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

[eurowabbit]

i get this on the zha integration page...

[puddly]

@eurowabbit Can you open a new issue and fill out the issue template? Include a debug a log as well.

[TheJulianJES]

@quhar Can you please drag-and-drop the custom Inovelli quirk(s) you have installed at /config/zhacustomquirks into the GitHub comment field here, so we can take a look at it? Afterwards, please remove it from that directory and restart Home Assistant Core.

We'll take a look at further hardening ZHA, so (broken) custom quirks that remove attributes don't prevent ZHA from loading completely, but at least you'd currently find broken custom quirks this way if you forget about any 😅. PR for fixing a part of this crash in ZHA:

• Fix discovery crash from quirk removing ZCL attributes zigpy/zha#788

Please also report if the upstream quirks are missing any features/entities. If they do, please try reconfiguring the device from the device page first. Otherwise, let us know here.

[quhar]

Thanks. I didn't realize that this could have been caused by the quirks. Please find them attached. And yes, after removing them I was able to upgrade to 2026.8 without any issues. Thank you!

init.py

VZM32SN.py