-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
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
Feature Request: Switchbot K10+ Pro #1069
Comments
Should work with v4.0.0 |
Thanks for your quick response, but:
And - the tinyurl does not work. |
Did you set the device in your config? Also your deviceId has |
Sorry - i did copy&paste from the App with ":"
|
Can you please remove the device from your config, turn debug mode on under the plugins advanced settings and then post the logs? |
OK - I could solve the problem with help of the debug-log. The DeviceID is not, as usual, the MAC of the device, it is a constant number. I did not understand this from the readme. Thanks for your patience. |
So it is working now? |
Yes, but all K10 running with the same DeviceId - good to have only one. 😊 |
So, one more time. The folowing debug-code appears every two minutes and sets the state to on: [13.10.2024, 09:46:22] [SwitchBot] [DEBUG] Got device status: 360TY420801009805 |
Can you get me debug logs for Thai.
Then I can potentially get it to set the right status. |
Stop in Homekit (Robot in dock, off, but switch was on)
Start in Homekit (Robot starts cleaning)
Stop in Homekit (Robot returns to dock)
Homekit Switch is on again
|
Can you also just getting me all the logs together, there are other logs that the plugin spits out, so I can see how they flow from one to the other? No need to explain in between because we have the above. |
That was the complete Log (start/clean/return to dock). But her again:
|
Problem
New Device K10+ Pro, so far is not supported:
Solution
device: {"deviceId":"360TY420801009805","deviceName":"Bot","deviceType":"K10+ Pro","enableCloudService":true,"hubDeviceId":""}
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: