Experiencing issues when syncing with Baikal and davx5

[stimpietubby]

When i enter my baikal url and login credentials, everything go's right. And when i make a appointment and click on the sync button, i get a message that i sync's successfuly. But when i go to the calander of my phone i dont get the appointment there. got also successfuly the baikal setup on my phone. When i create a appointment on my phone its sync's to the baikal server, but not from baikal server to easyappointmets programm.

[professortaha]

have the same issue too

[alextselegidis]

Hello!

Can you please confirm you are syncing / viewing with the right calendar?

Alex Tselegidis, Easy!Appointments Creator Need a customization? Get a free quote!

[stimpietubby]

Hii

I put the same details what i enter in easyappointments in a app called davx5 and i use the normal standard calander app from my android phone.

[professortaha]

I'm using davx5 for android and apple calendar and thunderbird same link and user name and password.
the only one isn't working is easyappointments

[alextselegidis]

I will need to test the set-up with davx5 to see what the problem may be.

Alex Tselegidis, Easy!Appointments Creator Need a customization? Get a free quote!

[alextselegidis]

Hello!

FYI the upcoming 1.5.1 will feature improvements to the CalDAV sync integration that might fix the problems you experience.

Keep an eye out for the new release (social media, blog or here in GH)

Alex Tselegidis, Easy!Appointments Creator Need a customization? Get a free quote!

[RichardHeilmann]

@alextselegidis

How exactly should the current CalDAV implementation work?
Is it supposed to be a two-way sync, so events in each calender get updated in the other?
Or is is supposed to be a one-way sync, so only events from the CalDAV calendar are synchronized to the Easy!Appointments calendar?

I'm currently experiencing the same issue with the CalDAV sync, that it only works one-way:

CalDAV calendar -> Easy!Appointments calendar

Im using grommunio as the CalDAV server. It is based on SabreDAV, wich is also the base for Baikal.
But I'm also using the Easy!Appointments docker image, which is still on version 1.5.0, so maybe that is the reason, why the sync only works one way?

It would be great If you could clarify if this is a bug or works as expected :)