---
title: "Connect a DoorBird Cloud intercom to Link’nX: status and troubleshooting"
description: Declare a DoorBird Cloud intercom in Link’nX, authorize it with the administrator account, then read its status, connection errors and deletion messages.
canonical: https://wiki.can-nx.com/en/guides/link-doorbird-cloud/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: Security & Access devices, DoorBird Cloud record and DoorBird authorization"
---

# Connect a DoorBird Cloud intercom to Link’nX: status and troubleshooting

Context: Link’nX web: Security & Access devices, DoorBird Cloud record and DoorBird authorization

The **DoorBird Cloud** record in Link’nX links a DoorBird intercom to your project through the DoorBird cloud. Once the device is authorized with its administrator account, Link’nX can create and delete access codes on its keypad, for Access Control bookings or from the KNX bus.

Intended for the authorized installer or administrator of the project. For an intercom reached directly on the local network, follow the [local DoorBird guide](https://wiki.can-nx.com/en/guides/link-doorbird-local/) instead.

## Before you start

- The project and gateway selected in Link’nX are the right ones.
- You have the administrator access of the DoorBird device: the connection help specifies a username ending in **0000**.
- These credentials are entered only in the DoorBird authorization space.

## Declare and connect the intercom

1. Open **Devices → Security & Access → DoorBird Cloud**, or search for **DoorBird** in **Search a device...**. On mobile, first open the three-line menu. For a missing card, a padlock or an availability indication, see the [navigation guide](https://wiki.can-nx.com/en/guides/link-navigation/).
2. Click **Add**. In **DoorBird Cloud declaration**, fill in **Name**, required and limited to **64 characters**, for example “Reception gate”.
3. Under **DoorBird Cloud connection**, the status shows **Not connected**. Click **Connect DoorBird**. There is no need to save and reopen the record first: Link’nX saves the declaration and moves straight on to the authorization.
4. In the DoorBird window that opens, sign in with the administrator account of the right device and follow the instructions shown. If the browser blocks pop-ups, the authorization continues in the current tab. The labels of this external space may differ from those of Link’nX.
5. Back in Link’nX, wait for **DoorBird connected: the device is ready.** and the **Connected** status.

## Save or change the name without connecting

The **floppy disk at the bottom right** saves the declaration or a name change, then returns to the list. It stays grayed out while the name is missing. Wait for **Success!** after a creation, **Updated!** after a change, then reopen the row to reread the name.

A record saved with only its name stays unconnected: reread its **Status**, then use **Connect DoorBird** if necessary. To abandon an entry, leave the record; if **Unsaved changes** appears, **Cancel** stays on the form and **Don't save** discards the change.

## Check the result

1. Return to the list with the back arrow at the top left. Find the row by **Name**, **Device** and **Status**.
2. Reopen it with the **Edit** pencil and reread the status, even if the DoorBird window closed normally.
3. Reread **Device**, **MAC address**, **Keypad**, **Relays** and **Max codes** to identify the associated hardware. This information comes from the connection: it is for viewing only and is not entered in the record.
4. Read any warning about the keypad or schedules (see “Troubleshooting”), then run an opening test before commissioning.

To prepare bookings, continue with [Declare an access control device](https://wiki.can-nx.com/en/guides/link-accesscontrol-device/). To associate the code commands with KNX, follow the guide to [the DoorBird Cloud gateway](https://wiki.can-nx.com/en/guides/link-doorbird-cloud-gateway/).

## Remove a declaration

A deletion can affect the connection and the codes in use. Have the removal and its scope confirmed by the administrator. If active bookings or access are concerned and the consequences are not established, contact support before the operation.

1. In the **DoorBird Cloud** list, check the device row, then click its **Delete** trash can.
2. The browser confirmation displays **Delete item**, followed by the name. Cancel if the name or the operation does not match your intention; otherwise, confirm.
3. Read the result message, then reread the list.

| Message | Meaning and next step |
| --- | --- |
| **Deleted!** | The interface reports the removal. Then run a keypad test to check it on the hardware. |
| **Deletion incomplete — try again.** | The code cleanup did not finish; the device and its authorization are kept for a retry. Consider the codes as still present and try again. If the retry fails, contact support with this message. |
| **Device removed, but its DoorBird connection had expired…** | The declaration is gone, but codes may remain on the keypad. The message asks you to remove the codes prefixed **CanX:** manually from the DoorBird app or its web administration. Have this check carried out by the authorized administrator; if the path or the consequences are uncertain, contact support before erasing codes. Until this check is done, consider access as still active. |
| **Cannot delete: this DoorBird is used by an access-control device.** | The DoorBird stays declared. The message asks you to delete the access control device that uses it first: have that removal confirmed as described above. |

## Troubleshooting

| Status or message | Check and next step |
| --- | --- |
| **Connection expired** | The authorization is no longer valid: codes can no longer be created or deleted until the device is reconnected. Open its record, click **Reconnect DoorBird**, then reread the status after the authorization. |
| Device **Connected**, but the association must be redone | The button is called **Reconnect**. Check the device and the scope before starting a new authorization. |
| **Could not start the DoorBird connection. Check your Internet connection and try again.** | Check the connection, then retry from the same record. The declaration may already be saved: look for it in the list before creating another one. |
| **The connection session has expired or is no longer valid.** | Start the connection again from the device’s record. If the return places you on the list, first reopen this record. |
| **Access refused on the DoorBird side** | The authorization was not granted. Check that you are using the expected administrator account and the right device, then resume the authorization. |
| **This DoorBird is already connected to another site.** | The message asks you to disconnect it from the other site before connecting it here. First have this attachment and the consequences for existing access checked; if the site change procedure is not known, contact support rather than deleting an active device. |
| **Technical failure while connecting to DoorBird.**, **Unexpected error during the DoorBird connection.** or **The DoorBird connection failed**, followed by a code | Retry once from the record. If the failure repeats, contact support with the message displayed and the attempts made. |
| **Keypad: Absent**, or a no-keypad warning | Check that the right device is connected and that it has a keypad. Without a keypad, access code commands have no effect. |
| Warning: the device does not support DoorBird schedules | Created codes will not be able to trigger a relay. Have the capability and the model confirmed by support. |

If the problem persists, contact support@can-nx.com and state Link’nX, the project, the device model or name, its status, the message displayed and the steps already tried. Do not send passwords, PIN codes or confidential authorization links.

French labels: **Appareils → Sécurité & Accès → DoorBird Cloud → Ajouter**, **Déclaration d'un DoorBird Cloud**, **Nom**, **Connexion au cloud DoorBird**, **Non connecté**, **Connecter DoorBird**, **Connecté**, **Connexion expirée**, **Reconnecter DoorBird**, **Reconnecter**.