Closed merdok closed 1 year ago
@0x5e
do you have any tips on how to cause the "user ack timeout"
? I cannot trigger them on any of my devices, and having them to trigger would make it easier to debug this issue.
@0x5e
do you have any tips on how to cause the
"user ack timeout"
? I cannot trigger them on any of my devices, and having them to trigger would make it easier to debug this issue.
If I send command to the mesh device too frequently, It will cause this error. For example, copy 4 commands together and paste to the shell, and enter, then usually failed at the third command...
The thing is that I do not have any mesh devices😅 So I need a reliable way to reproduce it without that. Other then that, if you have coding knowledge and time, could you try to have a look? The code should be in the protocol file.
OK, just give me some time to read the code, I will try.
thanks 👍
I execute 4 commands in one shot: turn off, get status, turn on, get status. Compared with miot and miiocli, miiocli almost never failed, but miot almost failed at the third command every time.
And I switch the first and the third command, still failed at the third command.
Update: I see miiocli's retry_count=3, timeout=5, so I add
--retries 3
for miot, still failed.Here's the data captured from wireshark:
Seems miot retry not correctly working.
Originally posted by @0x5e in https://github.com/merdok/homebridge-miot/discussions/348#discussioncomment-3828503