Doorbird integration

This is what I plan to do.

The current DoorBird component code gets the LAN IP of the HA machine and uses that. Once I get time to work and test it, I’ll attempt to read the base_url option of the http component and use that instead, otherwise fall back to the IP address if it isn’t set up.

I just looked at the code and it should work fine with SSL.

Could you please share your http component configuration?

If you need more info that this I’ll PM you…
http:
api_password: !secret http_api_password
ssl_certificate: !secret ssl_certificate_loc
ssl_key: !secret ssl_key_loc
base_url: !secret base_url

The component should be using the base_url, so double-check that it’s correct.

Otherwise, please go to http://_doorbird_lan_ip_here_/bha-api/notification.cgi, log in with the same user account you have in your component configuration. It should look something like this:

{"BHA": { "RETURNCODE": "1", "NOTIFICATIONS": [{"event": "doorbell1","subscribe": "1","url": "http://_home_assistant_url_/api/doorbird/doorbell","user": "","password": "","relaxation": "10"}]}}`.

Then try going to the exact/entire url value and see if it responds correctly (it should just say OK) and serves a valid SSL certificate.

I finally had time to troubleshoot this on my setup. Your instructions above do fire the doorbell event if i use the local IP address. Also, if in the Doorbird app i go into Admin and under HTTP Calls I change the fully qualified domain name (eg duckdns.org) to the local IP (10.x.x.x) it all works fine, but of course this setting does not stick once I restart HA. Is a solution to set the URL to LAN IP instead of FQDN?

First off thanks so much for this! I have the doorbell event working great, my question is does this work with any other events? Motion to be more specific? Thanks

I would like to use duckdns domain as base_url, but if I do it, it doesn’t work because Doorbird tries to reach ha server through duckdns, and not through local ip. I have to set local ip in base_url to get it working.

Please, can you add a “url” property to Doorbird component, and use it instead of base_url? You can use base_url if component’s url is not defined (as telegram component does). So we can have base_url with duckdns, and Doorbird url with private ip.

While the motion event is documented for the DoorBird API, it doesn’t seem to work, so I didn’t include support for it.

yep same problem I’m having, @Klikini any chance you can have a look at it when you have time please?

Did anyone get the automatic Axis camera configurator pop up on their home page after connecting their doorbird?

I got it well before official integration. Had to hide it via the config

How did you do that?

@sviudes @reynos I have created a pull request that implements this feature: https://github.com/home-assistant/home-assistant/pull/13268

They have a question that I can’t answer because I don’t use a third party DNS service, but hopefully you can: https://github.com/home-assistant/home-assistant/pull/13268#issuecomment-375760242

My proxy solution just stopt working, still had no time to test this component. So I thought maybe this is the moment…

When I was reviewing my current configuration I noticed that my api notifications were named “legacy”, also the event is now called doorbell1 instead of doorbell. So I grabbed the latest api manual and guess what… They created a hole new api called schedule.cgi OMG!!, and they have stated that the old notifications are migrated. But when reviewing the schedule.cgi api a lot of paramaters are messed up or missing…

Second time they screw up the api…

Also getting all these 401 - Unauthorized on api requests, seems like they also introduced a new permisssion called “API-Operator”.
DoorBird listen: For the sake of backwards compatibility don’t turn it off by default for current (api) users!!!

Men I getting pissed off… :angry:

1 Like

Thank you. I answered the question.

I had the Axis camera config pop up too but it went away once I configured the doorbird camera manually.

camera:
  - platform: doorbird
    last_visitor: true #retirves the most recent last visitor image
> discovery:
>    ignore:
>     - axis

Also would like to see the motion, i was using the one from basschipper, which worked like a charm. Including the motion, i use that to turn on the porch lights since the motion sensor has a nice detection around my door. So i know the notification url did work in the past but since the api updates i am getting those 401’s too. Hence why i am also looking into this direction since if it has motion then i’ll be all set too :slight_smile: if you need me to test anything, just let me know.

I am trying to set up an automation that plays a ring over my home speakers when the door bell is pushed, but I can’t find the sensor that would trigger that automation. I am sure I’m just missing it.