# \[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:** 20
**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:** [June 2, 2023, 6:26am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/385 "2023-06-02T06:26:48Z")
> [@Automate\_Asia](#): > > On the web UI, the connect button will again state that the user is unauthorized. If I don’t click on the connect button and just click on continue, I’m eventually presented some SQLITE\_CONSTRAINT: NOT NULL constraint failed: Device.name error. > > Both app and webUI is not able to add the doorbird. Firmware issue? Sent a diagnostic report right after the SQLITE\_CONSTRAINT error as well. As mentioned this sounds like a Homey firmware issue or possibly even an issue with the hardware of your Homey. Does your Homey have enough free space? And have you reported this to Athom already? And please post the output of http://\<\>/bha-api/info.cgi using the same credentials you are entering in the Homey pair wizard. ---
**Author:** ![Marco\_Ter\_Weeme](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_ter_weeme/32/79282_2.png) [@Marco\_Ter\_Weeme](https://community.homey.app/u/Marco_Ter_Weeme)\ **Post date:** [June 20, 2023, 8:58am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/386 "2023-06-20T08:58:15Z")
Hello, I’m at a client with a 2 button doorbird, when i push 1 of the buttons the flow card does not trigger at al. Can you check what is going wrong? Diagnostic ID: a34cd1dd-18f6-4d7b-ad05-430bbe26dc03 ---
**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:** [June 20, 2023, 5:02pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/387 "2023-06-20T17:02:55Z")
The app currently does not support multiple doorbell buttons. You should be able to work around this though by creating a webhook in Homey, adding this webhook as HTTP call in the DoorBird Administration and setting this HTTP call in the HTTP events schedule of the second button, also within the administration area. ---
**Author:** ![Patrick\_Mandemaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_mandemaker/32/73654_2.png) [@Patrick\_Mandemaker](https://community.homey.app/u/Patrick_Mandemaker)\ **Post date:** [July 15, 2023, 12:24pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/388 "2023-07-15T12:24:23Z")
Any chance the a1081 can be added? ---
**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:** [July 15, 2023, 9:05pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/389 "2023-07-15T21:05:59Z")
What is not working? ---
**Author:** ![Eric\_Franckx](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eric_franckx/32/81174_2.png) [@Eric\_Franckx](https://community.homey.app/u/Eric_Franckx)\ **Post date:** [August 4, 2023, 8:00pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/390 "2023-08-04T20:00:53Z")
Hi, just a feedback: - add some printscreen link to steps and actions required - to make easy administration, use URL :[https://webadmin.doorbird.com/login](https://webadmin.doorbird.com/login) and set your admin user/password ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/333bfe301a1ecc82d12dbb922d0df120b3939c4e.png) - activate the API access as will be required then click on Connection (and not on Continue) Simple steps, example/printsceen will avoid a lot of ticket/support request and make live more easy. Regards, Eric ---
**Author:** ![martgom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martgom/32/85092_2.png) [@martgom](https://community.homey.app/u/martgom)\ **Post date:** [August 26, 2023, 1:56pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/391 "2023-08-26T13:56:10Z")
Hi, I have a D2101KV and the flow with the Doorbell is not working correct. I dont receive a message when someone press the doorbell, but with the flow “Someone pressed the Doorbell” this flow is triggered when someone enters a code on the keypad. Any idea what is wrong? When I test the API it is working (from a browser) but when someone press the doorbell I get the “General alarm” event in 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:** [August 26, 2023, 2:03pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/392 "2023-08-26T14:03:02Z")
Sounds like you messed up the http notification schedule. Try to remove and re-add the schedule from the device settings within Homey. ---
**Author:** ![martgom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martgom/32/85092_2.png) [@martgom](https://community.homey.app/u/martgom)\ **Post date:** [September 17, 2023, 8:17pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/393 "2023-09-17T20:17:21Z")
First I tried to remove all http notifications and add them again. It was still not working. Just did a factory reset of the Doorbird and still the same behaviour. Any idea how to solve this? ---
**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:** [September 18, 2023, 5:16am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/394 "2023-09-18T05:16:23Z")
Check the time schedule of the doorbell under the admin settings. Make sure the correct HTTP call is selected there. It should be the doorbell HTTP call. Do the same for the relay where it should mention the relay HTTP call. ---
**Author:** ![TBO](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tbo/32/37131_2.png) [@TBO](https://community.homey.app/u/TBO)\ **Post date:** [September 27, 2023, 7:50pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/395 "2023-09-27T19:50:24Z")
Hi, For some time now I have been receiving double notifications when the bell is pressed. I receive a double notification with snapshot and twice a doorbell sound over the Sonos speakers. As far as I can see, I have no duplicate flows and the Https calls and schedules in the DoorBird app are correct. I have already removed the DoorBird as a device in Homey, but this did not help. ---
**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:** [September 27, 2023, 9:13pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/396 "2023-09-27T21:13:07Z")
Perhaps something with the DoorBird itself? Have you tried restarting it? 🤔 ---
**Author:** ![TBO](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tbo/32/37131_2.png) [@TBO](https://community.homey.app/u/TBO)\ **Post date:** [September 28, 2023, 11:30am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/397 "2023-09-28T11:30:36Z")
I don’t know where the problem was. But resetting the Doorbird to factory settings, removing and reinstalling the device and app in Homey and reinstalling the Doorbird app on the phone worked. I get a single notification again when the doorbell is pressed. ---
**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:** [October 12, 2023, 2:12pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/398 "2023-10-12T14:12:19Z")
How can I log in with a newly created user if I get this screen and only admin credentials are working? ![Posnetek zaslona 2023-10-12 161114](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/7/97af47e2fc1f2e9498c8d2e76ebd01e3f7557ed6.png) ---
**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:** [October 12, 2023, 4:36pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/399 "2023-10-12T16:36:48Z")
You cant. As mentioned in the login screen you need to login with the admin users which was created during the setup of the device in the DoorBird app. ---
**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:** [October 13, 2023, 11:05am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/400 "2023-10-13T11:05:13Z")
It doesn’t work that way either. I can log in and add a device but after that, I don’t see anything (no live stream, doorbell snapshot, etc.) ![Posnetek zaslona 2023-10-13 130258](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/f/3f7898c62bb12b49867e68debce64ae28d9d4f6c.png) ![Posnetek zaslona 2023-10-13 130312](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/b/dbff8eda241d930c66eaff280b1de158b53c8ce2.png) ![Posnetek zaslona 2023-10-13 130326](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/7/c7b08ea82b380cd434ca3bf1cdf2bf4c8461f001.png) ![Posnetek zaslona 2023-10-13 130344](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/b/6b7a1f0bb66bcf4d45b808362cd5070ad0ba6b32.png) ![Posnetek zaslona 2023-10-13 130400](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/7/675be7f3445be551d2cd206ce7573db6fdb4984e.png) ---
**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:** [October 13, 2023, 12:01pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/401 "2023-10-13T12:01:00Z")
Restart the DoorBird app on Homey. It seems that something Homey does not initialize the device correctly. If that doesnt work send me a diagnostic report from the app settings. Not sure if I can actually help though as in this case it seems to be some sort of permission issue with your admin account and DoorBird Cloud. ---
**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:** [October 19, 2023, 9:27am UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/402 "2023-10-19T09:27:38Z")
I created the diagnostic report f8ff153c-7879-44fd-8ac6-274830bbdbc2 Device history and latest value for movements and generic alarm are now working, everything else unfortunately not. When I try to trigger the relay, error 400 bad request appears. ![Posnetek zaslona 2023-10-19 112023](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/b/5bc22651ef52512d97c44ef6cedfb5ed5a72c821.png) ---
**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:** [October 19, 2023, 6:08pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/403 "2023-10-19T18:08:20Z")
There is nothing in the log about a bad request and I cant reproduce. As this does not seem to be a problem for other users I dont think it’s something with the app. I did see an error in the log related to the cloud connection and a known bug with Homey cloud. Find the information about this below. There is a known bug in Homey Cloud which Athom does not prioritize or is unable to fix. This could result in devices not responding anymore on Homey Cloud often with the error `Could not get OAuth2Client` . The workaround is to reinstall the app from the app store to force a restart of the connection between Homey Cloud and DoorBird Cloud. Be sure to [report this issue](https://support.homey.app/hc/en-us/articles/360015784034-Submitting-a-support-request) to Athom as well so they might eventually fix this bug. When reporting this you can mention it’s an open issue for the Shelly app as well, known as issue #78 under the verified developer support portal. To be able to actually report the issue to Athom using a form you need to select the “Other …” option and not “App” as this is not an issue with the app but with Homey Cloud. ---
**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:** [October 20, 2023, 10:06pm UTC](https://community.homey.app/t/app-pro-cloud-doorbird/115/404 "2023-10-20T22:06:33Z")
Reinstalling the app to force a restart is also not working. I don’t know what else I can do that this will work in homey. I made another diagnostic report after reinstalling the app, I hope it will help. a1497688-6386-4a2a-9f04-38852be84676 [Previous page](https://community.homey.app/t/app-pro-cloud-doorbird/115.md?page=19) [Next page](https://community.homey.app/t/app-pro-cloud-doorbird/115.md?page=21)