-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZHA: Unknown application frame
warning
#94614
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
What exact radio hardware/stick are you using for Zigbee? Can you upload diagnostic JSON for the ZHA integration? |
I am not sure if we're experiencing the same error but in my logs is the below. This (Zigbee devices stop working/reporting) started to happen as soon as I upgraded to the latest 2023.6.2 and for whatever reason I also can't revert the setup to the previous to try downgrading it. If I had enough time/patience during the week I would try to stand up another VM but this has already been a week. Essentially if I reboot the entire VM cold, the zigbee integration works for... under an hour, then stops and won't until rebooting the VM again. Z-wave is working on the same stick seemingly without issues for now.
I think I also see... is any of this helpful? never contributed a bug report before.
|
I am having a similar issue as well. I was using a Nortek Zigbee/Zwave stick and noticed since 6/10/23 many zigbee devices not responding to automations or manual toggling. Sometimes it would respond to on/off on a 5-10 second delay, sometimes the devices wouldn't respond to any toggle. System: To eliminate my build/config, or physical hardware, I purchased a Sonoff 3.0 Zigbee device and built a new HA VM from scratch. The only configuration I made on the new build was add the ZHA integration and configure with the Sonoff 3.0 (Nortek is unplugged). I scanned and paired a few zigbee devices and am experiencing the same issue. This is a completely new build, all up to date. System: I have attached my log file with ZHA debugging turned on. Please let me know if there is anything I can help provide for further diagnosis. |
@jgandhi19 accurately describes what I am experiencing. I built a new VM and installed 2023.6.1 - after a little finagling zigbee is back to stable. Stability for me looks like this setup: |
@octomobiki so downgrading to 2023.6.1 resolves the issue for you? |
@jgandhi19 Your log has the following warning: 2023-06-16 11:37:46.312 WARNING (MainThread) [zigpy.application] Zigbee channel 15 utilization is 97.39%!
2023-06-16 11:37:46.314 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc. In the same vein, in one hour 1500 packets refused to send because of interference. I suggest you follow the advice in the warning. You can migrate your network to a new channel but it would be easiest to fix the environmental problem responsible for this. This behavior is not controlled by ZHA, nor can it be changed with software. It's built into the firmware on your stick. |
this is correct, however, 2023.6.2 I could not get to downgrade at all. it just wouldn't do anything. I had to make a new VM to get 6.1 on there. |
Thank you @puddly, I had noticed that error as well. I will review best practice for channel utilization and change to the more optimal channel. I will report back with my findings. Thank you for confirming @octomobiki. I will consider setting up an environment with 2023.6.1 to see if that resolves the behavior as well. I'll try to keep the same variables in play just to see if the only change being HA version. I'm hoping that will assist pinpointing where the issue might lie. |
There were few changes between 2023.6.1 and 2023.6.2, with the only ZHA change fixing a bug with a button in the frontend. Anyways, let's move these discussions to separate issues. If you're not seeing |
@jgandhi19 I opened up #94733 |
I wanted to provide an update after adjusting my zigbee channel. Almost instantly after I made that change (set channel to auto, it went to 20) my issues went away. I apologize that my issue appears not related to the original post; the timing looks to be coincidence in my instance. I am assuming some other outside factors may have caused a tipping point for channel 15 (neighbors wireless, etc.) although I've been running this setup for over a year. Thank you everyone who chimed in and helped me get to the right path. This was a helpful experience and another +1 for such a great community! |
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. |
The problem
Hello
I have recently installed Zigbee, so I don't know if it is a 2023.06.1 error.
In the logs there are several errors:
Logger: bellows.ezsp.protocol
Source: runner.py:179
First occurred: June 13, 2023 at 8:26:54 PM (228 occurrences)
Last logged: 11:29:55 PM
Unknown application frame 0x0208 received: b'8067' (b'00800008028067'). This is a bug!
What version of Home Assistant Core has the issue?
2023.06.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Zigbee
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: