Calendar Card: can't select initial_view in UI editor

[mamoel666]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

The dropdown for the parameter "initial_view" only shows three empty items and they have no effect on the configuration. So it's not only a visual problem.

Describe the behavior you expected

I'd like to have the option to select from

• Month View
• Day View
• List View

Steps to reproduce the issue

1. Add calendar card to UI
2. Select entity
3. Try to change initial view

What version of Home Assistant Core has the issue?

2022.3.6

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[sniper6661991]

Same issue On 2022.3.5 Tired chrome and edge

Tried Code editor with following and just blanks the card. type: calendar initial_view: (dayGridMonth, dayGridDay, or listWeek)

• calendar.qwertyuiop
• calendar.abcdefghijk

[atkjedi]

I have the same issue

[jugla]

Same issue. The problem seems to be within src/panels/calendar/ha-full-calendar.ts . As a workaround, in HA 2022.4.2 , you can create a calendar card and select code. E.g. :

initial_view: dayGridMonth
type: calendar
entities:
  - calendar.royan_tides
title: Next tide

In initial view you can put : dayGridMonth dayGridWeek dayGridDay list (value given by const viewButtons)

NB : as you can notice there are 4 possible values, whereas 3 seems to be wanted to be shown

(Same behaviour on windows 11, chrome / edge)

[jugla]

Don't know if it can help: #9993 may solve it.

[jantoney]

@jugla workaround confirmed working and also confirmed still a fault in HA 2022.4.6

#9993 seems to be stuck waiting for #9193 which has now been marked stale and closed... So I don't think it's going to go anywhere

[jugla]

@spacegaier , do you know how to handle this PR #12093 ?

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[thoemmi]

This issue still exists in 2022.8.7

[devedsmith]

Yes, this is still an issue.

[spacegaier]

That is already fixed in the current stable release.