The binding was merged into to the openHAB distribution today, Oct 17. It should be available in a snapshot release after build 1728, as well as the next milestone release.
We made several changes to the binding throughout the review process:
The restart and sipHangup channels were removed. They were replaced by the thing actions restart() and sipHangup() that can be called from within rules. There’s an example in the README.
The doorbell channel was redefined to be a system.rawbutton channel that will generate trigger events PRESSED and RELEASED. If you want to use this channel with a Switch item, you need to add the rawbutton-on-off-switch profile to the channel definition. There’s an example of this in the README. If you’re not running a recent snapshot, this won’t work because the rawbutton-on-off-switch profile was recently added to the openHAB core. Instead, you may need to define a proxy item and update its state in a rule that triggered off the PRESSED and RELEASED events.
The getImage channel was removed. To refresh the image channel, send a REFRESH command to the item linked to the image channel.
End of update.
I’ve been developing a binding for the Doorbird doorbells. If anyone is interested in trying it out, the binding jar file and related 3rd party dependencies can be found here.
Features include:
support for models D101 and D210x (note I don’t have a D210x, so that model has not been tested)
channels for doorbell pressed and motion detected events, including switch channels, timestamp channels, and image channels
image channel that can be refreshed on a user defined number of seconds
image and timestamp channels for retrieving historical images and timestamps for button press and motion detected events
history image “montage” channels for displaying a montage (photo strip) of the last n doorbell press and/or motion history images
channels for triggering open door and light relays
all interactions with the Doorbird are done directly (i.e. no cloud) with the exception of the retrieval of the doorbell and motion history images, which the Doorbird pulls from the cloud
Please post back here with any issues or feature requests.
Thanks to @swamiller for helping me test the binding.
Thanks to @dastrix80 for testing some of the new features, as well as the D210x.
Thanks to @Skibi for testing on the RPi. The binding now should work on the RPi2 and Rpi3.
Thanks to @Novanoid for helping me sort out the issues with multiple Doorbirds.
This may be a while, as it’s not supported in the API spec at the moment (although there is something in there that says it’s coming). I’ll email their support to find out if there are really plans to add it.
Hi Mark, i had spoke to them and its coming yes. There is an ability right now with RFID, I have setup the Doorbird to send a HTTP request when the RFID is used to turn on my RFID switch item so there is already some functionality.
Hi @mhilbush once the two binding files are added, is the thing added as per normal by hitting + under THINGS in paperui? Or do we require a THING file ? If so, do you have a sample.
Hmm. I running it on a 2.5 snapshot, and it’s a fairly old snapshot version (build 1502). That build was prior to the ESH reintegration work, and the conversion to the new build system. So, if it runs on that, it should run on 2.4 stable.
The fact that the dependency bundle isn’t showing up is really odd.
What is the size of the jar files in addons? Are you sure you downloaded the jar files? Did you right-click SaveAs on the jar file links, or did you click on the jar file links, then press the Download button? The former will get you an HTML file.
$ ls -l /opt/openhab2/addons
total 8448
-rw-r--r-- 1 mark mark 3824192 Apr 23 08:12 doorbird-deps-1.0.0.jar
-rw-r--r-- 1 mark mark 25079 May 3 07:50 org.openhab.binding.doorbird-2.5.0-SNAPSHOT.jar
Edit: Your doorbird binding might not be exactly the same size, as I’m running a newer version that what’s posted in my Github repo.
If you want to define the thing in a .things file, you would do something like this. The last three parameters are optional, and could be removed, if desired. Note I haven’t tested these…