-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
viomi v8 #296
Labels
Comments
It seems that this vacuum has a problematic data from a last cleaning. Full cleaning should fix this issue. One more thing: your config puts unnecessary stress on your HA instance, I recommend to use following one: camera:
- platform: xiaomi_cloud_map_extractor
host: 192.168.209.108
name: camera_in
token: !secret in_token
username: !secret xiaomi_cloud_username
password: !secret xiaomi_cloud_password
force_api: viomi
attributes:
- calibration_points
scan_interval:
seconds: 10
- platform: xiaomi_cloud_map_extractor
host: 192.168.209.110
name: camera_ian
token: !secret yan_token
username: !secret xiaomi_cloud_username
password: !secret xiaomi_cloud_password
force_api: viomi
draw: ['all']
attributes:
- calibration_points
scan_interval:
seconds: 10 |
thanks, I will try. |
thank you very much. Everything is ok. |
Let's keep this open as this error should have been handled by the integration. I will close this issue when a proper solution will be merged in code |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Checklist
The problem
Hi! I have two identical viomi.vacuum.v8. First of them works fine, but second don't give any data from map cart extractor. How I can resolve the isue?
What version of am integration has described problem?
v2.2.0
What was the last working version of an integration?
No response
What vacuum model do you have problems with?
viomi.vacuum.v8
What version of Home Assistant do you use?
2022.5.5
What type of installation are you running?
Home Assistant OS
Camera's configuration
Errors shown in the HA logs (if applicable)
Additional information
No response
The text was updated successfully, but these errors were encountered: