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

Caldav: Google deprecated commonly used endpoint #668

Closed
thucke opened this issue Apr 18, 2018 · 5 comments
Closed

Caldav: Google deprecated commonly used endpoint #668

thucke opened this issue Apr 18, 2018 · 5 comments

Comments

@thucke
Copy link

thucke commented Apr 18, 2018

The current examples of the Caldav Command Binding documentation for connection Google calendars are shoing URL examples like https://www.google.com/calendar/dav/[email protected]/events.
However the CalDAV API Developer's Guide states that this endpoint is deprecated and no longer supported.

Hence the binding should be extended to support Googles OAuth 2.0 authentication.
There were already activities and also a functional solution (see querdenker2k/openhab#2) that I personally used in OH 1.8.

@Confectrician
Copy link
Contributor

Hi @thucke

Thanks for pointing out this issue.
All of our Binding Documentation is maintained in the corresponding Add-on Repos beneath the Binding code.
We grab it from time to time and update all Binding docs in one run.

For CalDav the location would be:
https://github.com/openhab/openhab1-addons/tree/master/bundles/binding/org.openhab.binding.caldav-personal

What does that mean now?

The issue you are pointing out has to be filed in the right place.
In your case this would be the openhab/openhab1-addons Repository.
https://github.com/openhab/openhab1-addons/issues

Especially it does make much more sense in the other repo, because the documentation is not the root problem in this case.

@Confectrician
Copy link
Contributor

Sorry that close was by mistake. 😄

@thucke
Copy link
Author

thucke commented Apr 19, 2018

Thank you @Confectrician
Issue #5557 opened
Should this one stay open for later update of the documentation?

@Confectrician
Copy link
Contributor

Should this one stay open for later update of the documentation?

I would say no.
The documentation readme file is in the openhab1 repository too,
so we should better keep an eye on updating the information there while introducing a possible fix/improvement.

What do you think?

@thucke
Copy link
Author

thucke commented Apr 19, 2018

Surely - thank you again.
Take care ..

@thucke thucke closed this as completed Apr 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants