-
Notifications
You must be signed in to change notification settings - Fork 23
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
Roomba i7+ issues with paho-mqtt 1.5.1 #52
Comments
KeyError solved via issue: #50 and pull request:#51 Home Assistant Evac solved via: home-assistant/core#43594 |
paho-mqtt bumped from 1.5.0 to 1.5.1 via: #47 |
Most of the major issues seemed to be addressed via active pull requests, will monitor those and do some further testing if things become un-responsive again. If anyone else experiences similar issues please post here for troubleshooting. |
Seems to be resolved with the release of 2020.12.0 and the mentioned pull requests. Will monitor but closing for now. |
The problem
With the Roomba I7+, and I would assume any Roomba with a Clean Base, there appears to be an issue with the bump to paho-mqtt 1.5.1 causing some KeyErrors. This causes the Roomba Integration to get stuck in a state when it goes to do the Bin Empty (evac) mode. I've also noticed that the i7 will become un-responsive after a number of hours. Example each morning the Roomba controls no longer function with no error messages or logs but a re-load of the integration resolves it. The latter issue is very hard to reproduce. It appears that paho-mqtt is a requirement for the iRobot Roomba Integration that took me a bit to track down. I have validated that downgrading the version of paho-mqtt resolves the issue.
Might be similar to home-assistant/core#41423 but I couldn't figure out the exact details of what caused that issue and might be erroneous in relation to this issue.
Environment
https://www.home-assistant.io/integrations/roomba/
Problem-relevant
configuration.yaml
NA
Traceback/Error logs
Additional information
There was a previous pull request that was put in to add the Evac state (Bin Empty) into Home Assistant but was closed. home-assistant/core#39913
This change alone won't solve the issue. It also requires and upstream change to roombapy
Adding an Evac state to const.py will solve the KeyError:
However I am not sure that will resolve the Roomba becoming un-responsive after a time, hence opening an issue instead of a pull request. I think ideally the Roomba Integration should be updated to work with paho-mqtt 1.5.1 but I'm not sure that I've caught all the necessary changes required. Currently this is a breaking bug that will stop any Roomba with a clean base from not getting stuck when it runs the empty bin procedure.
The text was updated successfully, but these errors were encountered: