-
Notifications
You must be signed in to change notification settings - Fork 1
Common Errors
This behaviour is usually caused by other third-party plug-ins connecting to the Roomba via MQTT. Unfortunately, all Roombas only seem to support one client at a time, disconnecting any other clients trying to connect.
To eliminate this nasty behaviour, you must choose which plug-in you will use to manage your Roombas. (Hopefully this one)
Example:
[13/07/2024, 10:44:00] [iRobot] Roomba Roomba went offline...
[13/07/2024, 10:44:00] [iRobot] Roomba Roomba connection closed.
[13/07/2024, 10:44:01] [iRobot] Successfully reconnected to roomba Roomba
[13/07/2024, 10:44:01] [iRobot] Roomba Roomba connection closed.
[13/07/2024, 10:44:02] [iRobot] Successfully reconnected to roomba Roomba
[13/07/2024, 10:44:02] [iRobot] Roomba Roomba connection closed.
[13/07/2024, 10:44:02] [iRobot] Successfully reconnected to roomba Roomba
[13/07/2024, 10:44:03] [iRobot] Roomba Roomba connection closed.
[13/07/2024, 10:44:03] [iRobot] Successfully reconnected to roomba Roomba
If you recently updated your Smart map, the room switches in HomeKit have most likely yet to be updated with this latest information. When you change the map (or accept suggestions), an internal ID changes and this is stored in Homebridge. To pass the update into Homebridge (and Homekit), you must re-run the room commands via the App.
For now, the only solution is to clear the cached accessory in Homebridge.
Setup
Features
Help/About