DoorBird Integration Authentication Failure (401 Unauthorized)

[gerdschadler]

The problem

Description: Home Assistant is unable to authenticate with the DoorBird integration. The following error appears in the logs:

Config entry '192.168.1.100' for doorbird integration could not authenticate: 401, message='Unauthorized', url='http://192.168.1.96/bha-api/info.cgi'

It messes up the two products!

This error occurs randomly since the 2025.1 release. Any guidance on resolving this authentication issue would be appreciated. Let me know if further logs or debugging steps are required.

It messes up the two products

What version of Home Assistant Core has the issue?

2025.1.4

What was the last working version of Home Assistant Core?

2024.12

What type of installation are you running?

Home Assistant Container

Integration causing the issue

doorbird

Link to integration documentation on our website

https://www.home-assistant.io/integrations/doorbird

Diagnostics information

Logger: homeassistant.config_entries Source: config_entries.py:668 First occurred: 01:16:28 (1 occurrences) Last logged: 01:16:28

Config entry '192.168.1.100' for doorbird integration could not authenticate: 401, message='Unauthorized', url='http://192.168.1.96/bha-api/info.cgi'

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

I have two doorbird products - A Doorstation 192.168.1.100 and one Buirdgard 192.168.1.96 - Workaround - delte doorstation a add it again.

[home-assistant[bot]]

Hey there @oblogic7, @bdraco, @flacjacket, mind taking a look at this issue as it has been labeled with an integration (doorbird) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of doorbird can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign doorbird Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

doorbird documentation doorbird source _{^{(message by IssueLinks)}}

[tnagels]

I have the same issue. Seems to be related to the config getting mixed up when using 2 or more Doorbirds in the same install.

[juwild83]

Hello, I've been having the same problem for a few days. I have 2 Doorbird devices in the network but only one of them is configured in Home Assistant.

Addendum: Home Assistant always tries to connect to the wrong Doorbird device. Since I have two devices, things seemed to get mixed up.

[tnagels]

@bdraco since you are the assignee, do you need more information concerning this issue? Let me know if there is anything I can do.

[cbw]

I have two Doorbird door stations, and am experiencing the same issue, Failed to set up: 401, message='Unauthorized', url='http://[ip address]/bha-api/info.cgi' on both.

[visitdigital]

I have the same issue and am also using 2 doorbirds on one network.

[giantsumo]

Same issue with 2 devices on the same network. I deleted and re-added both and they worked for a while, but both have reverted to authorization failures.

[giantsumo]

I was able to workaround the error editing .storage\core.config_entries and restarting HA

Both devices had the same "host" key IP address, despite everything else (including the "title" key which has the correct IP) on each line being correct.

{"created_at":"2025-02-16T21:52:40.253584+00:00","data":{"host":"192.168.20.20","name":"Doorbird1","password":...
{"created_at":"2025-02-16T21:53:37.285135+00:00","data":{"host":"192.168.20.20","name":"Doorbird2","password":...

Re-authing via the UI doesn't work because the config flow assumes the "host" key is correct and re-uses that (and therefore contacts the wrong device).

I don't know if the host key is being written incorrectly to start with, or something else is coming along and overwriting the value incorrectly.

[tnagels]

I was able to workaround the error editing .storage\core.config_entries and restarting HA

This worked for me as well. Just an additional tip: you can do this using the File Editor addon, but you need to remove .storage from the ignored patterns in the config.

[giantsumo]

Dug further as after a while the problem cropped up again after I did a HA update.

core.config_entries is being re-written incorrectly every time in developer tools I reload "All YAML Configuration". By disabling zeroconf (had to remove default_config and add all entries except zeroconf), a full yaml config reload no longer rewrites the bad entry.

[tervoluto]

I’m here with 4 DB devices facing the same problem. Editing the .storage\core.config_entries worked for now. But I’m not sure how to do the last advice giantsumo suggested…

[giantsumo]

@tervoluto edit your configuration.yaml and remove default_config: and replace with the entries listed here: https://www.home-assistant.io/integrations/default_config/ except comment out/exclude zeroconf:

Then restart HA.

[stanford-scs]

I have a similar issue. I have four doorbirds, and occasionally the integration will connect to the IP address of the wrong doorbird and think there is an authentication failure. It used to be that it would actually change the IP address in .storage/core.config_entries, so to fix it I would have to shut down homeassistant edit the core.config_entries file to restore the correct IP address, and then restart homeassistant. It hasn't happened as much recently, but happened again where the error message clearly had the wrong IP address, but the core.config_entries file was okay, and just reloading the integration fixed it.

It seems like the integration might be accidentally accessing some global variable where it intends to use per-doorbird variables?

[beatfussel]

I have the problem that I want to add the integration again. I am currently unable to establish the connection to the Doorbird doorbell system with the user login information. Is there already a solution that I can try?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.