Open i3laze opened 1 month ago
Hey there @pschmitt, @cyr-ius, @shenxn, @orhideous, mind taking a look at this issue as it has been labeled with an integration (roomba
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
roomba documentation roomba source (message by IssueLinks)
Quick workaround could be exposing and allowing to edit current IP in integration properties:
The problem
I'm duplicating this issue, as it was closed without resolution: https://github.com/home-assistant/core/issues/53941
I have 3 roombas in my house, and for some reason the older one keeps loosing its connection in HA. The logs indicate it can't connect:
2021-08-04 07:30:28 ERROR (SyncWorker_7) [roombapy.remote_client] Can't connect to 10.13.0.36, error: timed out
Upon investigation, the IP for the roomba has changed. Using the roomba-discovery command in the homeassistant container, it does list roomba, but with a new IP. I've successfully shut HA down, edited config/.storage/config.entries and manually updated to the new IP address, restart HA, and things work. But shouldn't HA be able handle the IP changing since the BLID is static, and its still discoverable on the network?
Same story: iRobot got new IP via DHCP. Integration didn't re-discover or pickup new IP, although it has iRobot MAC-address shown all-over UI.
Expected behavior: re-discover previously configured iRobot without mangling with config.entries file
What version of Home Assistant Core has the issue?
core-2024.10.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Roomba
Link to integration documentation on our website
https://www.home-assistant.io/integrations/roomba
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response