I did enable KeepAlive – not sure if it is used, the CalDAV binding seems to poll. On the advanced tab, I did not enable Kerberos because the OpenHAB CalDAV binding passes credentials. I used a PKCS12 store (Windows type), but a java keystore should work too (you may need to add the key signing key to the ca truststore for your java instance). On the ‘encryption’ tab, you can configure a private keystore to allow the client to communicate over SSL. On the first connection through DAVMail, there will be a pop-up asking you to verify and accept the certificate. You *can* put the thumbprint of the IIS web site server certificate for your Exchange server into the “server certificate hash” field or you can leave it blank. On the ‘network’ tab, check the box to allow remote connections. Configuration - for Exchange 2013, you need to select the “EWS” Exchange protocol and use your server’s EWS WSDL URL. Installation was straight-forward (click ‘next’ a few times). Scott found DAVMail - essentially a proxy that can translate between CalDAV clients and the EWS WSDL. Problem is, Microsoft stopped supporting CalDAV. Move the gymnastics session to a new day, and the audio reminder moves itself. We’ve wanted to get our Exchange calendar events into OpenHAB - instead of trying to create a rule to determine preschool is in session, the repeating calendar event will dictate if it is a break or school day.
0 kommentar(er)
