-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
no vacuum to select #97
Comments
Ive got the eufy robovac 11c pet edition. Maybe it isn t supported? |
Same issue with the X10 Pro so probably not just you |
I'm currently unable to re-add my vacuums to the integration. This used to work. As posted before, version defaults to v1.0 no matter what is installed. Seeing some errors in debug log (AttributeError: 'RoboVacEntity' object has no attribute 'vacuum'), not sure if related. I had issues and uninstalled the integration, rebooted and reinstalled/rebooted. After that, no luck. |
following - nothing to select here either. own a pair of x10 pros |
following - same issue for the Eufy X10 pro |
following - also with X10 Pro |
I've been looking into this today as I got my X10 Pro earlier. Newer machines don't use the Tuya infrastructure the current release of this uses, and instead uses MQTT on Eufy's own servers. Looks like this is being tracked and worked on in #68. |
following - also with X10 Pro |
1 similar comment
following - also with X10 Pro |
Posting here because unable to create a new issue. I've been unable to use both my old 30C and my new L60 with this integration. Up to like a year ago (maybe less?) everything worked fine on my 30C. I'm able to download the integration in HACS, then add it in integrations. Have tried installing a brand new (for the rest empty) home assistant instance in proxmox; same result. I do see that in the integration page, the version number is 1.0.0 (so in http://:8123/config/integrations/integration/robovac). I seem to be unable to update this at all. Is that normal, or not? |
The text was updated successfully, but these errors were encountered: