Open grkhr opened 1 year ago
The error just means that the device did not respond to the request. If your vacuum is disconnected from the cloud, could you try if other commands work?
@rytilahti Do you mean Xiaomi Cloud?
@grkhr yes, some devices are known to become unresponsive when they have no connection to the cloud, some other known issues can be found at https://python-miio.readthedocs.io/en/latest/troubleshooting.html . Generally speaking, these errors can be really hard to debug without accessing the device by rooting it and looking into the logs what is happening.
@rytilahti Got you. But this device is connected to the cloud and the control is working perfectly via mobile app. I'll try to reset it a bit later, may be it will help.
Same issue happening here!
root@b80231cbdc3c:/# miiocli -d roborockvacuum --model roborock.vacuum.s5 --ip 10.75.0.208 --token ************************ info
INFO:miio.cli:Debug mode active
DEBUG:miio.miioprotocol:Got a response: Container:
data = Container:
data = b'' (total 0)
value = b'' (total 0)
offset1 = 32
offset2 = 32
length = 0
header = Container:
data = b'!1\x00 \x00\x00\x00\x00\x0f\x9d\x90\x82fU\x83\x91' (total 16)
value = Container:
length = 32
unknown = 0
device_id = unhexlify('0f9d9082')
ts = 2024-05-28 07:11:13
offset1 = 0
offset2 = 16
length = 16
checksum = b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' (total 16)
DEBUG:miio.miioprotocol:Discovered 0f9d9082 with ts: 2024-05-28 07:11:13, token: b'ffffffffffffffffffffffffffffffff'
DEBUG:miio.miioprotocol:10.75.0.208:54321 >>: {'id': 1, 'method': 'miIO.info', 'params': []}
DEBUG:miio.miioprotocol:Retrying with incremented id, retries left: 3
# ....
ERROR:miio.miioprotocol:Got error when receiving: timed out
DEBUG:miio.click_common:Exception: No response from the device
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/miio/miioprotocol.py", line 193, in send
data, addr = s.recvfrom(4096)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/miio/miioprotocol.py", line 193, in send
data, addr = s.recvfrom(4096)
socket.timeout: timed out
04:17:26.102069 IP 10.75.0.1.59939 > 10.75.0.208.54321: UDP, length 32
04:17:26.102117 IP 10.75.0.1.59939 > 10.75.0.208.54321: UDP, length 32
04:17:26.102142 IP 10.75.0.1.59939 > 10.75.0.208.54321: UDP, length 32
04:17:26.104279 IP 10.75.0.208.54321 > 10.75.0.1.59939: UDP, length 32
04:17:26.104365 IP 10.75.0.208.54321 > 10.75.0.1.59939: UDP, length 32
04:17:26.105072 IP 10.75.0.208.54321 > 10.75.0.1.59939: UDP, length 32
04:17:26.107518 IP 10.75.0.1.46166 > 10.75.0.208.54321: UDP, length 96
Describe the bug Roborock S5 max (roborock.s5e) not working properly. See the logs.
Version information (please complete the following information):
Device information: If the issue is specific to a device [Use
miiocli device --ip <ip address> --token <token> info
]:miiocli device info
not working :)To Reproduce Steps to reproduce the behavior:
miiocli cloud list
mirobo discover
to make sure that the device exists in the networkmirobo --ip ip --token token info
Console output