TheItschi
TheItschi
Same issue here: `C:\Users\yavuz\AppData\Roaming\Python\Python310\Scripts>miiocli dreamevacuum --ip 192.168.100.118 --token xxx info Running command info ERROR:miio.miioprotocol:Got error when receiving: timed out ERROR:miio.click_common:Exception: No response from the device Traceback (most recent call last):...
Same result: `C:\Users\yavuz\AppData\Roaming\Python\Python310\Scripts>miiocli dreamevacuum --ip 192.168.100.118 --token xxx status ERROR:miio.miioprotocol:Got error when receiving: timed out ERROR:miio.click_common:Exception: No response from the device Traceback (most recent call last): File "C:\Users\yavuz\AppData\Roaming\Python\Python310\site-packages\miio\miioprotocol.py", line 199,...
This is the result after I turned the robot off and on again: `C:\Users\yavuz\AppData\Roaming\Python\Python310\Scripts>miiocli dreamevacuum --ip 192.168.100.118 --token xxx status C:\Users\yavuz\AppData\Roaming\Python\Python310\Scripts>miiocli dreamevacuum --ip 192.168.100.118 --token xxx info Running command info...
No, doesn't help. For me looks like the robot goes into kind of sleep mode and ignores requests. However the app is cumming trough.
`C:\Users\yavuz\AppData\Roaming\Python\Python310\Scripts>miiocli dreamevacuum --ip 192.168.100.118 --token xxx status ERROR:miio.miioprotocol:Got error when receiving: timed out ERROR:miio.click_common:Exception: No response from the device Traceback (most recent call last): File "C:\Users\yavuz\AppData\Roaming\Python\Python310\site-packages\miio\miioprotocol.py", line 199, in send...
That make no difference. Still "No response from the device". Again, it looks like if the robot is at the charging station for a while, it's not answering anymore.
Hm, according to a hint in the discussions I changed retry_count in device.py to 20. Now it takes quite long but works.
Still having the same issue, even when putting the key between ''
` - ./windows:/` Hm, that is exactly what's listed as example yaml of the documentation. However, I deleted the volumes section but the error stys the same.
Well, I only installed docker desktop with no other distro on that pc. The distro listed in WSL ist therefore "docker-desktop'. Up to know I had no need to install...