# \[APP\]\[Pro&Cloud\] DoorBird

**URL:** <https://community.homey.app/t/app-pro-cloud-doorbird/115>\
**Category:** Apps\
**Tags:** app, homey-pro, homey-service\
**Created:** [August 22, 2018, 11:00am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115 "2018-08-22T11:00:53Z")\
**Posts on this page:** 20\
**Page:** 23

<div class="post-metadata">

**Author:** ![Harry\_Inia](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harry_inia/32/85112_2.png) [@Harry\_Inia](https://community.homey.app/u/Harry_Inia)\
**Post date:** [February 7, 2024, 8:12pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/445 "2024-02-07T20:12:50Z")

</div>

I did notice the flowcard, but nothing under the device I see.

Thx @phuturist for your help today!

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [February 19, 2024, 8:14am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/446 "2024-02-19T08:14:54Z")

</div>

I found out that sending push notifications with an image from Doorbird doesn’t work → the device doesn’t get push notifications, occasionally it happens that a push notification comes but without a picture.

It also doesn’t work if I choose another image source (Last doorbell snapshot, Last motionsensor snapshot, or live snapshot) instead of the snapshot from the when card.

Example of flow that I have:

 ![Posnetek zaslona 2024-02-19 090640](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/e/ee1416d8509d1650c1678ac37f3396968dd39a80.png)

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [February 19, 2024, 8:33am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/447 "2024-02-19T08:33:41Z")

</div>

Seems you are right but this is a bug with Homey Cloud. I have no control over the notification action cards. You should report this to Athom.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [February 19, 2024, 8:58am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/448 "2024-02-19T08:58:05Z")

</div>

Maybe it has something to do with the image itself (size, quality, format, etc.). Just guessing 😃

Because flow testing always works (a push notification is sent) - the snapshot image in this case is a default logo from Homey.

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [February 19, 2024, 9:43am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/449 "2024-02-19T09:43:21Z")

</div>

Who knows. I have no knowledge of what goes inside core Homey code. The same image works fine on Homey Pro when used as token so your guess seems unlikely. And I tested sending the image over Slack from Homey Cloud and it works fine as well. My more educated guess would be it’s due to resource limitation on Homey Cloud or just a plain bug in Homey Cloud SDK but I don’t like guessing. Better would be for Athom to actually investigate it.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [February 19, 2024, 11:48am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/450 "2024-02-19T11:48:17Z")

</div>

Ok, I’ll report this to Athom to check.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [February 20, 2024, 3:00pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/451 "2024-02-20T15:00:11Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dc010e31633c71ed4b5da0682a6f125313acd3d1.png)

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [February 20, 2024, 3:34pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/452 "2024-02-20T15:34:31Z")

</div>

That’s the default first level response, the response is supposed to lower the load on the helpdesk by reverting users back to app developers. You need to push through to get it escalated to an actual developer that will take a look at it. Tell them that the developer of the DoorBird already looked at it. That the sending of a DoorBird image as token over Slack works fine and that the issue therefore is with the image notification action card on Homey Cloud, not with the app.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [February 20, 2024, 3:41pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/453 "2024-02-20T15:41:23Z")

</div>

I have already responded to them and I will try to get it through.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [February 21, 2024, 1:12pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/454 "2024-02-21T13:12:51Z")

</div>

Looks like I got it through, and the issue has been forwarded to development. I hope they find out where the problem is and fix it as soon as possible.

---

<div class="post-metadata">

**Author:** ![Daan\_Hendriksen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daan_hendriksen/32/78952_2.png) [@Daan\_Hendriksen](https://community.homey.app/u/Daan_Hendriksen)\
**Post date:** [March 12, 2024, 8:49pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/455 "2024-03-12T20:49:37Z")

</div>

Hi,

I’m not sure if this is the right place for this. Sorry if it’s not.

I got myself a DoorBird ds101. Installed it and working fine.

Then I connected it to homey. Configuring it I got an error 503 but it’s added anyway.

I can use everything from the DoorBird but the DoorBird app itself doesn’t send any push notifications anymore.

When I delete the https settings in homey, push notification are restored.

Does somebody have an idea on how to fix this?

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [March 13, 2024, 3:36pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/456 "2024-03-13T15:36:49Z")

</div>

> [@Daan\_Hendriksen](#):
>
> Then I connected it to homey. Configuring it I got an error 503 but it’s added anyway.

That doesnt sound good, have you tried repairing to see if this is consistent?

> [@Daan\_Hendriksen](#):
>
> When I delete the https settings in homey, push notification are restored.

Could you post a screenshot of these https settings in Homey. I dont know what you mean by this. And is this on Homey Pro or Homey Cloud?

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [March 14, 2024, 11:47am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/457 "2024-03-14T11:47:07Z")

</div>

One question can I somehow use two different Doorbird units?

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [March 14, 2024, 4:30pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/458 "2024-03-14T16:30:17Z")

</div>

Yes. Use Homey Pro.

On cloud I would not know how that would work together with OAuth2. Have you tried just adding it. Think it should work but I can’t test.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [March 15, 2024, 8:44am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/459 "2024-03-15T08:44:06Z")

</div>

I tried, but when I want to add a new device, it displays a dialog saying no device found and the login is skipped.

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [March 15, 2024, 11:24am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/460 "2024-03-15T11:24:11Z")

</div>

Is that device found and can it be added as the first device? A device not being found doesnt isnt equal to no support for adding multiple DoorBirds on Homey Cloud. That would be the first thing to test if you havent already.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [March 15, 2024, 3:01pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/461 "2024-03-15T15:01:08Z")

</div>

The problem is that the login screen is skipped and I can’t enter the credentials from another device.

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [March 15, 2024, 4:39pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/462 "2024-03-15T16:39:34Z")

</div>

And both devices operate under an different administrator account?

What happening is that Homey or to be more exact the OAuth2 module (and not the DoorBird app) is caching the credentials used to authenticate requests. This is a good thing but apparently it’s also using these cached credentials when pairing new products, which is easy if all products are present under the same account but results to not being able to add another product under the same app but with different credentials. My guess is that this is not supported on Homey Cloud but you’d have to ask Athom.

---

<div class="post-metadata">

**Author:** ![Daan\_Hendriksen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daan_hendriksen/32/78952_2.png) [@Daan\_Hendriksen](https://community.homey.app/u/Daan_Hendriksen)\
**Post date:** [March 16, 2024, 2:45pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/463 "2024-03-16T14:45:59Z")

</div>

![IMG_1253](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/f/4fbff36090c0112e1aff3a0fea62f8597224b4e1.png)

This is what I get when I add the DoorBird. Once I unbox it adds. I can use all functionalities from the DoorBird in homey but the db app no longer sends notifications

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [March 16, 2024, 5:14pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/464 "2024-03-16T17:14:51Z")

</div>

Send a diagnostic report from the app settings after you tried setting the notifications from the device maintenance actions.

[Previous page](https://community.homey.app/t/app-pro-cloud-doorbird/115.md?page=22)

[Next page](https://community.homey.app/t/app-pro-cloud-doorbird/115.md?page=24)
