Calendar Node (beta)

[zachowj]

https://zachowj.github.io/node-red-contrib-home-assistant-websocket/node/events-calendar.html

[rallep71]

First of all, thank you very much for the node! I have found the following: When I create an event in the calendar, it works in Node Red. However, if I change the times in the calendar for the same entry, it is sometimes triggered in Node Red and sometimes not.

[rallep71]

I have tested it again. When I create a new event in the calendar, it is triggered. However, if I only change the time for an event that has already been created, it is no longer triggered.

[yanikdude]

Hey All.

Using this new node and trying to get the Calendar entry details pushed to my phone. I can get the phone push notifications working but can't get the details to output. Any help would be greatly appreciated.

[lukejagger]

It doesn't seem to work some of the time. I am searching for calendar event with 'Reserv' at the beginning, 10 hours prior to start, and I've seen it work once, but now it doesn't seem to trigger. Will it look past other events as I have an 'Airbnb (Not available)' event before the 'Reservation' event.

[gbrogna]

I have been waiting for this node. Like others have said it is intermittent and unreliable. Looking forward to updates. Thank you for all your efforts.

[lukejagger]

Any progress on fixing this, it is a great addition!

[morlie]

I couldn't find any detail in the current documentation. When I create an event in the google calendar it's not shown in Node-Red immediately. How long does it take till Node-Red sees the event? When I restart Node-Red it's showing the event immedtiately after it's online again.

The events are shown in Google and Homeassistant immediately but not queued in NR. Is there an option to trigger and re-load newly created events?

[Ewoodster]

Same problem here. Only after deploying, the node will update and queue the calendar event.
In general, the node is awesome, but it has been in Beta for a year now without any updates. I wonder if it will ever be released.

[nightfever77]

Negative offset does not seem to work as intended.
E.g. offset is set to -15 minutes, but payload will always be injected 15 minutes after event start.

Edit: Just saw in the issues that the offset is inverted. Can live with that, just need to know.

[Teme-V]

With recurring calendar event, i.e. daily but with 30d interval - node trigger previous event information on each day - next event in calendar is on 20250402T221500

recurrence_id: "20250303T221500"
rrule: "FREQ=DAILY;INTERVAL=30"

[RoberDNuno]

I need help with this. I can't reed events

[yanikdude]

So you are tying to see if there is an event scheduled for the following day, which accrues at 07:30, to trigger another event at 05:30 like preheat the car?

Or I maybe worth specifying the full use case.

[RoberDNuno]

Let me explain this better:
At 5:30 a.m., I need to know if there is a calendar event that will occur at 7:30 a.m. (2-hour offset).
With the node I showed you earlier, it sometimes works with small offsets, but not with longer offsets.
When the node discovers if the event exists, it modifies a variable to perform different automations (lights, blinds, coffee, etc.)

[morlie]

It's a well known bug since a while
#1302

[RoberDNuno]

Is a short-term solution expected? Are you using any alternatives?

[morlie]

Is a short-term solution expected? Are you using any alternatives?
But was reported more than 1 year back. It's unlikely.

You could read the google calendar in Home Assistant and fire an event. Node-Red reacts on the event and does whatever needs to be done. Or you create the calender entry starting 5:30 ...

`
description: ""
mode: single
triggers:

• trigger: calendar
  entity_id: calendar.homeassistant
  event: start
  offset: "--2:0:0"
  conditions: []
  actions:
• event: xxxx
  event_data: {}
  `

[fredrikbuchanan]

no biggie but slightly annoying.
There is a mismatch between the documentation and the actual web config , the documentation references "conditions" but not "filters", in the web config there is a "filtering" choice but nothing about "conditions".

[phlo2009]

May I suggest to have 2 outputs for the node with for start and the other for stop to identify the state transitions. Condition filters are not necessary as this can be handled more efficiently by using an external Switch node.

[etymotic]

Hmmm, I'm trying to wrap my head around this node.

I was thinking it would output either "on" or "off" based on whether or not you're currently inside a calendar event, but it outputs text based on the event so you can't use a Switch node to made decisions based on "on" or "off".

It also only outputs once -- either at the start or the end.

So, in typing this out, if I want to trigger something at the beginning of an event and also at the end of the event, I need two calendar nodes.

Easy enough -- I just had to wrap my head around the logic.

[garrathbond]

how does the filter work please

[phlo2009]

Ref version 0.77.2 I tested the start and end modes. Works great as expected. Philip

…

On Sun, Aug 31, 2025, 11:55 a.m. garrathbond ***@***.***> wrote: how does the filter work please — Reply to this email directly, view it on GitHub <#1295 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADI6NOQMAEWEUGWOYZZXYDD3QMLHTAVCNFSM6AAAAABDC3PYBCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRWHA3DKNQ> . You are receiving this because you commented.Message ID: <zachowj/node-red-contrib-home-assistant-websocket/repo-discussions/1295/comments/14268656 @github.com>

[joezappie]

I have a local calendar for our trash schedule. I had existing events when installing node red, and tried recreating them, but no matter what Im getting "No upcoming events queued at: Sept 10:55". Any info on why this is?

I have the node red hacs custom integration installed and use it for HA buttons.

[carlson993]

I also have the same issue