Hello @Svobi95, thank you for opening this issue! 🙏

The culprit of the problem seems to be here:

The same behavior works without problems on DateCalendar, but on the Picker component, this line is stopping the expected behavior.
@flaviendelangle, maybe you know why this particular decision has been taken here? 🤔

The following diff seems to solve the problem:

diff --git a/packages/x-date-pickers/src/internals/hooks/usePicker/usePickerViews.ts b/packages/x-date-pickers/src/internals/hooks/usePicker/usePickerViews.ts
index 4ed9a1a87..e96e3754f 100644
--- a/packages/x-date-pickers/src/internals/hooks/usePicker/usePickerViews.ts
+++ b/packages/x-date-pickers/src/internals/hooks/usePicker/usePickerViews.ts
@@ -183,12 +183,12 @@ export const usePickerViews = <
   TAdditionalProps
 >): UsePickerViewsResponse<TView> => {
   const { onChange, open, onClose } = propsFromPickerValue;
-  const { views, openTo, onViewChange, viewRenderers, timezone } = props;
+  const { view: inView, views, openTo, onViewChange, viewRenderers, timezone } = props;
   const { className, sx, ...propsToForwardToView } = props;
 
   const { view, setView, defaultView, focusedView, setFocusedView, setValueAndGoToNextView } =
     useViews({
-      view: undefined,
+      view: inView,
       views,
       openTo,
       onChange,

Running tests after this change does not produce any failures. 🤔 🤷

@Svobi95 an additional note is that your usage of toolbar slot might result in problems even if the issue was fixed.
Consider reading more about recommended slot usage.

I must admit that I don't remember, and that your fix seems to make a lot of sense...
All the tests are passing, there is no comment above the view: undefined explaining why we don't forward it.
I think that if you can play with it and it does not break, then we can say that there was no big reason hidden behind this code but just a mistake on my side 😆

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@Svobi95: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.