Hi @mhilbush,
I have a question regarding the openDoor1 and openDoor2 channels: I use them with autoupdate=“false” and added them to the sitemap with a switch, which is using a mapping. The result is a single button in the sitemap. I use this method for many other channels. But in the left of the doorbird channels the switch’s state is shown. Is it possible to hide the state?
Thank you!
Olliver
Sure:
Items:
Switch SPA01_Door1 "Haustüre" <frontdoor> {channel="doorbird:d210x:spa01:openDoor1",autoupdate="false"}
Switch SPA01_Door2 "Hintereingang" <door> {channel="doorbird:d210x:spa01:openDoor2",autoupdate="false"}
Sitemap:
Switch item=SPA01_Door1 mappings=[ON="öffnen"]
Switch item=SPA01_Door2 mappings=[ON="öffnen"]
Result:
The state of the two items is null, because autoupdate is set to false.
Regards,
Oliver
Can you try changing the item definitions to this (note the empty brackets)?
Switch SPA01_Door1 "Haustüre []" <frontdoor> {channel="doorbird:d210x:spa01:openDoor1",autoupdate="false"}
Switch SPA01_Door2 "Hintereingang []" <door> {channel="doorbird:d210x:spa01:openDoor2",autoupdate="false"}
Thank you, worked for me. But why is it necessary only for doorbird channels?
It’s not specific to Doorbird channels. I use this in a variety of places unrelated to Doorbird when I use a mapping and don’t want the state to show up.
Edit: It’s been discussed here on the forum a couple times. Here’s an example.
I have the DoorBird EA Controller as well - am I right that this is not (yet) supported?
Or is it? 
Greetings!
PhiL
btw, I have a DoorBird D205, which you can add to the supported things now
This is the model A1081? If so, it’s currently not supported. However, it looks like it might use the same API as the video doorbells. You might want to try adding a D210x thing, then trying to operate the doors using the openDoor1 and openDoor2 channels. Let me know if that works.
Is the D205 functionally equivalent to the D101?
I’ll add these to my list of things to do. I’m currently focused on getting the binding through the review process and into the distribution. Once that wraps up, I’ll see about adding the D205 and Controller.
Unsure, I added it as a D210x Thing and it worked.
yes it is a A1081. I just tried adding it as a D210x thing, but the button failed.
Here is the tcp dump of that action:
GET /bha-api/open-door.cgi?r=1 HTTP/1.1
Accept-Encoding: gzip
User-Agent: Jetty/9.4.18.v20190429
Accept-Language: en-us
Authorization: Basic Z2hjcW...
charset: utf-8
Host: 10.0.11.248
HTTP/1.1 404 Not Found
Content-Type: text/html
Content-Length: 345
Date: Sun, 06 Oct 2019 21:03:36 GMT
Server: lighttpd/1.4.44
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>404 - Not Found</title>
</head>
<body>
<h1>404 - Not Found</h1>
</body>
</html>
GET /bha-api/open-door.cgi?r=2 HTTP/1.1
Accept-Encoding: gzip
User-Agent: Jetty/9.4.18.v20190429
Accept-Language: en-us
Authorization: Basic Z2hjcWlqMD...
charset: utf-8
Host: 10.0.11.248
HTTP/1.1 404 Not Found
Content-Type: text/html
Content-Length: 345
Date: Sun, 06 Oct 2019 21:03:39 GMT
Server: lighttpd/1.4.44
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>404 - Not Found</title>
</head>
<body>
<h1>404 - Not Found</h1>
</body>
</html>
So If you need help with that - when you get to it - drop me a note, I’ll be around 
Ok. The only thing I’m aware of that’s different between the D101 and D210x is that the D101 supports one door relay and the D210x supports 2 door relays.
Hmm. I took a quick look but didn’t see a separate spec for the A1081. I’ll take another look.
Will do.
Did a little investigation myself, so here ismy finding, maybe it helps to estimate the effort you need.
To open the relay, it is enough to post a GET request to that URL:
example:
http://ghcqiis0001:absdaso3@192.168.0.123/bha-api/open-door.cgi?r=ghcbnl@1
Ah, yes, I see it now in the spec. Should be pretty easy to create a A1081 thing that sends the proper URL for doors 1-3.
I also see there are Ext1 and Ext2 external inputs. I’m not sure if/how those are exposed through the API. Do you use those inputs?
No, I don’t .
I couldn’t resist temptation any longer and ordered a D101 yesterday. Hopefully it will arrive tomorrow so I can tinker with it over the weekend. 
Woohoo! Now to start setting it up. I’ve got a PoE switch in the cellar I can use to power it.
Are there any gotchas I should be aware of when setting it up? Or do I just give it a static IP, update the firmware (if necessary) and add it via the Paper UI?
Yep, that’s how I have mine set up.
They push the firmware updates. I’m not terribly happy about that process, but there always are compromises…
If your Doorbird is on a different subnet or VLAN than your openHAB server, you’ll need to set up routes for the UDP packets that the Doorbird uses for doorbell press and motion events.
I have a separate userid/password that used just by the binding. Make sure the user id you use has the proper permissions, including the API permission.
The motion sensor is a wee bit too sensitive for my taste. Even when narrowing down the detection area, I still get shadows and car lights that trigger it.
After a false start in which I thought the DoorBird was DoA but actually turned out to be because I’d plugged it into the non-PoE switch instead of the PoE switch I’ve got it up and running on the bench. However, the doorbell and motion channels are greyed out and don’t provide the option to attach an item to them:
Is this expected? I’ve enabled debug logging to a separate file and can see entries added to the log when I press the doorbell.
I created a second user as you suggested and enabled all permissions for it. I was a bit surprised that you can’t select the username and password, you just have to accept the username and the password it autogenerates for you every time you tap the “change password” button. Not a big deal though.
Hmm. I’ve not seen that before. In the version you’re running, the doorbell and motion channels are defined as triggers, with profiles that provide the Switch ON/OFF functionality. It’s possible that defining items based on profiles doesn’t work in PaperUI. Can you confirm that you’re using PaperUI to link the channels to items?
Plane about to take off so I might not be able to respond for a bit…
