hello,
I noticed that the Grocy addon is still not working since HA 2025.4 ) although a fix is available since sometime.
For your information
Can you please clarify your comment and why you think it’s relevant to the current beta?
Do you mean the community addon or the custom integration?
The add-on has not stopped working for me at any point, but I’d be interested to know if it does have problems.
The custom integration did break with 2025.5.0 due to a dependency on an outdated python component, but this has now been fixed, and a new maintainer has taken over. It should return to HACS imminently, although the repository was archived a couple of weeks ago, which will have issued a repair notification if you have HACS installed.
But overall, if you update to the latest version, it works as it did before. And all this is about a custom component anyway, which is a bit off-topic for this thread.
But is there something I should be concerned about?
2 Likes
The issue is related to the community addon .
The existing github issue … Cannot add items to shopping list-create new shopping list-edit some of items quantity conversion ratio · Issue #476 · hassio-addons/addon-grocy · GitHub
Regards
Please stay on topic. This thread is for Home Assistant built-in beta issues and feedback only. What you’re posting about is off-topic.
2 Likes
ok sorry @Petro , I was thinking it could speedup the availability of this fix .
I realize that the addon is not part of the Core , as the HACS custom integration
Neither are a part of core, neither are managed by home assistant.
as this thread might have a different audience than the Discord beta channel, let me post 2 ‘issues’ I face with the new release 2025.6
sidebar config now is made per user account and received an update in the UI, which in itself seems very nice. It now is saved into the user account, and automatically used wherever you use it, no matter the device. (so, no more editing that menu in each and every device you use)
However, what I fear now, is that as an admin I can non longer completely control what my users will see, other than setting the require_admin flag in the yaml.
Since the sidebar config is now saved in the user account, and users control that themselves, there is no more option for the admin to decide. And users can play around in the sidebar 
do we have a non-edit flag for that…?
sidebar_editable: >
[[[ is_state('input_boolean.sidebar_editable','on'); ]]]
(personally I use custom plugin custom-sidebar that has all of that fixed, but that is another matter, this is about the 2025.6 beta)
Secondly, I am not 100% sure, but there seems to be another change related to this: upon each and every connection after changing from cloud to wifi and vv, I am deferred to the default ui-lovelace.yaml. I have that edited to show a screen of the settings, but most people will probably see the all entities page there.
before, this did not happen as frequently, and many times we could simply continue browsing the app, no matter the connection change. Which of course is as it should be.
The system sees those connection changes as new logins probably, and forces the user to that landing page… (because of that it will also probably be marketed as a fix )
I would appreciate if other beta testers could check this, and confirm or deny what I am seeing
I’m not having that dashboard issue. I’ve noticed with the iOS app, if you leave the app and come back, the view tabs in the top bar no longer redirect you to their page. I haven’t written this up yet, but it seems to be a problem. Simply refreshing the page causes them to work again.
1 Like
There does appear to be some disconnect in the implementation - there are “mobile” settings so I’m not sure why this has not been taken in to account. I’m sure it will all be sorted before go-live 
that could have to do with the connection setting in your profile?
‘verbreek achtergrond verbindingen?’ (Which as you see I have disabled exactly because of that)
I do have that turned on, however this issue occurs whenever the app is closed. Leaving and coming back within the 5 minutes causes tab selection to break. It could be related, however I’d consider it an issue. I also didn’t have this issue prior to the beta.
I’ve opened a quick and dirty Issue in the frontend repo, to get this logged before release
I did discover this bug on the alarm section, normally this would work with a height of 7, but I had to bump it to 8, even then it still doesn’t fit right, previously it was a pill shaped button
yes there has been a change for the alarm panel card.
if you believe it is a bug, then file it as an issue in the Frontend repo, so devs can check, and at least it is registered to be solved
1 Like
btw @MissyQ if this thread will be closed after the beta finishes, will these posts be migrated to the release thread?
asking because I suppose several of the issues raised here wont be fixed before release, and it would be good for people to reference them.
I don’t think she did last time. It was more is is still broke. Raise it and link content if necessary. Release 2025.6 is a different animal than beta 2025.6
1 Like
no
that is rather unfortunate, and a waste of peoples effort and time tbh.
another suggestion then:
why not rename this topic to the release thread and keep all? it would be good for new users of the actual release to see what beta testers have already discovered for them and might tempt more users to join a beta in the future.
The topics for blog posts are automatically generated by the blog post itself and many of the issues found in beta will not be related to the release.
2 Likes
right, I forgot about that, sorry.
that remains to be seen…