-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE REQUEST - add additional attributes #44
Comments
All of that information is reported, and looks to be available in my instance of HA still. If you’re not seeing it, something else is wrong. Can you provide more detail, specifically, what information do you see in HA, where do you see it in HA, and what is your configuration? For the configuration, please replace any usernames and passwords with a single asterisk (*) and please truncate the Google URL, if it’s a public one. I’d also like a copy of the actual file, if you can include that. But please hide anything remotely private in it (e.g. replace place names, person names, and other personal details with nonsense. :)
Thanks!
… On Feb 15, 2022, at 12:06 PM, glassbase ***@***.***> wrote:
HA calendar entities support additional attributes such as message, location, description, start_time and end_time attributes, etc.
Currently your component does not populate them. It would be awesome if you could add those. We could use this additional info to display calendar events start times, etc on dashboards.
(I only tested Google Calendar, but it appears to populate the start_ and end_time with a timestamp of the current or next calendar event.)
Examples in documentation: CalDAV and Google.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
|
Maybe it is my ICS sources?
All attributes on the calendar entity:
|
Whereas, a Google Calendar entity (using the official Google Calendar integration), populates much more attributes:
|
HANG ON, Looks like I somehow have 2 custom integrations for ICS. I appear to be using the other dev's (ics vs ics_calendar) EDIT - switched over to your custom component and seeing same results. |
So to clarify, the calendar works. It shows in the HA calendar menu with all the events at the proper dates and times. All I am really talking about is (hopefully) -- adding the additional attributes to the calendar entity. |
Thanks! I understand, now. This is the same as issue #43. If an event were actually taking place (i.e. offset_reached is true), you'd see the other attributes. You could also try switching the parser to icalevents, but that could introduce other issues, too. The reason I suggest icalevents is that it will return the "next" event, no matter how far in the future and you'll see all the attributes as you expected. This functionality is something I just haven't had time to implement, once I realized the new parser doesn't behave the same as icalevents in that regard. |
Thanks. Changing parser worked |
@glassbase Please note version 2.6.0 adds a new "days" option for this purpose. Set it to something greater than 1, you may need to experiment a little or look at how far apart your events tend to be. Please note, too, that with version 2.6.0 using the icalevents parser will require the use of the new days option, as it now returns data in the same manner as the other two parsers. I recommend removing the parser option and setting the days option with this update. |
HA calendar entities support additional attributes such as message, location, description, start_time and end_time attributes, etc.
Currently your component does not populate them. It would be awesome if you could add those. We could use this additional info to display calendar events start times, etc on dashboards.
(I only tested Google Calendar, but it appears to populate the start_ and end_time and the other attributes with the details of the current or next calendar event.)
Examples in documentation: CalDAV and Google.
The text was updated successfully, but these errors were encountered: