search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.03k stars 28.28k forks source link

Rainforest Raven integration stuck in "Configuration flow is already in progress" #116878

Closed mtbBrian closed 1 week ago

mtbBrian commented 1 week ago

The problem

I am unable to complete the Rainforest Raven integration setup with my Rainforest EMU-2. The device is hooked up to the Rasp Pi 4 running HA with a USB cable. I have been successfully integrating this unit for 3 years using the HACS integration https://github.com/damienheiser/ha-rainforest-emu2

When the core integration was first released I tried to migrate by removing the HACS integration and adding the core Rainforest Raven one, but was unsuccessful. I can't remember the details of why. I went back to the HACS integration without issue and decided to tackle this another day.

With the update to 2024.5 the HACS integration stopped working. Restoring back to 2024.4.4 got the HACS integration working again. I have been trying to migrate to the core integration without success.

My steps:

  1. Remove HACS integration
  2. Comment out sensor in configuration.yaml
  3. Restart HA (also tried rebooting)
  4. Tried combinations of changing USB ports an rebooting.
  5. Click "Add Integration", select Rainforest Raven
  6. Select usb port with Rainforest EMU identified

I keep ending up with the following message: image

What version of Home Assistant Core has the issue?

2024.04.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Rainforest Raven

Link to integration documentation on our website

https://www.home-assistant.io/integrations/rainforest_raven/

Diagnostics information

No response

Example YAML snippet

# HACS integration sensor commented out
sensor:
#  - platform: rainforest
#    port: "/dev/ttyACM0"

Anything in the logs that might be useful for us?

No logs I have found

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @cottsay, mind taking a look at this issue as it has been labeled with an integration (rainforest_raven) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `rainforest_raven` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign rainforest_raven` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

rainforest_raven documentation rainforest_raven source (message by IssueLinks)

mtbBrian commented 1 week ago

@cottsay, perhaps there is a method to kill or restart the configuration flow? Otherwise, please let me know if there is any other steps I can perform or information I can provide

mtbBrian commented 1 week ago

Updating to OS 12.3 seems to have resolved the issue. After update the device became discovered and available for the integration. Configuration was successful. Cheers