So I assume there is no problem with the basic caldav connection and sync. Still I do not get the switch “Fritz_Esszimmer_Switch” turned ON or OFF (i.e. nothing is logged in events.log).
This is my ics entry as I find it replicated by the binding:
Is this ics entry looking like it should? At least for my eyes the DESCRIPTION looks as expected.
Or do I have to go to the item file where Fritz_Esszimmer_Switch is declared and add something?
This is the caldavCommand v1 binding running on a very recent openhabianpi 2.1.0-1.
BEGIN/END command in SUMMARY field or in DESCRIPTION field
iPhone as calendar editor
Outlook as calendar editor
It is frustrating that:
the calendar entries are really copied to /var/lib/openhab2/etc/caldav/mycalendarname/SomeFilename.ics on my openHABianpi system
every BEGIN/END is logged to openhab.log at exactly the right minute
but still no value changes and nothing appears in events.log
I must be missing something really obvious, because all others having problems with caldavCommand binding reported success as sson as they got the entries synchronized.
Thank you for your help. The one difference I can see is that your item is a virtual one (not bound otherwise) whereas my switch has an existing binding to homegear.
But then again: I checked with a virtual Number item as well, which doesn’t have any binding.
Is there something special behind your gRestore group? Or is this just a group controlling the last-value persistence?
That I would have to use that prefix was stated in some thread about migration from OH1 to OH2.
I assumed that I had no issues at that level of configuration because the entries are scheduled at the right time. But maybe I should give it a try w/o that prefix.
UPDATE:
That really is the solution. The “caldavio:” prefix in my caldavCommand.cfg was ill-guided. Deleting it solves the problem. My fault was that I assumed when the *.ics entries from my calendar are synced and EventJobs are scheduled at the right time, then the readCalendar statement would be right, i.e. because it points to the right calendar. But it seems EventJobs are already scheduled if the caldavio.cfg alone is configured. Strange.
Arrrgh I can’t believe it took me this long to understand that the calendar name in caldavCommand:readCalendars=blah has to match caldavio:blah:
I thought readCalendars referred to the actual calendar names inside the caldav server, so i had “owncloud” in one file and “openhab” in the other. No wonder it never worked!
Thanks for the clarification, now that I look at the documentation again it makes perfect sense but maybe it should be clarified that we are referring to the caldavio instance name by calling the variable in the example something else than calendar-id