A general reminder: Beta week is not designed to fully overhaul a new feature, but to identify bugs that may be introduced with the update.
If you have an issue, please let us know here! However, the developers are very active in the #beta channel of our Discord server during Beta - it’s good to hop in there if you can. To ensure things are addressed in a timely manner, be sure to also submit issues on GitHub in their proper space:
New tile card features! Several people pulled together to get these added in, a huge thank you to those who helped here. Card improvements include the history chart, fan direction and oscillation controls, a new button card (I’m personally super hyped for this one), valve controls, and setting a date.
New storage insights lets you see what your disk usage looks like at a glance.
New integrations - Sleep as Android, SEKO PoolDose, and ToGrill Bluetooth BBQ thermometers.
Noteworthy improvements to existing integrations - Husqvarna Automower now allows you to reset cutting blade usage time and track error events; Reolink has new volume controls; PlayStation Network allows you to send DMs to your friends; and UniFi switches now have individual switch port control.
The list of backward incompatible changes isn’t large, but there are a couple of important ones. I think the best to call out here are Husqvarna Automower BLE, SwitchBot Bluetooth, and Yale August - but there are a couple more there so check the list out just in case.
Build should already be available for y’all. Happy testing, friends!
Also, update and event entities were added to template integration
While I have not created it myself, I’m fairly sure HA Container users can create update entities for containers running next to HA. I.e. update notifications and popups in the HA interface for other containers, just like addons.
If you have an issue with the beta, create an issue on github and tag the beta as the version.
Secondly, I don’t see any posts from you in the beta channel. I don’t see hundreds of bug reports either, I’m fairly active there. Are you sure you went to the right spot?
Lastly, on the weekend you typically need to wait until monday before people reply (the first work day of the week). Only volunteers reply on the weekend, sometimes you’ll see a random core member post, but understand they are posting on their day off.
Typically, most people avoid documentation aside from the 2 or 3 core members who manage it. Volunteers don’t like documenting, they like coding. So you’ll likely have to wait for the documentation team to get to the issue.
You’re always welcome to just fix the issue with the documentation. It’s fairly easy to do and contributions take priority over issues against the documentation.
If you want to talk something through before creating an issue, you can mention it here or on discord.
No, all bugs are if they are actually bugs (not requests for new features) and the author can provide a way to reproduce the issue.
If your github issue is just “my thing doesn’t work”, not much is going to be done because there’s no information to go off of.
No. If your issue is truely related to a change in 2025.7 then you just should submit a normal bug report if one hasn’t been created. If you already have an issue on github, then you need to wait for a developer to reply. If the integration in question does not have a volunteer code owner, you may be waiting a very long time.
For the 2 HA issues (#1 and #2) You didn’t fill out any of the information that’s requested… You skipped all fields that would assign this to the correct people in order to get a response. All of which is covered when filling out the form.
Your last issue got developer response. You just need to wait for a fix now. Keep in mind bug fixes can take a long time, especially with hardware. It will not be instantly fixed.
Card improvements include the history chart, fan direction and oscillation controls, a new button card (I’m personally super hyped for this one), valve controls, and setting a date.
Happy testing, friends!
