Tedee Binding [5.0.0.0;5.3.0.0)

Add-on Marketplace Bundles
, ,
1

Sign
Sign540×540 2.36 KB

The Tedee binding integrates Tedee devices (like a lock) through either the Tedee Cloud REST API or the local REST API exposed by a Tedee Bridge in the local network.

Cloud API and Local API bridge/things are separate but can run in parallel.
E.g. the same physical lock may therefore appear once below each configured connection.

README

Cloud REST API

  1. Add a Tedee Bridge - Cloud REST API and set your Personal Access Token (api token).
  2. Wait until this cloud bridge is ONLINE.
  3. Add auto-discovered locks, keypads, and bridge devices within the inbox (they bind only to this cloud bridge).

Local REST API

  1. Enable the local Bridge API in the Tedee app and create a local API token.
  2. Add a Tedee Bridge - Local REST API and set apiRoot (e.g. http://192.168.1.10/v1.0) plus apiToken.
  3. Wait until this local bridge is ONLINE.
  4. Add auto-discovered locks from the inbox (they bind only to this local bridge; keypads are not available locally).

Changelog

Version 1.0.0-beta

  • initial release

Resources

Download jar file

Source code

2

I tried your binding, but it always failed , saying ‚invalid token‘. I use the same data for my template rule.

IMG_1494
IMG_14941640×2360 237 KB

3

Hi, even I assume you already double checked: but are you sure your token is correct? Is it the token of your local api from the bridge and not of tedee cloud? Possibly unwanted character copied (space or something)?

When you open swagger in your browser of your tedee birdge via http://192.168.1.72 and you click on Authorize button, enter your token and then try to execute e.g. the GET /bridge endpoint, does it work or will it result into http 401 aswell?

4

I set a new api token in Tedee app, and even then, I only get ‘invalid token’ in swagger and the bindung. But my rule and webhook messages are proper working. Maybe setting the webhook in the bridge blocks something