core: Unknown Cluster Errors & Unexpected Response filling log file
Home Assistant release with the issue:
0.87.0
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Hass in VM Environment Linux ha 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
Component/platform:
Description of problem:
Seeing Unknown Cluster Errors & Unexpected Response consistently throughout the log file. The Unexpected responses is immediately followed by Unknown Cluster. Both appear to be in relation as they come in the same for each occurrence. The ‘TSN=##’ is different for each log entry. Have not been able to correlate
If needing additional logging, please reach out via PM outlining how to enable to capture.
Displayed Errors:
[0x9351:2] Message on unknown cluster 0x0001
7:17 AM util/async_.py (WARNING)
Unexpected response TSN=103 command=266 args=b' \x00 \x1b'
7:17 AM util/async_.py (WARNING)
[0xb077:2] Message on unknown cluster 0x0001
7:12 AM util/async_.py (WARNING)
Unexpected response TSN=51 command=266 args=b' \x00 \x1b'
7:12 AM util/async_.py (WARNING)
[0x345b:2] Message on unknown cluster 0x0001
7:07 AM util/async_.py (WARNING)
Unexpected response TSN=24 command=266 args=b' \x00 \x1b'
7:07 AM util/async_.py (WARNING)
[0xa0fa:2] Message on unknown cluster 0x0001
7:06 AM util/async_.py (WARNING)
Unexpected response TSN=35 command=266 args=b' \x00 \x1b'
7:06 AM util/async_.py (WARNING)
Log File Output:
2019-02-11 07:06:23 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=35 command=266 args=b' \x00 \x1b'
2019-02-11 07:06:23 WARNING (MainThread) [zigpy.endpoint] [0xa0fa:2] Message on unknown cluster 0x0001
2019-02-11 07:07:38 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=24 command=266 args=b' \x00 \x1b'
2019-02-11 07:07:38 WARNING (MainThread) [zigpy.endpoint] [0x345b:2] Message on unknown cluster 0x0001
2019-02-11 07:12:14 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=51 command=266 args=b' \x00 \x1b'
2019-02-11 07:12:14 WARNING (MainThread) [zigpy.endpoint] [0xb077:2] Message on unknown cluster 0x0001
2019-02-11 07:17:40 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=103 command=266 args=b' \x00 \x1b'
2019-02-11 07:17:40 WARNING (MainThread) [zigpy.endpoint] [0x9351:2] Message on unknown cluster 0x0001
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Traceback (if applicable):
Additional information:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 26 (15 by maintainers)
@dshokouhi the unexpected response messages happen sometimes from retransmissions of messages and can be safely ignored. I am going to talk to the other folks about making these debug instead of warning so that we can avoid the log noise.
the other message is a timeout during reconfiguration. It works still because it was already successfully configured from when it joined. There is no need to reconfigure the devices from the “unexpected” warnings.
Again, these aren’t errors. We’ll see what we can do to change the log level to reduce the noise in the logs.
I saved it… go ahead and kill it if you want.