-
Notifications
You must be signed in to change notification settings - Fork 25
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
Tva/fixes #26
base: master
Are you sure you want to change the base?
Tva/fixes #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you fix that single issue and rebase your PR? I'll merge it then, good work! :)
], | ||
"dependencies": [], | ||
"codeowners": ["@nqkdev", "@KrzysztofHajdamowicz"], | ||
"config_flow": false, | ||
"iot_class": "local_polling" | ||
"iot_class": "cloud_polling" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why cloud_polling
?
According to Documentation local_polling
is acceptable value and this integration communicates with vacuum locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does it communicate locally? I thouhght that it sends commands to the xiaomi server and the only way to communicate locally is to root the vacuum, am I wrong?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_LOGGER.info("Initializing with host %s (token %s...)", host, token[:5]) |
It uses IP and token of vacuum to connect locally using Xiaomi protocol.
device_state_attributes