core: #33302 new Roomba setup - discovered but integration cannot connect

The problem

When trying to get my Roomba980 working with the new way of configuring Roomba devices, the discovery in Integration seems to work (I see the card in Configuration -> Integrations), but when clicking on Configure in the GUI, I need to enter the same information again, that I already provided in the configuration.yml file (IP address, BLID and password). Since I do not have any certificate in my certificate store, I deleted the default value since it is marked as optional in the documentation. When clicking Submit, all entries are deleted and an error messages indicates: Unexpected Error. Unfortunately, I do not see anything in the logs at ~/Library/Logs/homeassistant.log nor in the logs in the GUI at Developer Tools.

Environment

My previous homeassistant installations were running on a Pi3 and on Synology, both in Docker. Attaching my Roomba980 did always work without a problem with previous versions of homeassistant using always the same host IP address, BLID and password. Some weeks ago, I migrated my home assistant installation to macOS running in a Python venv starting with homeassistant v108. I never managed to get my Roomba980 working. I did not continue troubleshooting for long to figure it out, because I knew that v109 would come up with a breaking change for Roomba vacuums.

  • Home Assistant Core release with the issue: v.109
  • Last working Home Assistant Core release (if known): v.108, but in Docker. On macOS in venv, it was not working either.
  • Operating environment (Home Assistant/Supervised/Docker/venv): macOS venv
  • Integration causing this issue: Roomba
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/roomba/

Problem-relevant configuration.yaml

# Vacuum
roomba:
  - host: 192.168.1.19
    blid: 3142xxxxxxxx
    password: xxxxxxxxxxx

Traceback/Error logs


Additional information

hass_roomba_connection_submit hass_roomba_connection_unecpected_error

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

Can confirm also fixed in 109.4.