Skip to content
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

[BUG]: Wrong month in upcoming node #176

Open
overlinden opened this issue Apr 29, 2024 · 0 comments
Open

[BUG]: Wrong month in upcoming node #176

overlinden opened this issue Apr 29, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@overlinden
Copy link

Describe the bug
I have a calendar (google ical) with all birthdays of my contacts. The birthday within the ical is correct but the date in the calendar object returned by the upcoming node is wrong.

To Reproduce
Steps to reproduce the behavior:

  1. Create an annual event in the google calendar
  2. Create a public ical link for that calendar
  3. Add the calendar to the upcoming node
  4. Connect the upcoming node to a debug node and check the message returned

Expected behavior
The dates (startdate and enddate) should math the ones in the calendar.

Screenshots
Node configuration:
Bildschirmfoto vom 2024-04-29 20-22-12

I downloaded the ical file and checked the event section:

BEGIN:VEVENT
DTSTART;VALUE=DATE:20210130
DTEND;VALUE=DATE:20210131
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTHDAY=30
DTSTAMP:20240429T181451Z
UID:coo3ieb16cr3gb9lcpi30b9k6spjab9o74omab9l6or30cj268o3idhm6k@google.com
CREATED:20210124T184900Z
LAST-MODIFIED:20210124T184900Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:xxx yyy Geburtstag 
TRANSP:OPAQUE
END:VEVENT

But the msg looks like:
Bildschirmfoto vom 2024-04-29 20-25-00

**node-red-contrib-ical-events

  • Version 2.2.5
  • node-red version 3.1.9
@overlinden overlinden added the bug Something isn't working label Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants