You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 7.6.0 "fixed" #1093 but this now makes events that span multiple days but are not "all day" on the start and end days harder to understand.
The current view looks like this now:
Each of those events all start at "16:00" and run for one or more days and end at 11:00, but they all show as "All Day" with the latest release.
I have many of these calendars and they've all become a lot harder to work with since this change happened. Especially since I share them to a house cleaner so they know when guests have left rental properties. While usually they all have the times I've stated above, sometimes they are different and it's critical for me to be able to show that when I provide these to other people!
Expected behaviour
Previously these sort of events would look more like this:
Is there an existing issue for this?
Current Behavior
Version 7.6.0 "fixed" #1093 but this now makes events that span multiple days but are not "all day" on the start and end days harder to understand.
The current view looks like this now:
Each of those events all start at "16:00" and run for one or more days and end at 11:00, but they all show as "All Day" with the latest release.
I have many of these calendars and they've all become a lot harder to work with since this change happened. Especially since I share them to a house cleaner so they know when guests have left rental properties. While usually they all have the times I've stated above, sometimes they are different and it's critical for me to be able to show that when I provide these to other people!
Expected behaviour
Previously these sort of events would look more like this:
Steps To Reproduce
No response
Mode
Event (default)
Card Version
7.6.1
Home Assistant Version
2023.08.4
Configuration
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: