New users will probably assign the areas to rooms, hallways, front and back yard and they will have a neat out of box experience with the new dashboard feature. After a few months they will want to make their own dashboards based on other criteria and maybe even ditch the defaults. I think it is great that HA gives a better out of box experience. And we that have years old dashboards did not loose anything in that process.
2 Likes
The more features we get - the better. Not using autogenerated dashboards myself, but they could be a great start for beginners.
I wrote a function years ago which uses a list of key-value pairs and will substitute one for the other. I always run it over a buffer of logs before sending them anywhere. Yes it takes a few minutes to create (just a few) but quite handy once done. Especially if you like to contribute logs and try to help fix things.
The device hierarchy is super-useful @karwosts and has enabled me to nest all of my devices within the āhomeā and āextensionā devices so I can now for the first time remove the double counting and see how much unmonitored consumption there is in these circuits.
However ā¦
Whilst the double counting is resolved in āIndividual devices detail usageā and I can see the untracked consumption, the chart below, āIndividual device total usageā is unchanged and there appears to be no way to see how much the untracked consumption actually is (other than the hour by hour breakdown).
In my example, Extension is a parent of Washing Machine and Cooker, but individual device total usage shows the total for Extension not the untracked Extension - Washing Machine - Cooker, etc.
Maybe it needs to be something that can toggle between showing the totals and showing the net (untracked) totals after taking account of the energy device hierarchy?
1 Like
Yes to start with we only augmented the devices detail graph, and didnāt make any changes to the device total graph.
Iāve played with some ideas for augmenting the total graph e.g. below image, but weāre still thinking about it and reviewing. Maybe it gets updated in the future.
6 Likes
Man I wish I was rich enough for a roborockā¦ Dumb Roombaā¦ Disgusted face as it vacuums my chip crumbs
3 Likes
Shout-out to @joostlek for all his work on SmartThings the last few months! Amazing work! Itās been greatly appreciated!
2 Likes
Iām having exactly the same experience after upgrading to 2025.4.1.
Iāve looked at the UI to revert to 2025.3.4 but my previous backups arenāt listed (2 years worth of backups).
Iāll try accessing via SSH. Fingers crossed my backups are accessible via SSH.
Seems the have the error āSystem is not ready with state: setupā when trying to update or restart from the UI.
Yes, mine were not listed in the web UI either, but they were visible from SSH. I however did not need to restore any backup, I simply downgraded to 2025.3.4 and everything worked as it did before the update. Simply ran the command from the debug SSH session (port 22222 for me):
ha core update --version 2025.3.4
Had the same issue with 2025.4.2 so would probably not suggest trying that one either. Maybe 2025.4.3 but with this being Easter weekend not likely I will have time to install or want to take the risk though I have gotten good at reverting.
Cheers Larry, Iāll give it a go. Just jumping on to manually take a copy of all my configuration files so I donāt lose them if I lose the entire build.
The supervisor seems to have screwed up in the install of 2025.4.1. Even sshing onto my raspberrypi box it comes up with supervisor error (in a state of setup)
That is on the standard port 22 I am guessing. Have you tried port 22222? Do you still get a command prompt? If so you should be able to hopefully get to the backups and download using SCP some other method.
Good luck!
Yeah Iāve sshād onto my home assistant build and backed up all of the config files and taken a copy of my 2025 backups.
The failed supervisor seems to stop me reverting to a backup and also installing a previous version
Yeah can SSH onto the home assistant device and have taken a backup of my config files and my 2025 backups.
Ive just done a hard restart by disconnecting the power so hopefully that kick starts the supervisor back into life.
Guessing you could try ha supervisor repair and see if you get lucky. Your system seems to have been much more affected than mine was. All SSH was working as expected in my case. Glad you were able to get the configs / recent backups off.
Assuming you are confident with what you have it might honestly just be quickest to rebuild and restore.
The hard restart seemed to kick the supervisor back into action. Iāve got the option to upgrade to 2025.4.2 and isnāt throwing errors straight away, so will give that a go.
I also seem to be able to SSH onto the home assistant build with supervisor working, so should be able to revert to an earlier backup or previous version.
All good, was able to update successfully to the latest version.
Cheers for your responses and suggestions.
That is great news! I tried 2025.4.2 and it still had the identical issues for me, hoping 2025.4.3 just fixes it otherwise will need to take a lot more time to dig deep and hopefully find the root cause.
Those version numbers are just for HA, not for the supervisor or HAOS. So these updates wonāt affect your issue.
This entire discussion has been around HA versions. Started with the borked 2025.4.1 upgrade and then eventually got the 2025.4.2 to work for him. Does not work for me. I also see the HAOS 15.2 sitting out there but at this point would not consider applying that. Donāt know that I have ever seen a specific supervisor only update.