iOS - 1.198.0
(16.06.2024)
Table of contents
- Added support for Dry Contact
- Continue with Microsoft
- Session expired bar now differs from Incident bar
- Unauthorized PIN activity log
- Automatic pull spring by PIN activity log
- Issue with connecting to the lock using Bluetooth
- Issue with expiring session
- Improved accessibilty labels
- Issue with calibration of the lock during adding process
Added support for Dry Contact
Tedee Dry Contact allows you to control your Tedee smart lock using traditional electronic methods like switches, wired legacy systems, and local smart home integrations. As a compact module wired to your controller and power source, Tedee Dry Contact unlocks Tedee GO or Tedee PRO via Bluetooth, without needing an app or internet connection. Enhance accessibility and simplify protection by syncing your smart lock with buttons and automatic door openers. Connect your Tedee PRO or Tedee GO to your wired smart home or alarm system, enjoying central management and local integration.
Continue with Microsoft
You can now log in to Tedee app using your personal or business Microsoft account.
Session expired bar now differs from Incident bar
It’s now easier to distinguish the incident status bar from the session expired status bar.
Unauthorized PIN activity log
Tedee lock administrators can now see in the activity logs when a PIN was used outside of authorized access times.
Automatic pull spring by PIN activity log
Tedee lock administrators can now see in the activity logs when the spring was pulled automatically using a PIN.
Issue with connecting to the lock using Bluetooth
We have fixed issues where app was in some cases not able to connect to the lock using Bluetooth.
Issue with expiring session
We have fixed issues where the access token could not be refreshed in the background, resulting in the session expired status bar being displayed.
Improved accessibilty labels
We have improved some accessibility labels in widgets configuration and selection elements.
Issue with calibration of the lock during adding process
We have fixed an issue where the lock could not be calibrated during the adding process when app has lost connection to the lock.