# \[APP\]\[Pro&Cloud\] DoorBird **URL:** \ **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:** 24
**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 19, 2024, 7:16am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/465 "2024-03-19T07:16:50Z")
> [@Phuturist](#): > > 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. Yes, both devices have different administrator accounts. How about this on Homey Pro, I assume that OAuth2 is also used for authentication. ---
**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 19, 2024, 7:42am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/466 "2024-03-19T07:42:00Z")
> [@Boris\_Fers](#): > > How about this on Homey Pro, I assume that OAuth2 is also used for authentication. Nope, this is cloud independent and works with a local DoorBird user with API credentials. ---
**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\ **Post date:** [March 21, 2024, 10:20pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/467 "2024-03-21T22:20:53Z")
Hi there, I believe I did as I should have to create a playable audio file, but I get this (strange) error message if I try to upload the file: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/2/d2c0216c4eb7edcf7e5fa779060fbd3d164490c2.jpeg) Any ideas? Regards ---
**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 22, 2024, 6:14am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/468 "2024-03-22T06:14:48Z")
Not a strange error. The error is telling you this isn’t the correct format. It seems you didn’t save the file with a header-less header but used Panasonic raw header. ---
**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\ **Post date:** [March 22, 2024, 12:07pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/469 "2024-03-22T12:07:54Z")
Hmm… what am I missing? ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/3/f3b2a6d9e578125ba37ad186dd078f71a316eb38.jpeg) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/7/3788405c8d4a2d42157e0cc7436625dd08c5d3ff.jpeg) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/b/5ba97209d2c72f26d26744e8dcdeecce1b42542a.jpeg) ---
**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 22, 2024, 2:02pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/470 "2024-03-22T14:02:47Z")
Seems alright, perhaps macOS is adding something funny. I’ll just add that file type to the allowed list of formats with the next release. I assume it shouldnt matter if the file is still encoded properly. ---
**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\ **Post date:** [March 22, 2024, 8:20pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/471 "2024-03-22T20:20:23Z")
Never mind - I missed an update or two… it´s working when using the latest Audacity version… 😉 ---
**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\ **Post date:** [March 22, 2024, 8:46pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/472 "2024-03-22T20:46:30Z")
But now: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/c/fc46173f8f20b2269b8bb0ef719c807314381667.jpeg) Which also is kind of interesting, because the Doorbird´s ip address is 192.168.1.220 and not 210… 🤔 ---
**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 22, 2024, 9:26pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/473 "2024-03-22T21:26:49Z")
That suggests it changed after pairing. You should make sure it has static assignment. For now you can change it under the device settings. ---
**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\ **Post date:** [March 23, 2024, 9:50am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/474 "2024-03-23T09:50:30Z")
You’re right - I must habe assigned a static ip after initial pairing… Thanks! ---
**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\ **Post date:** [March 29, 2024, 11:30am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/475 "2024-03-29T11:30:57Z")
Another question: I am using Heimdall to trigger alarm events with door bird being one of motions sensitive devices: ![Bildschirmfoto 2024-03-29 um 12.28.45](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/794dd30b94e79452242298529f7e008720812432.jpeg) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/0/40c8c952b6c1b00c7ca61e268c290970a89e34f4.jpeg) But when Heimdall is triggered by a motion event, I receive this erroneous push message: ![IMG_7870.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/5/8568ecff34b6c3b052600c8c61ec790519ad0903.jpeg) Any suggestions? ---
**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 29, 2024, 12:35pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/476 "2024-03-29T12:35:57Z")
> [@naehle](#): > > Any suggestions? Yes, complain about it to Athom. There is a bug in Homey cloud with the image tokens. ---
**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:** [April 2, 2024, 8:43am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/477 "2024-04-02T08:43:29Z")
This is a bug on Homey and Athom had to fix it. I’ve opened a support issue for some time now and I’m waiting for them to make a fix. Latest response from their support team: > I will forward your report to Development so they can take a look at it. I can’t give you any guarantees on when your issue will be found and solved, but please know that it will be placed in the right hands and will be investigated. Homey Pro (Early 2023) Changelog v10.3.2 - Fixes an issue where the image of a virtual IP camera could not be send as a push message to an Android device. So this patch is still missing only for the cloud. ---
**Author:** ![Julian](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julian/32/2651_2.png) [@Julian](https://community.homey.app/u/Julian)\ **Post date:** [April 3, 2024, 10:15am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/478 "2024-04-03T10:15:30Z")
Is it correct thet the motion sensor of the Doorbird (which is visible in Homey and works fine) does not show as a motion sensor in the zone it is in? I have two motion sensors and the Doorbird in my driveway and only the two motion sensors show up when going in the ‘Activiteit’ tab. FYI the Doorbird is not excluded in the relevant settings, it does not show up at all. ---
**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:** [April 3, 2024, 1:48pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/479 "2024-04-03T13:48:06Z")
You will need to set the status indicator of the device to the motion\_alarm under the device settings. ---
**Author:** ![Julian](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julian/32/2651_2.png) [@Julian](https://community.homey.app/u/Julian)\ **Post date:** [April 3, 2024, 4:38pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/480 "2024-04-03T16:38:59Z")
Thank you, I would not have guessed that. I immediately tried but in my case nothing changed? I tried restarting Homey. ---
**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:** [April 3, 2024, 5:13pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/481 "2024-04-03T17:13:34Z")
Could you post a screenshot from the screen where you would expect the DoorBird motion to show up. Perhaps I’m misunderstanding you. ---
**Author:** ![Julian](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julian/32/2651_2.png) [@Julian](https://community.homey.app/u/Julian)\ **Post date:** [April 3, 2024, 6:39pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/482 "2024-04-03T18:39:54Z")
This is when you go to ‘Apparaten’ and then select the zone (in my case ‘Oprit’) and then you select ‘Activiteit’ in the top right corner. Here you see the two motion sensors whereas in the zone itself the Doorbird is also located. ![IMG_9749](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/4/c40b6c2edcad66cbb08147801acca9772f86a1d9.png) In the settings here in the top right corner the Doorbird is also not present, so I do not have the option to exclude or include it. ---
**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:** [April 3, 2024, 9:09pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/483 "2024-04-03T21:09:56Z")
I see. My guess is that it doesnt show here because the device class of the DoorBird is a `doorbell` and Athom decided to filter this page based on device class `sensor` instead of the more logical filter `any device with the motion_alarm capability`. It’s not for me to fix as I wont be changing the device class of the DoorBird because of this. You can report it to Athom though, perhaps they can change the filter for this page (assuming my guess about why this is happening is correct). ---
**Author:** ![Julian](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julian/32/2651_2.png) [@Julian](https://community.homey.app/u/Julian)\ **Post date:** [April 4, 2024, 9:13am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/484 "2024-04-04T09:13:42Z")
Ok, thanks for thinking along. I know it used to work because I changed my flows when the ‘zone is active’ functionality became available. So I will change it back to seperate flows again and will ask Athom if they can change anything in that area (or why they changed it in the first place, perhaps it is a bug). [Previous page](https://community.homey.app/t/app-pro-cloud-doorbird/115.md?page=23) [Next page](https://community.homey.app/t/app-pro-cloud-doorbird/115.md?page=25)