Anyone else having trouble with:
- e.g. “turn light back on” in same conversation, assist tells “turned back on” but kept dark
- sun rise automation didn’t even start (usually does perfectly)
I’m seeing exactly the same problem on my gas graphs. Here’s my theory… It looks like it’s trying to work out how wide to make the bars based on how many calls there are distributed across the whole period (day, week month etc). Day view should show 1 bar per hour but only one of those hours within an (e.g.) 4 period contains a non-zero value, it seems to be assuming that value represents the whole 4 hour period, and it sizes the bar to span it. Then if the next hour has a non-zero value, the graph then realises it’s showing hourly values rather than 4-hourly values, and so it corrects the bar widths.
I suspect it’s more likely to happen on gas graphs since gas consumption tends to be more sporadic (e.g only when heating is on, hot water being used etc) so there are more likely to be periods in the when there is no gas consumption such as during the night, so this is more likely to be observed in the early mornings after the first hour of non-zero consumption is shown in the graph.
That’s correct,I also see it with water usage in the first hour of the day…
First time in a while ive had some problems on upgrading, have searched and cannot find simialr issues. For me a bunch of custom components got removed, HACS being one of them. Had to reset up HACS manually and then download any missing components. Strange.
Hi, I’ve noticed that in both version 2025.2 and 2025.2.1, even when setting up remote backups, a lot of space is still used on the HDD where Home Assistant is installed.
Does this always happen, or only when the transfer fails? Also, is there a temporary folder where the files are stored before being transferred? If so, which folder can I delete them from?
Thanks!
Is it possible to backup to a SSH or SFTP location?
I haven’t tried the new backup system yet, but from what I’m told, the way HA does the back up is to create all the .tar files, and bundle them into the final backup file, locally. Only then is it copied to whatever remote location you specify. This is a good thing for performance, but if you’re tight on local storage it’s a consideration. Also if you’re using an SD card, which are rumored to have a limited lifetime number of write cycles, you’re potentially shortening the life of the card.
After my first experiences with using 2025.2.1, I wanted to give the developers a quick feedback:
Thank you for listening to the community. The new backup system is sooo much better than with 2025.1.X!
If you could now differentiate how many backups are stored locally and how many are stored externally, it would be almost perfect. At least I only know a few who have as much storage on the HA system as on the external storage locations…
2 Likes
good day, thanks for all you effort in this. It looks as if the virtual components from shelly devices GEN3 are not working anymore. I get a fail to set up message.
Fix is ready Bump aioshelly to version 12.4.2 by bieniu · Pull Request #137986 · home-assistant/core · GitHub
2 Likes
I’m piggybacking on this. It would be really cool and a culmination if you could set the number of copies stored individually for each location.
2 Likes
As of this update my dashboard does not fit the screen anymore. Previously it would resize the energy consumption graph a little bit to make everything fit nicely. Now I need to scroll to see the status bar at the bottom (this is a heatpump status if you a curious).
Also, the solar energy (orange in the bar graph) is now on the top of the bar columns which should be a the bottom (as on the picture). Attache image is of the old situation, don’t have a proper screenshot .
2 Likes
Are you using sections?
For the graph card, under layout try removing the value for rows. You will need to do it in the yaml view.
So long as MS treats these as two different things with the same name, it has to be handled as two different things. It would make sense why they started with personal, and they are just using the name MS uses.
Once again a great release! Love the monitor in the Bluetooth integration.
Just an idea: maybe the Bluetooth Company Identifier could be enriched with the company name using this source: [Bluetooth Company Identifiers] Company identifiers are unique numbers assigned by the Bluetooth SIG to member companies requesting one. · GitHub
In this case identifier 76 = 4C hex = Apple Inc.
6 Likes
Put it in a feature request.
1 Like
Graphs.
In 2025.1.x I could use ctrl, left click to select an area of a graph to zoom in on - fantastic just like the great HACS history card . And then I could then use ctrl and scroll to zoom in closer.
In 2025.2.1 I can’t now ctrl, left click to select an area.
Even after refreshing the browser cache. I have tried Chrome and Edge both exhibit the same lack of functionality
I see this in the forums
History graph regression with 2025.2 - Configuration / Frontend - Home Assistant Community
Is this because of the following from the release notes, if so its a backward step of functionality that was only introduced in last months release!
I hope I have just missed something.
Preparing our graphs for the future
This release includes a major overhaul of every graph we display and show in Home Assistant. We have entirely replaced the software library that renders these graphs in the frontend.
You can most definitely tell things have changed, but everything still looks very similar. The latter was our goal for now, as we wanted the existing experience to be familiar.
3 Likes
One of regression of new graphs is that a legend became scrollable - like it is shown here on another person’s post:
The reason is that Echarts themselves allow a legend to overlap a graph:
There is a “padding” property in Docs - but it does not seem to be working to define a vertical gap between a legend and a graph.
Play here as you like.
3 Likes
It was my exact experience after updating from 2025.1.4 to 2025.2.1 just now. It really screwed up my statistics sensors. 