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've got the following log on my ZiGate component:
[zigate] - Source EndPoint : b'01' [zigate] - Cluster ID : b'0006' [zigate] - Attribute ID : b'0000' [zigate] - Attribute type : b'10' [zigate] - Attribute size : 1 [zigate] - Attribute data : b'00' [zigate] # encoded : b'018102120210021eefb52c82021102100216021002100210100210021102106f03' [zigate] # decoded : 0181 02 00 0E EF B5 2C 82 01 00 06 00 00 00 10 00 01 00 6F03 [zigate] (@timestamp : 22:15:57) [zigate] BAD LENGTH 33026 != 16 [zigate] # encoded : b'01e0018102120210021eefb82c82021102100216021002100210100210021102116303' [zigate] # decoded : 01E0 01 81 02 00 0E EF B8 2C 82 01 00 06 00 00 00 10 00 01 01 6303 [zigate] (@timestamp : 22:16:02) [zigate] -------------------------------------- [zigate] RESPONSE 8102 : Attribute Report / Response [custom_components.zigate.zigate2hass] ZIGATE SIGNAL : [custom_components.zigate.zigate2hass] - Signal : zgt_signal_update_2c8201 [custom_components.zigate.zigate2hass] - Property : last seen [custom_components.zigate.zigate2hass] - Data : 2018-03-16 22:16:04
Is the bad length error always due to communication transmission issues?
The text was updated successfully, but these errors were encountered:
never encountered such error Can you tell what device is causing it and which ZiGate firmware you're using ?
Sorry, something went wrong.
Xiaomi Door/Window Sensor using ZiGate 3.0d. It's like if batching occurs when communication is not perfect.
No branches or pull requests
I've got the following log on my ZiGate component:
Is the bad length error always due to communication transmission issues?
The text was updated successfully, but these errors were encountered: