# Tedee lock in offline environment

**URL:** <https://community.tedee.com/t/tedee-lock-in-offline-environment/140>\
**Category:** Feature Requests\
**Created:** [July 8, 2024, 8:33pm UTC](https://community.tedee.com/t/tedee-lock-in-offline-environment/140 "2024-07-08T20:33:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![User\_migrated](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@User\_migrated](https://community.tedee.com/u/User_migrated)\
**Post date:** [July 8, 2024, 8:33pm UTC](https://community.tedee.com/t/tedee-lock-in-offline-environment/140/1 "2024-07-08T20:33:11Z")

</div>

Let’s have the following scenario: - cottage in the woods with electricity available - no internet nor cellular network signal at all - tedee lock on a door - BT enabled mobile phone with tedee app installed - one month stay Will the lock work normally the whole time of it’s owner presence? Meaning: will the mobile app be able to control the lock via BT (BLE)? Background: Somewhere in the tedee docs, I have read that on BLE, client needs to periodically refresh access certificates, and these are available only via the tedee “cloud”. If that applies also for the tedee app, the whole system is unusable for the mentioned scenario (also as in general it renders it unusable without tedee “cloud” availability).

---

<div class="post-metadata">

**Author:** ![User\_migrated](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@User\_migrated](https://community.tedee.com/u/User_migrated)\
**Post date:** [July 8, 2024, 8:33pm UTC](https://community.tedee.com/t/tedee-lock-in-offline-environment/140/2 "2024-07-08T20:33:12Z")

</div>

It needs to periodically refresh certificates. The scenario you posted will not work.

---

<div class="post-metadata">

**Author:** ![User\_migrated](https://avatars.discourse-cdn.com/v4/letter/u/f04885/32.png) [@User\_migrated](https://community.tedee.com/u/User_migrated)\
**Post date:** [July 8, 2024, 8:33pm UTC](https://community.tedee.com/t/tedee-lock-in-offline-environment/140/3 "2024-07-08T20:33:13Z")

</div>

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).
