<calender-id>: look into the calender details at google
You also have to create an additional Client-Id. Look at https://developers.google.com/google-apps/calendar/caldav/v2/guide#creating_your_client_id
Then set the log level of the OH plugin to TRACE and look at the logfile after OH has been restartet.
There should come up a message that access to goolge has to be authenticvted giving an URL to a google page. Call this, grant access and you will be provided with a access token which should be used a the password along with the client-id as username.
################################ CalDav Binding #######################################
#
#********************************************
#Googlekalender
#********************************************
caldavio:GoogleSmarthomeCal:url=https://apidata.googleusercontent.com/caldav/v2/<calender-id>/events
caldavio:GoogleSmarthomeCal:oauth=true
caldavio:GoogleSmarthomeCal:reloadInterval=5
caldavio:GoogleSmarthomeCal:preloadTime=10080
caldavio:GoogleSmarthomeCal:disableCertificateVerification=false
caldavio:GoogleSmarthomeCal:username=<client-id>
caldavio:GoogleSmarthomeCal:password=<access token>
# Additionally needed binding: org.openhab.binding.caldav-personal-<version>.jar
# used to record and simulate presence and to show upcoming/active events
# multiple calendars (calerdar-id) can be seperated by commas
caldavPersonal:usedCalendars=GoogleSmarthomeCal
now after one week running this configuration I can report that only the first ocurrence of the recurring entries has been recognized. I left all entries untouched.
Does this help you?
Thanks
Thomas
hi @sudocristian
with this URL same result on OpenHab. From Browser ask me Authentication, but I do not know which credential to use.
My Account Username and password do not work, and ClientID and Client Secret do not work too.
In log I do not got message and URL for authentication.
@sudocristian
it does not work, and arrived me an email from google on same account, that tell that some try to access to an insecure app, or something similar, i translated from italian
@sudocristian
I have another google account, Iâll try with it.
The strange thing, is that on version 1.8 I use the old Gcal binding with oAuth 2.0 and works fine since 2 years. I do not know what happen with this binding.
Thanks for help.
It really seems that all recurring entries got recognized now.
I switched back in my configuration to use the every weekday recurring entry which now doesnât drop any entry.
I made a cross-check using the old JAR-file which brought the issue back.
Now I stay using your new version. Will do additional tests.
E.g. I meant that I saw a removed entry in the middle of the week hasnât been recognized as deleted.
Thank yo so far.
Does the removed caching imply any other drawbacks?
@querdenker2k:
I can confirm that individually deleted entries of a recurring series wonât be recognized as deleted by the plugin and are still reported âactiveâ