2025.10: Undo, redo, and draw me too

No, I didn’t. I’m afraid of messing everything up.”

There was a message on the GitHub issue I created that someone did this but it was lost again on 10.1 update.

I did it while on 10.1 and all is seemingly well. I guess we’ll find out on the next core update lol

Sidebar now once again removed a crutial function for creating automations. Now you can’t see more than 1 block at a time, forcing you to constantly switch back and forth if you need to compare something or copy

5 Likes

There was pretty much one thing I often used on the media player more info dialog… The volume up and volume down buttons.

So, changing volume on my receiver is now a horrible experience and I’m going to have to make dedicated buttons for that now. Which is a massive waste of space of course.

7 Likes

Is it planned to support copy a line in the automation editor by holding Ctrl and moving the line? This would be amazing.

That config is the config of an entire section, not a card. Could it be you tried to add it as a card?

Do I understand it correctly the multple wake word works for all ESPHome devices? SO not just the Voice PE, but also for example the Atom Echo 5?

Custom wake words would indeed be even greater.

Are there any thoughts on how to integrate the new LG ThinQ energy sensors into the Energy dashboard?

2 Likes

That hotkey combo is usually “select all these items”

Shoutout to the devs for the new release. I enjoy the new automation UI, with the resizable sidebar. It allows me to look at a specific action without losing track of where I am in the sequence. If I need to see the entire automation, I usually just use the YAML view anyways, which also has these little arrows on the side to collapse/expand a particuar section.

The only thing I can suggest is maybe offer a setting to allow user to switch back to the old UI mode - i.e. have the sidebar be inline to the action. Not sure if it means double the work.

Anyways I prefer the new UI and I’m sure I’ll find some annoying quirks which I will feedback to the forum here.

New more information dialog for media player entities - Loss of the incremental volume up and down is a loss of functionality for no apparent reason

3 Likes

Anyone else with a Scrypted instance hosted via HA upgrade to 2025.10.1 to find that their HA motion sensors aren’t triggering in Scrypted anymore?

I have the same question!

Does anyone else have their DAIKIN integrations failing in latest release?

Failed setup, will retry: Cannot connect to host 192.168.10.120:443 ssl:<ssl.SSLContext object at 0x7f646ea8bed0> [[SSL: WRONG_SIGNATURE_TYPE] wrong signature type (_ssl.c:1032)]
1 Like

There appears to be a problem when editing any view on the dashboard using the visual editor. This is hard to describe as I don’t have a screen shot before I updated to 2025.10.1, but I’m not seeing the numbers representing each horizontal stack in a view. This has happened in a past release and was corrected. Let me know if you need additional information.
Thanks!

How about card yaml? Doesn’t look like you have a horizontal stack, it just looks like you have a vertical stack containing 1 layout card.

It would be a lot of YAML code to paste and I don’t want to clog this forum with half a page of code. If I have to revert back to the previous version to get a screen shot I will, but rather not as it screws up some integrations. I’ll just sit tight for now and see if someone else can definitively see the problem.

Thanks!

You can post code which is ‘hidden’ in a drop-down menu.

eg:

Summary
like this

and this

and this

here how:

1 Like

FYI, I have the same problem with a Sonoff coordinator. If “detects” the device but everything seems to work if I don’t touch anything.

HOWEVER, I have tried to “ignore it” and “add it” and both times it essentially nuked my Zigbee network and forced me to restore.

FWIW, I don’t have a SLZB-06M – I have a Sonoff stick.

I think a relevant GH ticket is: 3 SLZB-06M routers re-discovered, but already active · Issue #153394 · home-assistant/core · GitHub → seems like I should be able to safely ignore this discovery, but that didn’t seem to work (ignoring it then took the whole ZHA integration with it). I’ll try again in a few days.

1 Like