Checklist
Describe the issue you are experiencing
Hi,
I hope this is the right place to report this. I'm a bit unsure if this is a bug or the intended way how the dashboard should be displayed when casting. Anyway it is a change in behavior compared to versions earlier than HA 12.0.
When I'm castin a dashboard to a Google Nest Hub the setting max_columns is not respected.
These are test dasboards I create to illustrate the problem.
Sections view with 2 sections:
This looks as expected.

- type: sections
max_columns: 2
title: Test 2 sections
path: test-2-sections
icon: mdi:format-columns
sections:
- type: grid
cards:
- type: heading
heading: Ny sektion
- type: entities
entities:
- entity: light.kok
- entity: light.koksbord
- entity: light.soffbelysning
- type: grid
cards:
- type: heading
heading: Ny sektion
- type: media-control
entity: media_player.kd_55xe8096_2
Sections view with 3 sections:
Here the three sections are shown side by side. I expected the 3rd section to appear below the first section.

- type: sections
max_columns: 2
path: test-3-sections
icon: mdi:format-columns
title: test-3-sections
sections:
- type: grid
cards:
- type: heading
heading: Ny sektion
- type: entities
entities:
- entity: light.kok
- entity: light.koksbord
- entity: light.soffbelysning
- type: grid
cards:
- type: heading
heading: Ny sektion
- type: media-control
entity: media_player.kd_55xe8096_2
- type: grid
cards:
- type: heading
heading: Ny sektion
- type: entity
grid_options:
columns: 12
rows: 2
entity: binary_sensor.diskmaskin
Describe the behavior you expected
Here is a view from before 12.0 where the view contains 4 sections and the max_columns=2 is respected. The last section with the "Back" button has a colspan to take up the full width.
Steps to reproduce the issue
- Create a dashboard with 3 sections
- Use max_columns=2
- Cast to a Google Nest Hub
...
What version of Home Assistant Core has the issue?
2025.12.3
What was the last working version of Home Assistant Core?
2025.11.3
In which browser are you experiencing the issue?
Google Nest Hub (Gen2)
Which operating system are you using to run this browser?
Google Nest Hub (Gen2)
State of relevant entities
Problem-relevant frontend configuration
JavaScript errors shown in your browser console/inspector
Additional information
No response
Checklist
Describe the issue you are experiencing
Hi,
I hope this is the right place to report this. I'm a bit unsure if this is a bug or the intended way how the dashboard should be displayed when casting. Anyway it is a change in behavior compared to versions earlier than HA 12.0.
When I'm castin a dashboard to a Google Nest Hub the setting max_columns is not respected.
These are test dasboards I create to illustrate the problem.
Sections view with 2 sections:

This looks as expected.
max_columns: 2
title: Test 2 sections
path: test-2-sections
icon: mdi:format-columns
sections:
cards:
heading: Ny sektion
entities:
cards:
heading: Ny sektion
entity: media_player.kd_55xe8096_2
Sections view with 3 sections:

Here the three sections are shown side by side. I expected the 3rd section to appear below the first section.
max_columns: 2
path: test-3-sections
icon: mdi:format-columns
title: test-3-sections
sections:
cards:
heading: Ny sektion
entities:
cards:
heading: Ny sektion
entity: media_player.kd_55xe8096_2
cards:
heading: Ny sektion
grid_options:
columns: 12
rows: 2
entity: binary_sensor.diskmaskin
Describe the behavior you expected
Here is a view from before 12.0 where the view contains 4 sections and the max_columns=2 is respected. The last section with the "Back" button has a colspan to take up the full width.
Steps to reproduce the issue
...
What version of Home Assistant Core has the issue?
2025.12.3
What was the last working version of Home Assistant Core?
2025.11.3
In which browser are you experiencing the issue?
Google Nest Hub (Gen2)
Which operating system are you using to run this browser?
Google Nest Hub (Gen2)
State of relevant entities
Problem-relevant frontend configuration
JavaScript errors shown in your browser console/inspector
Additional information
No response