What are the ESPHOME requirements to use assist_satellite.start_conversation.?
I am trying with the Big bobbas firmware on my ESP32-S3-BOX-3s but none is able to do it.
The new area dashboard is indeed nice, but now the problem with (missing) nested areas is coming (again). Fingers crossed to get a solution one day 
Creating one big main area creates too much entities, keeping subareas do not enable to assign the main area temperature to each individual subarea (for example).
1 reply
Great news, now I can drop some of my “global” variables (fields in a dictionary), that were used only in a single script/automation!
Question to mods: does this mean, for trigger-based sensors, every variable is now visible to sensors (and not only top-level variables, as it was before)?
HA Yellow here and update entity update.home_assistant_yellow_radio_firmware also showing as Unknown
Thank you for the update.
I have not been able to spend much time in the whole LLM/voice features HA integrated but the last time I did, voice features on an RPi were essentially too slow to be useful.
Has this changed? Is it worth setting things up or will it continue to lag too much?
Additional question: does the companion app support wake words or is it still on the todo/future list?
Calendars finally work with iCloud (shared) calendars, thank you so much.
Enegry topic, really nice! Just received my IO Meter and found out the Matter get power now with Meross, so what a great day 
Clock card… thanks! But…
The big size is still ridiculously small if you plan to make it a wall clock.
Could we have more options or why do we have this limitation?
I would really like to have a HUGE clock with seconds, and dynamically change the size when we want to add more content like alers, notifications events etc.
Thanks 
I would like to thank you for the successful repair of the Tado integration. It works again without any problems.
Realistically, I just want the ability to restore backups. Ever since backups were screwed with at the start of the year, restoring them no longer works at all. And the ticket for it, although full of "me too"s doesn’t seem to be getting any attention from anyone capable of fixing anything.
1 reply
Thanks for fixing tado!
The continued conversation has a serious side effect. If the voice PE has a false trigger from the TV the assistant keeps on saying sorry I did not understand that and ask you to rephrase the question. The only way to stop it is to mute the TV and be silent. I have tried to say “cancel” or “stop” like I am used to with Alexa. That just becomes yet another “sorry I do not understand that, please rephrase your question”. I am going to end up with a divorce so I have to disable the LLM again. How do you stop this eternal loop from hell?
1 reply
It released around 4 hours ago
+1 thanking you for fixing Tado.
Thanks guys, good job! 
I can’t (no account, want to keep it that way) like and subscribe but wanna let you know that I like it very much and I!m always present at the release parties.
Any documentation for configuration of hierarchy within the energy? Cannot find the way to nest devices under an upstream meter.
1 reply
I noticed that all the elements in a picture-elements card lost their default hold action after updating to 2025.4.
In the previous version, there was an implicit default action of “more-info”) which didn’t need to be added in the yaml.
It seems I will have to go through every element and add the hold action explicitly in the yaml:
hold_action: action: more-info
Not sure this was intentional? I didn’t see anything related to this in the notes, but it did change between releases. I suspect something related to adding the actions into the UI where it’s supported (UI editing is not supported for picture-elements, though I wish it was)
1 reply
This update has broken all of my ONVIF cameras. Well, not quite, but it has renamed all the streams and the dashboard needs to be recreated.
Time card is nice
I would like to have option to add a date to it too in various formats like in those time/date widgets on phones? Also maybe have several such “widgets-cards” to choose from? And current weather too?
Next one is Alarm clock card 
maybe? 
You can assign temperature and humidity sensors to the area itself, by editing the area. Once you have assigned these to an area that will show up in the areas dashboard
Areas dashboard feedback from someone who wants to do opposite - disable Areas in HA for a several reasons:
Philips Hue integration adds its own “hardcoded” Areas to HA and you can’t delete them or persistently rename them because after HA restart or Philips Hue integration reload you will get the same initial Hue Areas names.
Philips Hue Areas (aka rooms and zones) are Hue-specific items and I use them to separate logically lights and switches with their configurations.
It’s also bad for Voice Assistant (I am using Speech-to-text). Those Areas created by Hue integration therefore useless in HA, but the problem is - they are also used in Speech-to-text pipeline which adds more errors.
New experimental Areas dashboard is not for me. I don’t plan to use areas and I don’t like that items automatically move around (I saw it in the demo). The current dashboard works fine for me, I manually add sections, devices, new dashboards if needed.
I don’t like the new area information in 2025.4 in the top left corner when you click on lamp card. Especially if it’s hue lamp because it’s useless for me. Wish I could disable it.
I wish I could disable areas in HA globally. They are pointless for my usecase and also make Voice Assistant experience worse. My other non-hue devices don’t belong to any areas.
edit: it should be Speech-to-Phrase, not Speech-to-text
5 replies
How do I get to that Voice Assistant wizard? I want to know what it does when you use “Focused local processing”.
I want Continued conversation for Wyoming Satellite too at least for timers! (It already can do timers)
like this:
> set timer!
> for how long?
> 2 minutes!
Amazing Roborock update!
I think the areas dashboard is a good start. Here are some things I would like to see:
Top level should be floors. Just show them as blocks. Click on the block goes to a page for that floor.
Each floor page should have one block for each room. These blocks can have one sub block for each type of device. For example, a block for lights that shows how many lights there are and how many are on or off. You should be able to turn all the lights on or off from here. You should be able to go to a room page.
Each room page should have all the entities in that room. As the current one does.
That would be a great next step.
“just works” is what we need smart but “all in one” default dashboard is hard to use. It’s a good improvement toward “smart”. previous design we can always custom dashboard but it will and did take lot of tweaking
The new starting a conversation and continuend conversation features are fantastic. As Frenck said during the release party there are so many great things that can now be done with this. Thank you for this great update.
Please provide a link to the issue.
Provide the config of your sensors or the integrations causing this — and the full log error.
Have you checked GitHub for known issues or created a new one?
2 replies
After the update, I have some error messages in the log (but the function is there) from my Alexa integration (via Amazon Alexa Smart Home Skill - not via NabuCasa) from cover and fan entities.
Can you check this for yourselves? Let an entity run in motion and then these error messages should also appear in your logs.
Looking forward to your feedback, thanks.
Logger: homeassistant.components.alexa.state_report
Quelle: components/alexa/state_report.py:427
Integration: Amazon Alexa (Dokumentation, Probleme)
Erstmals aufgetreten: 08:02:18 (2 Vorkommnisse)
Zuletzt protokolliert: 08:02:18
Error when sending ChangeReport for cover.alle_rollos to Alexa: INVALID_ACCESS_TOKEN_EXCEPTION: Access token is not valid.
Error when sending ChangeReport for cover.schlafzimmer to Alexa: INVALID_ACCESS_TOKEN_EXCEPTION: Access token is not valid.
The tokens are all perfectly fine (before the update without error messages) - I also checked Alexa Developer again.
That new Areas are really great! Huge thanks for that. But if you have A LOT of areas. It gets really crowded. We have each for a room, sometime to bundle elements (Electric Cars, watering/irigation systems, etc.). In total more than 50 areas. I could consolidate a bit, but still too much for “one tiny row”.
Why not give the option to include the floors? That would be even better. So you can navigate Floor → Area… As subpages…
again - thanks a lot!
Perhaps it’s beause the name is “Var” (reactive power) while the unit isn’t “Var” but "var " (all lowercase).
Just installed the update and I have none of these warning at all, not from within the Fronius Integration nor from various modbus yamls.
From your lines it says unit not valid, so you might give it a try. Unsure if unit have to be case sensitive.
this does not work for me neither.
i have sonoff sensors (T° and Humidity) in every room + an aqara one for outdoor, i have the room set and the sensors assigned to each room / area properly, and none shows:
i tried editing the areas dashboard to add them, either in the title or as a regular entity, it’s not even there! example with bedroom 1, the sensor and T° / Humidity entitys are not proposed, despite being assigned to this room
The below link mentioned in the blog doesn’t exist:
https://www.home-assistant.io/integrations/google_ai_conversation
Wanted to see whether this was affecting anyone else first before opening a ticket. From further digging it looks like either the configuration has become case-sensitive in the last update or there’s been a change in measurement units, for reactive power VA-reactive (VAR) you now have to specify it as var even though VAR is what’s usually used for this.
As an aside, if the only thing you’re permitted to have for a reactive_power class unit_of_measurement: is var, why do you need to specify it in the first place?
good catch, completely missed this one, it works!!
thanks
Please provide a link to the issue.
Unable to restore backup with 2025.2.3 "Failed to start restore. Unknown error." · Issue #138511 · home-assistant/core · GitHub
nvm had to reload my UI and clear cache, then it appears when setting up a Device in the Energy Dashboard ^^"
It looks like the current version is a lot more picky about sensor types, classes, and whatnot than previous versions were, see my post earlier about “VAR” vs “var” (var is technically the correct unit but VAR is what practically everyone uses, which makes it annoying to now see var everywhere which looks like part of a Visual Basic declaration rather than a unit of measurement).
Brilliant catch. I had all my areas set up correctly (I thought) but I never knew that setting was there when you go into Area Settings. Temp and Humi now displaying in the new experimental dashboard.
Extremely helpful post. Much kudos. 
You mean this? Home Assistant Voice Preview Edition - Home Assistant
how to add the Temp, etc to the Area Dashboard is mentioned in the Blog too @Haningback @sleveille4 a bit obtuse maybe but it is there (towards the end of the section about the Area Dashboard)…
Want to tweak it? Yes, you can ! You can rearrange, show, or hide entities to suit your preferences. At the top of each area page, temperature and humidity badges quickly indicate room comfort levels, which are configurable in the area’s settings.
Check to see if that entity is working.
Hello
Continuous and start conversation don’t work with Wyoming satellite ( like Assist-Microphone addon) . Is an update planned?
So with the new energy children feature.
If i create a helper > group > sensor > sum and call it “kitchen Power” and add all my energy monitoring plugs for the kitchen.
Then create a helper > utility meter called “Kitchen Energy”
I could then add that to the energy dashboard and set the kitchen plugs with the upstream device been the new “Kitchen Energy”.
Then I could monitor the different areas total power without inflating the power usage ?
EDIT —
I have set the kitchen up as a test.
helper > group > sum “Kitchen Power”
helper > group > integral "Kitchen Power kWh
helper > group > utility meter “Kitchen Energy Day”
Then added Kitchen Energy Day to the dashboard and set all the devices in the kitchen with the upstream the device as the Kitchen Energy Day.
See what happens.
1 reply
First, Congratulations for this long awaited (at least , bye me) EXCELLENT feature!
You guys rock ! 
Bugs (or not yet implemented?)thoses used to work in the “old” automatic dashboard (type: original-states)
WishesAlso add buttons to launch:
Keep up the good work! cheers 
I can only guess from a technical perspective: Decoupling. Some device classes have multiple UoM options, and a UoM can be specified without a device class. So, building in such defaults will create a tight coupling between the two concepts. The way it is it works more generally/generically.
I mean:
In the “legacy” automatic dashboard (type: original-states), scenes used to be shown at the end of the area, which was really great.
So adding it back, (plus also area-assigned automations & scripts), would be really usefull… without being forced to create dozens of virtual button entities, to launch all those things, as a tedious workaround (i already have 3376 entities…)
+1!
For now I’m using markdown + cardmod:
type: markdown
content: "{{ as_timestamp(now()) | timestamp_custom(\"%d-%m-%y %H:%M\") }}"
text_only: true
card_mod:
style: |
ha-card {
text-align: center;
font-size: 45px;
}
ha-markdown {
margin: 13px 0px 13px 0px;
}
Be good to see how that turns out.
I monitor each areas usage, using the undocumented type: energy-sankey (under test) card, using floors and areas, hopefully it will be added to the energy dashboard in the future (with values at each section)
This looks awesome, is it using this GitHub - MindFreeze/ha-sankey-chart: A Home Assistant lovelace card to display a sankey chart. For example for power consumption
But it looks like you are not using a custom card.
Any chance you could post your card yaml.
Edit >
Ah ok it looks like you do just add the card with type: “energy-sankey” mine is just sayig loading though… will see what happens
1 reply
use card mod? then do:
card-mod-more-info-yaml: |
ha-dialog-header: |
.breadcrumb {
{% if is_state('input_boolean.hide_more_info_breadcrumb','on') %}
display: none !important
{% endif %};
}
in a card-mod theme
No, not the custom card, its built in but not documented
Expressed during beta: I love the new Areas Dashboard. The sheer ease with which this is created is magnificent, and looks really beautiful. Again, thanks.
But…
because the number of my areas is way too big for the new default Areas dashboard, I had trouble showing it, and editing it (it’s the main landing page, so even opening the edit menu was a bit of a muscle job…)
what I did is ‘take control’, and move the current Home to the final view on the right (I don’t want that complete overview, but I didnt want to delete it either). That way I can safely click the Areas left menu item.
next, I took out what seems to trouble them, namely the camera entities. All I could see was the swirling icon trying to load them. I have those in a dedicated dashboard anyways, to could do without here. It’s still laggy, but seems swifter without them.
Also, I edited all views/tabs to show the Area icon. All manually, since the initial strategy we have now, does not import these from the area_registry unfortunately. At least I can have a few tabs on mobile now.
By default the new Dashboard is completely unusable for me on Mobile because of lack of space for more than 2, 3 if lucky.
Wish there would have been an organizing strategy per Floor in the main menu bar. That would have solved that from the start.
Now, since I did want to experiment with some landing overview in that first tab, I made it manually.
Main strategy change:
it’s super fast now, and I can at last scroll smoothly in the top menu bar.
Wish those separate area views had a back button though, like the subviews.
Styling needs to be done, and probably needs a bit of modding, but art least now I have it all under 1 click and organized as it suits me:
it wont take out the ease and power of tabbed-card, but for a core default dashboard its pretty neat
1 reply
I mentioned this in the beta thread, but since it’s come up here, just one comment about using areas as the foundation for the default new user front end…
I don’t use areas. Nothing against them, it’s a great option. But I think of my home as a collection of systems (which I must maintain) and not as a floor plan which is managed room-by-room.
I want to see, for example, my entire HVAC system at a glance. Or my sump pumps. Or my networked hardware, etc. If I want to know, say, the temperature in a room, I’ll look at the “temperatures” dashboard. I don’t have or want a dashboard for each room. That also shows me if that temperature is anomalous compared to other temperatures. I don’t care whether or not the light is on in that room.
My point is not that mine is the right way, or that areas is the wrong way.
Just that new users shouldn’t be steered down a path of deciding, up front, how and if they want to organize their entities into areas.
We all started out with just a few devices. Yet in these threads extolling the virtues of a new areas-centric default, it’s implicit that there are already many devices, and someone has taken the time to develop a naming strategy for putting them all in areas.
I just don’t see that as applicable to new users.
For the record, this doesn’t affect me directly. I’ll continue to develop my own dashboards regardless of the default. But this was presented as an idea on which feedback would be welcomed. And I do care about the new user experience, even if I’m not exactly “new” any more.
[Note: I tried the feedback form. It asks for specifics on how the new default dashboard is currently implemented. Not on whether or not it is generally a good direction.]
2 replies
The current default dashboard uses areas right now. All the blurb is referring to is replacing that dashboard, which you already don’t use. These changes won’t impact you and you can set any dashboard type as the overview page. To reiterate my comments in the beta thread:
Default dashboard does not mean overview dashboard, it means the current dashboard literally named ‘default dashboard’.
You did not say any of that other than “it won’t impact you”. I’m just clarifying what default dashboard means because its not clear to me that you understood what I said before.
Just had a play with this, very cool, like you said hope this is added to the energy dashboard soon!
btw, because of this whole manual exercise, I forgot this: would have been great if we could copy a View in a dashboard to another view…
+1 the existing discussion in Frontend from almost 2 years ago 
we can move it, but copy?
Unselect “Recommended model settings” then click submit and a bunch of advanced options will appear, including the one about web search
Don’t think so, I’ve just browsed a bit back and can’t see any. I think it mirrors the energy dashboard so if that doesn’t, assume this Sankey will not also
I’m excited to see progress on the start_conversation action, and I’m hoping that it will soon extend to local assistants for those of us who don’t want to use an LLM and are running everything locally. My use case is very simple, just things like asking me if I want it to close the garage door after noticing it’s been open for a while, processing a yes/no response, and then performing an action.
In version 2025.4
Aqara blind motor lumi.curtain.acn002 not update position in HA. It do , but only for a short time (minutes) 
anyone with same issue ? (It worked in 2025.3) with (Tal Current position entity., it’s aloso missing in 2025.4)
In this screenshot, the water heater is a child of the heat pump. Both report energy usage separately, but the water heater’s consumption is also included in the total reported by the heat pump. With device hierarchy enabled, Home Assistant correctly shows the usage of each device.
Heat pump shows 2kWh, water heater 10kWh. How can a lower value be included in a higher one?
1 reply
Some feedback on the clock…
I want a big clock that will be visible across the room. While the font size does increase, the tile has a very large border making it take up unnecessary extra space.
Please make the text take up most of the tile to optimise screen real estate use.
Thank you!
You guys are the best! Thank you for fix Tado integration in such a short time. I really appreciate the work you guys are putting into this project. 
Thanks. I’ll enable debug to check what is going on.
Hi,
I use ZHA with a Conbee 2 stick and 5x Aqara roller shade driver e1.
In Home Assistant version 2025.3.4 no problems.
In Home Assistant version 2025.4.0 the “Number” slider is unavailable?!
Before update:
After update:
The device “Window coverering type” is also changed after the update from “Drapery” to “Rollershade”:
I was thinking about it but Hue Integration is useful as backup in cases when HA is not available. It’s unfortunate that Hue Integration populates HA with entities like areas you can’t delete or hide.
That feedback link doesn’t work for me, and I never heard about that service.
This forum is just more trustable 
Hi, short question:
what impact does the change in the scope of the variable have if I have defined the same variable “location” in 143 scripts and then use this variable to dynamically address entities and other scripts? Most scripts run in parallel and are used equally for different rooms and almost simultaneously.
Best regards
1 reply
I don’t want to create any new areas and assign devices to them be it Hue light or not. I was trying to get rid of Hue areas entities created by Hue Integration, but it’s impossible.
The biggest problem for me is that those Hue areas entities are used in Voice Assistant (Speech-to-text) templates which is not desirable because of additional errors.
1 reply
Thank you for your response.
From the release notes:
The variables action is no longer restricted to local scopes; it can now update the value of a variable also in outer scopes. If the variable was not previously defined, it will be created in the top-level (script run) scope
…
If you have automations or scripts that use the same variable name in different (previously isolated) scopes, you will need to update them: simply use distinct variable names to prevent any conflicts.
For example:
I trigger a script-chain in the living room while my wife is triggering another script in the kitchen. Both scripts triggers the same script to set a radio station, but the kitchen action will trigger this script before the action in the living room.
So, will the location variable ‘living room’ be overwritten with ‘kitchen’?
3 replies
