Any chance custom root certificate authority could be used to workaround this? Meaning the lock user himself is being responsible for certificate renewal (and there’s no forced dependency on tedee cloud).
Any chance custom root certificate authority could be used to workaround this? Meaning the lock user himself is being responsible for certificate renewal (and there’s no forced dependency on tedee cloud).