ZHA - "Unknown application frame ... This is a bug!" error

[markcs]

The problem

Unable to configure SONOFF Zigbee 3.0 USB Dongle Plus V2.

I see the following errors in the logs:

2024-02-02 13:34:02.478 DEBUG (MainThread) [bellows.ezsp.protocol] Send command networkState: () 2024-02-02 13:34:02.877 WARNING (MainThread) [bellows.ezsp.protocol] Unknown application frame 0x8375 received: b'5998' (b'6264c975835998'). This is a bug! 2024-02-02 13:34:03.873 WARNING (MainThread) [custom_components.localtuya.common] [636...963] Failed to connect to 192.168.1.3: [Errno 113] Connect call failed ('192.168.1.3', 6668) 2024-02-02 13:34:08.479 ERROR (MainThread) [aiohttp.server] Error handling request

This is a brand new Zigbee device running firmware that came with it. This is the first time I've tried to get Zigbee working.

usb-devices gives this info:

T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=02(commc) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=1a86 ProdID=55d4 Rev=04.42 S: Manufacturer=ITEAD S: Product=SONOFF Zigbee 3.0 USB Dongle Plus V2 S: SerialNumber=20231218211506 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=132mA I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm E: Ad=83(I) Atr=03(Int.) MxPS= 16 Ivl=1ms I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm E: Ad=02(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

No response

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

home-assistant_2024-02-02T02-41-32.562Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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)}}

[javicalle]

You have a custom quirk in your HA. Try to remove the quirk and repair the device.

[markcs]

You have a custom quirk in your HA. Try to remove the quirk and repair the device.

Sorry, where would this custom quirk be? How to identify this?

Same issue reported here: https://github.com/home-assistant/core/issues/107828

[javicalle]

Sorry, my fault. I have misread custom_components.localtuya.common as a custom quirk, but it is just the localtuya component (not a quirk) It seems to be related with the linked issue.

[louim-lbs]

Same error:

First:

Source: runner.py:188
First occurred: 14:27:06 (5 occurrences)
Last logged: 14:40:10

Unknown application frame 0x8375 received: b'6698' (b'023acb75836698'). This is a bug!
Unknown application frame 0x59FD received: b'3f' (b'023a89fd593f'). This is a bug!

Second:

Source: runner.py:188
First occurred: 14:27:12 (5 occurrences)
Last logged: 14:40:15

Error handling request

[louim-lbs]

Solved using the same workaround as https://github.com/home-assistant/core/issues/94503#issuecomment-1680771900 Weird behavior though.

[issue-triage-workflows[bot]]

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.