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.
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
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.
Any chance the a1081 can be added?
What is not working?
Hi,
just a feedback:
add some printscreen link to steps and actions required
to make easy administration, use URL :https://webadmin.doorbird.com/login and set your admin user/password
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
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.
Sounds like you messed up the http notification schedule. Try to remove and re-add the schedule from the device settings within Homey.
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?
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.
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.
Perhaps something with the DoorBird itself? Have you tried restarting it? 
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.
How can I log in with a newly created user if I get this screen and only admin credentials are working?
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.
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.)
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.
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.
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 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.
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
