search

merdok / homebridge-miot

Homebridge plugin for devices supporting the Xiaomi miot protocol
MIT License
388 stars 61 forks source link

Stuck on Everything looks good! Initiating property polling! #290

Closed juster-cyber closed 2 years ago

juster-cyber commented 2 years ago

Describe the bug I can't control device. Stuck on [Robot] Everything looks good! Initiating property polling!.

Expected behavior Device fully controllable Your config.json { "devices": [ { "name": "Robot", "ip": "192.168.0.188", "token": "xxxxxxxx", "deviceId": "xxxxxxxx", "model": "roborock.vacuum.m1s", "pollingInterval": 10, "deepDebugLog": true, "micloud": { "username": "xxxxx@xxxxx.com", "password": "xxxxxxxx", "country": "ru", "forceMiCloud": true, "timeout": 10000 }, "buzzerControl": false, "ledControl": false, "childLockControl": false, "modeControl": false, "fanLevelControl": false } ], "platform": "miot" }

Debug log homebridge.log.txt

Additional context I tried to restart the homebridge I tried to reset token and ip for robot With and without Mi account With or without device model and ID

`OS: Windows 10 Home

Homebridge: [v1.5.0] (https://github.com/homebridge/homebridge/releases/tag/v1.5.0)

homebridge-miot v1.2.3

node: 16.15.1 (x64)

npm: v6.1.0`

merdok commented 2 years ago

You need to post a homebridge debug log with the deepDebugLog flag set to true, please have a look here. https://github.com/merdok/homebridge-miot#troubleshooting without that i will not able to help you.

juster-cyber commented 2 years ago

You need to post a homebridge debug log with the deepDebugLog flag set to true, please have a look here. https://github.com/merdok/homebridge-miot#troubleshooting without that i will not able to help you.

how to do this?

merdok commented 2 years ago

Just have a look at the link which i posted. It has the exact shell command to start homebridge in debug mode.

juster-cyber commented 2 years ago

okie. Anyways i will be afk for a couple of days homebridge.log.txt

merdok commented 2 years ago

Your ip or token is incorrect since based on the logs the handshake with the device is failing.

juster-cyber commented 2 years ago

But the IP and token are correct! I also tried using a third -party utility ( token extractor ) so with the utility built into the plugin, anyway!

merdok commented 2 years ago

I also see a lot of Error: The device with id xxxxxx could not be found on the ru server! Please make sure that the specified micloud country is correct! I would recommend to recheck that.

juster-cyber commented 2 years ago

Ok, i deleted id from plugin but it still doesnt work homebridge.log (4).txt !

merdok commented 2 years ago

As i already mentioned handshake timeout which appears in your log means either token or ip is incorrect.