What is iCal?
iCal Feed technical details
The data provided in an iCal feed can be different with each feed provider. To make the most use of integrating with an iCal feed, it should supply a list of Events with Start and End times in the future. Within each Event should be a list of "Attendees", which would be email addresses of people attending the Event.
For feeds from a Vacation Rental provider, a Reservation would be represented by an iCal Event, and guests of that Reservation would be listed as Attendees.
Feed Syncing and changes to Events
The RemoteLock system will periodically check your feed for new Events and changes to Events, which is referred to as a "sync". The default is to sync every hour, though that amount of time can be changed in the feed's Settings.
New Events should result in new guest access being generated for all associated doors, for the time period of the Event. If the event contained Attendee email addresses, separate PINs will be created for each Attendee, and the PIN with Access Instructions will be automatically emailed to each Attendee.
The RemoteLock system will detect certain changes to Events:
- Changes to the start/end time
- Cancellation of the Event
Any automatically generated guest access will be automatically updated to reflect these changes.
Currently, these changes are not detected, but may be supported at a later time:
- Removal or addition of Attendees within the Event
- Removal or addition of Doors/Locks after guest access has been automatically generated for an Event
- Deletion/removal of an Event. To revoke guest access that has been automatically generated for an event, the Event must be explicitly "canceled". Simply removing the Event from the feed will not revoke guest access.
Other notes regarding syncing of feeds:
- Access for "All Day" Events will use your account's Default Guest Start/End Times
- Emails to guests will either be sent immediately or scheduled according to your account's Guest Message Times if any have been created
Common issues with Feeds
A feed may be added that does not contain any upcoming Events. This is not necessarily a problem - Events may still be added sometime later, and would automatically be detected by the RemoteLock system.
Events that do not contain Attendees
While the email addresses of Attendees are typically included in an Event, they can be optional, meaning that some Events may not include any Attendee email addresses.
By default, the RemoteLock system will still generate a guest access PIN for these Events, but without Attendee email addresses, the PIN and Access Instructions cannot be automatically emailed.
If you would like to change this behavior to only generate PINs for Events that do contain Attendee email addresses, this can be enabled in the Settings for a feed by checking the "Only generate guest access for events that contain attendees" box.
Feed contains duplicate events
This occurs when a feed is not correctly following the iCalendar specification. In this case, our system detected that the feed is not providing consistent ID values for Events, which are needed to track the Event over time.
Feeds with known issues
Two separate iCal feeds are provided by Google Calendar - one Public, and one Secret. It is the Secret address that should be used here as it contains the full information for each event, including Attendee Email and All-Day events:
Note that the Secret address may be hidden for users of Google GSuite, and the GSuite administrator may need to grant permission to enable it.
Feeds from this provider are known to result in the "duplicate events" error above. We are working with Lodgify to resolve the problem.
Feeds from this provider are known to result in the "duplicate events" error above. We are working with TripAdvisor to resolve the problem.
Some feeds from this provider are known to result in the "duplicate events" error above, while other feeds are known to be missing both Attendee Emails and descriptions of each guest.
We are working with BookingSync to resolve the problems.
Feeds from this provider are not compatible. Events appear to be missing their "status", therefore our system can't determine if an event is confirmed or canceled. Some events appear to be missing a unique ID also.