ZHA unable to create new network when manual backup is selected by accident
Checklist
- [X] I have updated to the latest available Home Assistant version.
- [X] I have cleared the cache of my browser.
- [X] I have tried a different browser to see if it is related to my browser.
- [X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
when setting up a new ZHA network:
Select: "Upload a manual backup", then you will not be able to get out of this menu anymore:
Describe the behavior you expected
I want a back button so I can create a new network instead of forcing me to restore the backup that i accidentally clicked.
Steps to reproduce the issue
See photos
What version of Home Assistant Core has the issue?
Core: 2024.2.2 Supervisor 2024.02.0 Operating System 11.5 Frontend 20240207.1
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Firefox version 123
Which operating system are you using to run this browser?
14.3.1 (23D60)
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
If you just click the X to close the dialog, and restart the configure, does that not work, or are you permanently stuck?
It is permanently stuck. The only way I got it back was to ignore the newly discovered stick, restart home assistant, unignore (is that a word?) the stick, restart home assistant and restart the process.
Sorry to hear that. Might be worth reporting this in home-assistant/core for ZHA integration, I think these configuration flows are mainly designed by the integrations themselves, I think the frontend doesn't have a lot of control over the dialogs that accompany it. If there was going to be a back button I think it would have to be added there.
Cross posted: https://github.com/home-assistant/core/issues/111145. @karwosts do you want to leave this open?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
@karwosts reminder
I think we can close, thanks.