Multi-day events no longer show start or end times
Closed this issue ยท 3 comments
Is there an existing issue for this?
- I have searched the existing issues
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
type: custom:atomic-calendar-revive
name: 8616 Calendar
enableModeChange: true
entities:
- entity: calendar.rental_control_h3_8616
color: red
icon: mdi:home-clock
firstDayOfWeek: 0
maxDaysToShow: 360
refreshInterval: 60
sortByStartTime: false
showCurrentEventLine: false
showMonth: true
showWeekDay: true
showFullDayProgress: true
showEventIcon: true
showNoEventsForToday: true
disableCalLink: true
disableClaEventLink: true
disableEventLink: true
showHiddenText: false
showDate: true
hideFinishedEvents: false
showRelativeTime: true
showLocation: true
dimFinishedEvents: true
showProgressBar: true
showMultiDayEventParts: false
compactMode: false
hoursOnSameLine: false
showAllDayEvents: true
showTimeRemaining: true
showDatePerEvent: false
showAllDayHours: true
showEventDate: true
showMultiDay: false
offsetHeaderDate: false
Relevant log output
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Ok great thanks for the info I'm hoping to look at this tomorrow.
๐ This issue has been resolved in version 7.7.0 ๐
The release is available on GitHub release
Your semantic-release bot ๐ฆ๐