You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logger: root
Source: /usr/src/homeassistant/homeassistant/bootstrap.py:318
First occurred: 4:11:25 AM (1 occurrences)
Last logged: 4:11:25 AM
Uncaught thread exception
Traceback (most recent call last):
File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.8/site-packages/roomba/roomba.py", line 178, in periodic_connection
if self._connect():
File "/usr/local/lib/python3.8/site-packages/roomba/roomba.py", line 164, in _connect
raise RoombaConnectionError("Unable to connect to Roomba at {}".format(self.address))
roomba.roomba.RoombaConnectionError: Unable to connect to Roomba at 192.168.66.66
Additional information
Because roomba crashes in the night on some carpet or something. In the morning the batteries run dry, then you put it on the charger again but Home Assistant won't reconnect/recover it's self after this error. Happens a lot. (Bad for the WAF). Need reboot HA everytime to get it fixed :-(
The text was updated successfully, but these errors were encountered:
Hey there @pschmitt, @cyr-ius, @shenxn, mind taking a look at this issue as its been labeled with an integration (roomba) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)
The problem
Roomba integration goes down easly and does not recover it's self. Do need to reboot HA everytime.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
Because roomba crashes in the night on some carpet or something. In the morning the batteries run dry, then you put it on the charger again but Home Assistant won't reconnect/recover it's self after this error. Happens a lot. (Bad for the WAF). Need reboot HA everytime to get it fixed :-(
The text was updated successfully, but these errors were encountered: