We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I receive the following message sporadically for my Sinope 4210 devices:
Z2M Server: zh:controller:device: Handling of poll check-in from 0x500b914000051cdf failed (ZCL command 0x500b914000051cdf/1 genPollCtrl.checkinRsp({"startFastPolling":false,"fastPollTimeout":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false,"sendPolicy":"immediate"}) failed (Timeout - 3852 - 1 - 65 - 32 - 11 after 10000ms))
No response
This is a sporadic issue and i have the message for all devices from time to time
1.40.2
7.4.4.0 build 0
EZSP v13
add-on via Homeseer ZigbeePlus plugin
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
I receive the following message sporadically for my Sinope 4210 devices:
Z2M Server: zh:controller:device: Handling of poll check-in from 0x500b914000051cdf failed (ZCL command 0x500b914000051cdf/1 genPollCtrl.checkinRsp({"startFastPolling":false,"fastPollTimeout":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false,"sendPolicy":"immediate"}) failed (Timeout - 3852 - 1 - 65 - 32 - 11 after 10000ms))
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
This is a sporadic issue and i have the message for all devices from time to time
Zigbee2MQTT version
1.40.2
Adapter firmware version
7.4.4.0 build 0
Adapter
EZSP v13
Setup
add-on via Homeseer ZigbeePlus plugin
Debug log
No response
The text was updated successfully, but these errors were encountered: