Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some helpers fail to load in UI until a page refresh #126927

Closed
HarvsG opened this issue Sep 27, 2024 · 7 comments
Closed

Some helpers fail to load in UI until a page refresh #126927

HarvsG opened this issue Sep 27, 2024 · 7 comments

Comments

@HarvsG
Copy link
Contributor

HarvsG commented Sep 27, 2024

The problem

This is possibly a front-end issue.
I am assuming it is a core issue - because it doesn't happen for most helpers - so I therefore assume it is an issue with how components do or do not update the entity registry.

Whilst generating a config flow for the Bayesian Integration in #122552 I came across a re-producible issue with it and several other, in-production config flows.
For some helpers, when a new helper is added it displays an error on the page until the page is refreshed.

Issue with group:

Recording.2024-09-27.153342.mp4

Same issue with integral, also showing page refresh at the end:

Recording.2024-09-27.153527.mp4

What version of Home Assistant Core has the issue?

core-2024.11.0.dev0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Group, Integral

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No errors in the logs
No errors in the web browser console

Additional information

Tested on chrome and edge.
Possibly related: #124055
Related forum issue: https://community.home-assistant.io/t/how-to-remove-a-helper-without-entity-id/689704/15

It is possible the issue is somewhere in this function:

async def async_finish_flow(

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (group) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of group 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 group 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)


group documentation
group source
(message by IssueLinks)

@gjohansson-ST
Copy link
Member

While I experienced the same thing. I think this is a frontend issue and not a core issue so think it should be raised there

@issue-triage-workflows
Copy link

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.

@HarvsG
Copy link
Contributor Author

HarvsG commented Jan 6, 2025

Still an issue

@gjohansson-ST
Copy link
Member

Still an issue

I think you can/should close this and open it in the frontend rep instead.

@HarvsG
Copy link
Contributor Author

HarvsG commented Jan 7, 2025

Fixed in 2025.1.0, not sure which version or PR

@HarvsG HarvsG closed this as completed Jan 7, 2025
@HarvsG
Copy link
Contributor Author

HarvsG commented Jan 7, 2025

Likely it was home-assistant/frontend#22237 that fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants